CB-WP-0009-T03: InnerLoop v1.6

D2 the two exemptions — repairing the instrument that reports a breach
is always in budget, and the maintainer may authorize above-line work in
the workplan frontmatter. v1.5 had neither, and the first thing it did
was forbid fixing the budget's own defect.

D4 loop work cashes out into something runnable in the pass that invents
it, with the measured basis and the refutation condition stated.

D5 the tier table now triggers at M for changes to the loop's own
operation, closing the gap CB-RES-0005 §6 opened and this pass's own ADR
had to declare around.

The file went from 399 lines to 386: the chaos-roll calibration
rationale and the v1.0-v1.3 change log moved to InnerLoopReference.md.
Loadability is a gate too, and growing the file to fit a rule about
gates would have been the joke writing itself.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-01 15:43:34 +02:00
parent cd2dc5380a
commit 2b6bf29e8f
3 changed files with 116 additions and 68 deletions

View file

@ -92,7 +92,7 @@ a finding, both pinned by self-tests. First run: **0 due, 2 silent**
```task
id: CB-WP-0009-T03
status: todo
status: done
priority: medium
state_hub_task_id: "0b1b33ac-8046-4b34-b287-7b32755d964a"
```
@ -111,6 +111,11 @@ Fold **D2**, **D4** and **D5** into `specs/InnerLoop.md`:
pointer. Loadability is itself a gate; growing the file to fit a rule
about gates would be the joke writing itself.
**Done 2026-08-01.** v1.6 in `specs/InnerLoop.md`, **386 lines** — the
chaos-roll calibration rationale and the v1.0v1.3 change log moved to
`specs/InnerLoopReference.md`, so the file came in *smaller* than it
started at 399.
## Task: control loop — did the changes fire?
```task