tegwick
ee37b82675
Some checks failed
ci / check (push) Failing after 3s
Provenance (tier S, one paragraph in lieu of survey and ADR): the two clauses mutation-check has reported inert since CB-WP-0005. AM-7's scaling ratio was held up by a test literally named replay_100k_events_is_linear_and_fast that computed both throughputs, printed both, and never divided one by the other. AM-8's N=10 was held up by a runner that does two. Both are now red. AM-7 3/3, AM-8 2/2, M-D1-MUT 10/14, and ADR-0005's >=10-of-14 prediction MET for the first time. Neither was closed by amending the question away, which was the live risk: the denominator is unchanged and the four unenforced rows are the four already unenforceable. AM-7 needed three estimators. Best-of-N per leg then divide (AM-6's, correct for a floor on one number) gave 0.581-1.085 on an unchanged binary; legs back-to-back gave medians 0.931-1.004; legs interleaved at fold granularity give 0.987/0.991/0.989, and 0.989 under 8-way CPU contention while absolute throughput fell 4x. The INDETERMINATE guard demanded unanimity and failed a good measurement over one sample 0.001 under the floor; it now requires a two-thirds majority. The control that matters: AM-6's constant-cost mutation halves throughput and leaves this ratio at 0.999x green, so AM-7 is not a second AM-6. AM-8 kept N=10 because the measurement said so. Perturbing the RNG only from its fourth construction on: --runs 2 PASSES, --runs 10 fails. A late-onset divergence is deterministic, not flaky, so it is a control rather than a coin flip. Ten runs live on one scenario (make am8, ~2s) rather than all 25 (47s a build). GameKernel 5b records it. The full run also found AM-4a's own mutation stale since ADR-0008 D3 moved the target 250,000 -> 161,000 in CB-WP-0013 -- reported HARNESS-BROKEN, no score published. The build-free half of that check is now a --self-test assertion, so make all catches the next one. mutation-check clauses may now carry their own verify and mutation, and then the enforced flag is measured rather than declared; a declaration disagreeing with its measurement is refused. make all exits 0. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
142 lines
7.2 KiB
TOML
142 lines
7.2 KiB
TOML
# The gate registry (ADR-0006 D3, CB-WP-0009 T02).
|
|
#
|
|
# A gate without an expiry is a permanent tax justified once. Every
|
|
# standing control mechanism gets an entry here saying what it checks,
|
|
# what it has actually **caught**, when its keep-or-kill argument is due,
|
|
# and what would retire it.
|
|
#
|
|
# `make gate-review` reports what is overdue and what has caught nothing.
|
|
# It reports; it does not fail the build — CB-RES-0005 §4: a gate that
|
|
# blocks the remedy when the metric breaches is a trap, not a gate.
|
|
#
|
|
# `caught` is the load-bearing field. An empty `caught` is not proof a
|
|
# gate is useless — it may be preventing rather than missing — but it
|
|
# means the argument has to be made out loud on `review_by`.
|
|
|
|
# Targets in `make all` that are build or acceptance steps rather than
|
|
# *control* gates — they measure the product, not how we work. Listed
|
|
# explicitly so a new target has to be classified rather than ignored;
|
|
# `loop-lint` fails when a target is in neither list.
|
|
not_control_gates = [
|
|
"check", "test", "sim", "bench-test", "size-metrics", "runtime-metrics",
|
|
"am6", "am7", "am8", "replay-test", "dep-weight", "self-tests", "env-test",
|
|
]
|
|
|
|
[[gate]]
|
|
id = "CB-01/CB-02"
|
|
name = "cost budget"
|
|
target = "cost-budget"
|
|
checks = "spend since the last commit; soft $10, hard $22"
|
|
added = "2026-07-30"
|
|
review_by = "2026-11-30"
|
|
caught = [
|
|
"CB-WP-0005: hard breach forced the Phase C re-plan",
|
|
"CB-WP-0006 T07: $12.06 in one task, the pass's most expensive",
|
|
]
|
|
retire_if = "two consecutive passes never approach the soft line, or commits get small enough that the window is always trivial"
|
|
|
|
[[gate]]
|
|
id = "SH-1/SH-2"
|
|
name = "session-shape budget"
|
|
target = "shape-budget"
|
|
checks = "mean and p90 context since the last commit (SH-3 retired as a gate, ADR-0008 D1 — still reported as a diagnostic)"
|
|
added = "2026-08-01"
|
|
review_by = "2026-11-30"
|
|
caught = [
|
|
"first run fired HARD at 656,574 against a 300,000 ceiling, which is what prompted the compaction before CB-WP-0008",
|
|
"CB-WP-0013: SH-3 retired from this gate. Its window is *since the last commit*, which during a pass is implementation work, and batching needs two calls whose inputs are known at once — which is orientation work. Measured: 0 batched turns in 150 in-pass responses across three passes, against 37.5% in the gap between two of them. A floor the window structurally excludes is not a target (ADR-0008 D1)",
|
|
]
|
|
retire_if = "context stops correlating with cost, or the model's context handling makes the number unactionable"
|
|
|
|
[[gate]]
|
|
id = "M-D1-MUT"
|
|
name = "mutation coverage of acceptance rows"
|
|
target = "mutation-check"
|
|
checks = "each acceptance row's assertion must go red for a stated reason when mutated"
|
|
added = "2026-07-31"
|
|
review_by = "2026-12-31"
|
|
caught = [
|
|
"AM-6 measuring contention, not throughput",
|
|
"AM-5's 61% measurement error under load",
|
|
"peak RSS over-reported 3x",
|
|
"K10's first round trip not reproducing",
|
|
"the bench workload existing twice",
|
|
"AM-2's expect matching its own passing output (EXPECT-VACUOUS)",
|
|
"CB-WP-0015: the two clauses it had reported inert since CB-WP-0005 — AM-7's scaling ratio (a test named `replay_100k_events_is_linear_and_fast` that computed both throughputs, printed both, and never divided one by the other) and AM-8's N=10 (the runner did two). Both now red, 10/14, and the >=10-of-14 prediction met for the first time",
|
|
"CB-WP-0015: AM-4a's own mutation, stale since ADR-0008 D3 moved the target 250,000 -> 161,000 in CB-WP-0013. Reported HARNESS-BROKEN and refused to publish a score, which is the harness catching itself. The build-free half of that check is now a --self-test assertion, so it runs in `make all` instead of only on a full run",
|
|
]
|
|
retire_if = "a full pass adds rows without finding anything, twice running — the harness costs real money per run"
|
|
|
|
[[gate]]
|
|
id = "DFD"
|
|
name = "single source of fact"
|
|
target = "facts-check"
|
|
checks = "every tagged number in the docs matches the tool that measures it"
|
|
added = "2026-07-31"
|
|
review_by = "2026-12-31"
|
|
caught = [
|
|
"gr_scenarios stale at 21 after CB-WP-0008 T03 added three scenarios",
|
|
]
|
|
retire_if = "the untagged-literal count reaches zero and stays there, meaning the docs stopped restating measured numbers"
|
|
|
|
[[gate]]
|
|
id = "AM-1b"
|
|
name = "kernel spec->code link"
|
|
target = "coverage"
|
|
checks = "every numbered K-rule is named in the source; binds 2026-08-31"
|
|
added = "2026-07-31"
|
|
review_by = "2026-08-31"
|
|
caught = [
|
|
"3 unlinked K-rules at introduction (15/18); 18/18 today",
|
|
]
|
|
retire_if = "it stays at 100% through two passes that add kernel rules — at that point it is measuring a habit, not enforcing one"
|
|
|
|
[[gate]]
|
|
id = "META-25"
|
|
name = "meta budget"
|
|
target = "status"
|
|
checks = "share of the trailing 3 passes spent on the loop itself; soft 25%"
|
|
added = "2026-08-01"
|
|
review_by = "2026-11-30"
|
|
caught = [
|
|
"its own cumulative-window defect, reported in CB-EV-0007 §3 and fixed by CB-WP-0009 T01",
|
|
]
|
|
retire_if = "product and meta stop being separable, or the share sits under the line for four passes without anyone consulting it"
|
|
|
|
[[gate]]
|
|
id = "LOOP-LINT"
|
|
name = "executable InnerLoop rules"
|
|
target = "loop-lint"
|
|
checks = "loadability, unmeasured verdicts, tier and chaos declarations, review trails, self-test entry points, and this registry"
|
|
added = "2026-07-30"
|
|
review_by = "2026-12-31"
|
|
caught = [
|
|
"four loadability breaches (401, 427, 406, 409 lines), each fixed structurally rather than by raising the limit",
|
|
"a reporting tool with no --self-test entry point (tools/repo.py)",
|
|
]
|
|
retire_if = "two passes run with no finding while artifacts keep growing — that would mean it is measuring the wrong properties"
|
|
|
|
[[gate]]
|
|
id = "CHAOS"
|
|
name = "the chaos roll"
|
|
target = ""
|
|
checks = "d4 on each tier declaration, 12-declaration calibration window"
|
|
added = "2026-07-30"
|
|
review_by = "2026-09-30"
|
|
caught = [
|
|
"CB-WP-0011: first fire in 6 declarations — d4=4 rolled stage 1 from structural L to S; the deleted survey would have opened on 2D toolkits while the existing text renderer was showing 24 of 41 view fields (CB-EV-0009 §1)",
|
|
"CB-WP-0012: d4=1, no override — and the contrast is the entry. Tier L at full weight deleted its own structural trigger: adversarial review withdrew the capability port the declaration was made to build (ADR-0007 D2), and corrected the survey's headline claim by 85x (128x -> 1.5x, CB-EV-0010 §2). Two passes on one subject at two tiers, priced: 0.123 $/response at L against 0.099 at S (CB-EV-0010 §5)",
|
|
]
|
|
retire_if = "the window closes with no overridden tier producing a different outcome than the argued one — the evaluation this window exists to make possible"
|
|
|
|
[[gate]]
|
|
id = "GATE-REVIEW"
|
|
name = "this registry"
|
|
target = "gate-review"
|
|
checks = "gates past their review date, and gates that have caught nothing"
|
|
added = "2026-08-01"
|
|
review_by = "2026-12-31"
|
|
caught = [
|
|
"CB-WP-0013: forced SH-3's re-justification and then its retirement. `make gate-review` had reported SH-3 as a standing breach for seven passes with zero actions taken, which is this registry's own ritual test (ADR-0006 D4); asking what it had ever caught is what exposed that the metric could not read above ~0% in the window it was gated on (ADR-0008 D1)",
|
|
]
|
|
retire_if = "it has retired, tightened, or forced the re-justification of nothing by its review date — then it is a ritual, and ADR-0006 D4 says rituals cash out or go"
|