{"path":"research/catching-a-proposal-made-unnecessary/cases-negatives/BD29.md","content":"*Spoken name: CLAUDE.md written once a sitting.* *About: How a ruling reaches the always-loaded instruction file during a sitting of rulings.* **A ruling is recorded at once in the ledger row and the canon note, and CLAUDE.md is written once, at the end of the sitting, from a waiting list in the canon note.** Every edit to a CLAUDE.md attaches the whole changed file again to every running session, which carries the copy until it compacts; in the sitting of 2026-10-25 to 26 this session received 17 such copies, about 250,000 tokens each, one per canon ruling, against about 3,500 tokens a message for all the per-turn hooks together (`~/dotfiles/docs/claude_plan_usage_and_what_spends_it.md` § 3). The ruling and its canon decision still go in the same reply; only the write to the file waits. **Meets:** standing discipline 4 in CLAUDE.md § READ FIRST (every ruling carries its canon decision in the same reply), which this leaves whole; the plan-usage note § 5 item 4, which had left the batching unpursued. Reverses nothing settled."}