Evidence record / omp
A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.
2026-10-13-omp-per-model-compaction-numbers-became-scaled-bases-instead-of-exact-triggers
Per-model compaction numbers became scaled bases instead of exact triggers. A numeric compaction.modelThresholds entry now supplies a base the configured policy scales, rather than an exact compaction trigger. At v18.10.4 f400k preserves an exact 400K trigger subject to the model-window cap. Per-agent numeric overrides remain exact. A base above the standard model window can opt into extended context and its pricing even if the scaled trigger lands inside the standard window.
Channel: tagged-release. Half: both. Date: 2026-10-10 (v18.8.8).
Operator consequence: Inspect existing numeric model limits and the /models preview. Use the f form for an exact trigger, and keep bases at or below the standard window or fixed triggers below it when avoiding extended-context rates. Recheck model and agent limits separately.
Receipt
Finding metadata
Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0
Finding ID: 2026-10-13-omp-per-model-compaction-numbers-became-scaled-bases-instead-of-exact-triggers
Profile citations
- omp / claim / scaled-compaction-limits
Source links
Primary links, including exact changelog lines when available.
- commit2026-10-13-omp-per-model-compaction-numbers-became-scaled-bases-instead-of-exact-triggersgithub.com/can1357/oh-my-pi/commit/a5e542daa2e648397957f2c987aa3b3be9cf1309tagged commit file2026-10-13-omp-per-model-compaction-numbers-became-scaled-bases-instead-of-exact-triggerscan1357/oh-my-pi / docs/settings.md#L791-L808
Versioned source: run artifact