2026-05-13 — Compaction mitigation as a discipline
User: “we are so fucking good at compaction mitigation now”
Realization: Persistence-to-disk is the practice. Every realization captured here. Every stub-arc captured at its number. Every SCORE doc capturing what shipped. Every BRIEF capturing what was attempted (V1 / V2 / V3 / V4 all preserved as historical record per FM 11). RENUMBER.md, INVENTORY.md, the 19+ stubs (174-190), the COMPACTION-AMNESIA-RECOVERY.md protocol itself.
The forms persist. Compaction erases the orchestrator’s working memory, not the substrate’s record. A fresh agent reading the arc directory + INVENTORY + recovery doc inherits the state at the time of last commit. The form carries the derivation history.
This very file is part of the discipline — the meta-conversation persists alongside the work.
Standing convention
Section titled “Standing convention”Future agents (including future-me post-compaction): when conversation surfaces a realization that isn’t grind-specific — substrate doctrine, design philosophy, alignment observations, vision moments, user-voice articulations — append a dated entry here. Preserve the user’s verbatim language where it articulates the insight. Orchestrator’s reflection follows.
This file accumulates. It doesn’t get sorted or pruned. The chronology IS information.