CB-WP-0009-T04: CB-EV-0008 — the gate changes, measured
Some checks failed
ci / check (push) Failing after 4s
Some checks failed
ci / check (push) Failing after 4s
The windowed budget is confirmed for the failure it was written against and not for the general claim: a single-pass window reads 0% for CB-WP-0008 against 50% lifetime, but the trailing-3 window reads 45% against 50%, inside the refutation band. The prediction was written before the window size was chosen and did not say which comparison it meant. Both readings are on record and whether 3 is the right window is carried as open. gate-review's first run: 9 gates, 0 due, 2 silent. The silent two are the chaos roll and gate-review itself, both with dates. A registry where everything looked productive would have been one written to look good. D4 holds per pass, not per task: three of four tasks shipped a command, and the two that did not are the spec change that makes the commands normative and the evidence file that checks them. Cost is the honest part. This pass cashed out three commands and ran at $0.177/response — cheaper than every previous meta pass (0.228, 0.298, 0.362) and still 1.4x the product pass at 0.123. Partial support for D4, not vindication. Context breached both shape targets because the pass ran on an already-long session; reported, not gated. Meta reads 45% of the trailing three against a soft 25%. Nothing was displaced, but the number is over the line and the next pass should be product. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
2b6bf29e8f
commit
06483bc587
2 changed files with 142 additions and 2 deletions
|
|
@ -2,7 +2,7 @@
|
|||
id: CB-WP-0009
|
||||
kind: meta
|
||||
title: "Make control gates experimental: window them, review them, cash them out"
|
||||
status: in_progress
|
||||
status: done
|
||||
authorized_above_budget: "maintainer, 2026-08-01 — 'improve our policies where it seems promising; we will experiment our way to sensible task- and context-specific control and review gates'. Meta read 59% at the time."
|
||||
state_hub_workstream_id: "98c0af4a-415c-4cf5-92d0-a722eb70cb90"
|
||||
---
|
||||
|
|
@ -120,7 +120,7 @@ started at 399.
|
|||
|
||||
```task
|
||||
id: CB-WP-0009-T04
|
||||
status: todo
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "e06f57fc-147f-4cba-b398-0db6b060381f"
|
||||
```
|
||||
|
|
@ -139,3 +139,9 @@ answered from output, not argument:
|
|||
pass or needs the exception written down.
|
||||
4. **Cost**, against the 0.123–0.362 per-response range, and the meta
|
||||
share this pass itself consumed — reported under the rule it wrote.
|
||||
|
||||
**Done 2026-08-01.** [CB-EV-0008](../evidence/CB-EV-0008-adaptive-gates.md).
|
||||
The pass ran at **$0.177/response** — cheaper than every previous meta
|
||||
pass and still 1.4× the product pass, which is partial support for D4 and
|
||||
is reported as such. Meta share reads **45% over the trailing three**,
|
||||
over the line; the next pass should be product.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue