An index that outgrew its own budget
/ork:dream STEP 5.5 + context-file-budget-guard, #3741 · measured: this repo's MEMORY.md at 22,234 B, 127.7% of 17,408 · 2026-08-31
Why the budget existed and still did not bind
dream SKILL.md "target <= 17 KB, trim hooks, never drop an entry" prose, single-file invariant, no demotion rule budget guard ASKs before an over-budget MEMORY.md write skipped in BYPASS mode: the population that writes it most measured six projects at or over 17,408 B; this repo 22,234 B; MEMORY-ARCHIVE.md 23 KB, unbudgeted by design
Two fixes, one rule. The guard now returns advisory context in bypass mode (a systemMessage would be dropped by the write-edit dispatcher; context is the channel the model reads). And dream gets an executable budget pass: report by section, then demote by RULE, oldest first, never by judgement, behind the existing ask gate.
Try it: paste an index, pick a ceiling
Same rule as scripts/dream/scripts/index-budget.mjs: Handoffs older than 7 days (date from the filename), Feedback/Project older than N days (here: a fake age from the entry order), never hub_/user_/Policy. Ages are simulated in the browser; the script uses real file mtimes.