tegwick
291d1e9798
Some checks failed
ci / check (push) Failing after 3s
Covers what the immediate CI fixes did not. Framing finding: writing a rule into InnerLoop did not prevent the next instance of the failure it was written for; making it a CI step caught one on its first run. Four instances of the harness-does-nothing class, zero prevented by prose. Working hypothesis: a loop rule that cannot be executed is not a rule. Each item is made executable or deleted, default delete. Phase A makes rules executable: audit every InnerLoop rule as executable/checkable/decorative, extend the positive-control gate beyond benchmarks, and point adversarial review at measurement rather than only research — all four real errors were in measurement and build config, which the review never reads. Phase B is session economics, from measurement: 592 turns, mean context 245k tokens, $0.245/turn in cache reads, zero batched tool calls, cache reads 58% of cost against output at 12%. Cost is turns x context and context grows with turns, so a long session is quadratic. Also replaces the dead 8k/10k token budget, which was never enforced and which T08 exceeded by orders of magnitude with no signal. Phase C removes or fixes the rest: resolve the chaos roll (never fired, and at 1-in-10 will stay unevaluated), require retargeting to be an ADR rather than something the implementer does in the commit that measures the metric, give provisional items an owner and expiry, and strengthen the coverage gate beyond tag-counting. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| CB-WP-0001-inner-loop.md | ||
| CB-WP-0002-cost-accounting.md | ||
| CB-WP-0003-loop-hardening.md | ||