docs(assessment): Wave 0 — the execution plan and the ruling packet (R-1…R-15) #140

Merged

core-labs merged 2 commits from docs/wave0-rulings into main

2026-07-28 01:05:56 +00:00

core-labs commented

2026-07-28 00:48:02 +00:00

Owner

Phase 6 of the holistic assessment: what follows from it, and what it needs ruled before anything else can be sequenced. Docs only — no runtime behavior, no flag, no test changed.

Stacked: PR-1 (docs/wave0-amendments) sits on this branch and applies the register corrections. Merge this one first, merge-commit not squash.

What lands

docs/assessment/50-execution-plan.md — five waves (scrub/rule → delete → simplify/enforce → accelerate evidence loops → automate last) plus five frontier tracks, covering every G-1…G-20 and H-1…H-14 entry, with four hard dependency gates and nine risks stated before they are incurred.

docs/assessment/50-rulings.md — R-1…R-15. One decision per section: evidence verified at ed06dd64, options enumerated, a recommendation with its reasoning, and the exact diff that follows from each choice, so ruling costs one word. Nothing in it recommends reversing a ratified decision; R-12 amends two ADRs' records without touching either decision.

§0 carries seven corrections to the assessment

All found by reading code, workflows, and ADR supersession banners — none by re-reading documents. Four change planned work:

N-3 (new) — the local smoke suite (23 files) and smoke.yml (13) have diverged by 10 files. Severity is lower than this plan's first draft stated: AGENTS.md makes the in-worktree run the merge gate and CI secondary observability, and the local gate is the superset, so nothing is unguarded. What is real: two in-repo places assert a parity that does not hold — core/cli_test.py's audio block, and scripts/hooks/pre-push's own header calling step 1 "exact CI-gate parity" — plus the push that skipped the local gate, for which CI is the only automatic check.
N-4 — the L10 soak has been run: 5000 beats, reboot at 2500, all four gates pass (contract.md, landed aed273b1). G-5's "never produced an artifact" is wrong. The debt is the ceremony — no committed report, no pinned deterministic_digest (the contract's own unmet closing instruction), no cadence. Prose with no pinned digest is testimony, not evidence.
N-5 — G-10's blocker does not exist. ADR-0264 §4.1 carries a self-supersession banner: R5 removed the 16-premise cap on 2026-07-26, and four bands would earn SERVE the moment a ledger is sealed. PR-13 is withdrawn and the entire throughput frontier reduces to one ruling (R-8).
N-7 — the flag count is 28 of 32 RuntimeConfig booleans, not seventeen.

Plus N-1 (the orphan scan artifact: TEST_SUITES["full"] is a directory), N-2 (the L10 pins run twice a day, post-merge and nightly), and N-6 (H-8 has a fourth instance inside the code — two flag docstrings assert a production profile CONTINUOUS_LIFE_CONFIG_FLAGS does not have, which moves R-3 decisively toward "incomplete flag set").

The fifteen rulings, one line each

#	Question	Recommendation
R-1	CR-3 efferent action	A deferred, criterion named
R-2	CR-4 "now"	B beats govern cognition, wall-clock in telemetry only
R-3	F-6 accrual flag	A incomplete set — add the flag
R-4	Flag profiles	A profiles + register + pin (28 flags)
R-5	Identity bar	A discrimination bar, corpus and floor named
R-6	Non-text ingest	A deferral with the falsification bench as the standard
R-7	Register supersession	A supersede both, migrate 7 ratchet items into G-5
R-8	Curriculum outcome-mix	C separate `unknown`- and `entailed`-serving licenses
R-9	Soak evidence + cadence	A commit artifact, pin digest, change-triggered cadence
R-10	PR #138	A merge — measurement only, fixes stay held
R-11	Interim fabrication gate	B measure the cost, then rule again
R-12	Two ADR record amendments	A/A apply both drafted texts
R-13	Wilson re-count	A authorize, apply demotions, move the pin
R-14	Gate parity direction	A raise CI, +46s measured on the runner's own hardware
R-15	Predecessor-verdict rule	A standing doctrine, scoped to authorization not building

To rule: reply with the item and choice — R-1 A · R-3 B · R-8 C. Anything left unruled stays PENDING and blocks only the wave named in its Blocks line.

Standing constraints honored

The PR #138 fabrication findings stay measured and pinned, fix held for ADR + ratification. R-10 recommends merging #138 because it is measurement-only; the two known mutations are not in scope anywhere in this plan.
The two ratified-ADR amendments (ADR-0146, ADR-0252) are not applied in either PR — they are drafted in full inside R-12 and land on that ruling, because editing a ratified ADR is Shay's authority even when the edit changes no decision.

[Verification]: base forgejo/main @ ed06dd64. In-worktree (core-wt-wave0): uv run core test --suite smoke -q → 641 passed in 175.06s. Pre-push gate on this push: smoke 641 passed, warmed_session lane 10 passed in 141.61s, deductive suite green. Docs-only diff; no code path touched.

Phase 6 of the holistic assessment: what follows from it, and what it needs ruled before anything else can be sequenced. **Docs only — no runtime behavior, no flag, no test changed.** Stacked: PR-1 (`docs/wave0-amendments`) sits on this branch and applies the register corrections. **Merge this one first, merge-commit not squash.** --- ## What lands **`docs/assessment/50-execution-plan.md`** — five waves (scrub/rule → delete → simplify/enforce → accelerate evidence loops → automate last) plus five frontier tracks, covering every G-1…G-20 and H-1…H-14 entry, with four hard dependency gates and nine risks stated before they are incurred. **`docs/assessment/50-rulings.md`** — R-1…R-15. One decision per section: evidence verified at `ed06dd64`, options enumerated, a recommendation with its reasoning, and the exact diff that follows from each choice, so **ruling costs one word**. Nothing in it recommends reversing a ratified decision; R-12 amends two ADRs' *records* without touching either decision. ## §0 carries seven corrections to the assessment All found by reading code, workflows, and ADR supersession banners — **none by re-reading documents**. Four change planned work: - **N-3 (new)** — the local smoke suite (23 files) and `smoke.yml` (13) have diverged by 10 files. Severity is **lower** than this plan's first draft stated: AGENTS.md makes the in-worktree run the merge gate and CI secondary observability, and the local gate is the superset, so **nothing is unguarded**. What is real: *two* in-repo places assert a parity that does not hold — `core/cli_test.py`'s audio block, and `scripts/hooks/pre-push`'s own header calling step 1 *"exact CI-gate parity"* — plus the push that skipped the local gate, for which CI is the only automatic check. - **N-4** — the L10 soak **has been run**: 5000 beats, reboot at 2500, all four gates pass (`contract.md`, landed `aed273b1`). G-5's "never produced an artifact" is wrong. The debt is the ceremony — no committed report, no pinned `deterministic_digest` (the contract's own unmet closing instruction), no cadence. **Prose with no pinned digest is testimony, not evidence.** - **N-5** — G-10's blocker does not exist. ADR-0264 §4.1 carries a self-supersession banner: R5 removed the 16-premise cap on 2026-07-26, and **four bands would earn SERVE the moment a ledger is sealed**. PR-13 is withdrawn and the entire throughput frontier reduces to one ruling (R-8). - **N-7** — the flag count is **28 of 32** `RuntimeConfig` booleans, not seventeen. Plus **N-1** (the orphan scan artifact: `TEST_SUITES["full"]` is a directory), **N-2** (the L10 pins run twice a day, post-merge and nightly), and **N-6** (H-8 has a fourth instance *inside the code* — two flag docstrings assert a production profile `CONTINUOUS_LIFE_CONFIG_FLAGS` does not have, which moves R-3 decisively toward "incomplete flag set"). ## The fifteen rulings, one line each | # | Question | Recommendation | |---|---|---| | R-1 | CR-3 efferent action | **A** deferred, criterion named | | R-2 | CR-4 "now" | **B** beats govern cognition, wall-clock in telemetry only | | R-3 | F-6 accrual flag | **A** incomplete set — add the flag | | R-4 | Flag profiles | **A** profiles + register + pin (28 flags) | | R-5 | Identity bar | **A** discrimination bar, corpus and floor named | | R-6 | Non-text ingest | **A** deferral with the falsification bench as the standard | | R-7 | Register supersession | **A** supersede both, migrate 7 ratchet items into G-5 | | R-8 | Curriculum outcome-mix | **C** separate `unknown`- and `entailed`-serving licenses | | R-9 | Soak evidence + cadence | **A** commit artifact, pin digest, change-triggered cadence | | R-10 | PR #138 | **A** merge — measurement only, fixes stay held | | R-11 | Interim fabrication gate | **B** measure the cost, then rule again | | R-12 | Two ADR record amendments | **A/A** apply both drafted texts | | R-13 | Wilson re-count | **A** authorize, apply demotions, move the pin | | R-14 | Gate parity direction | **A** raise CI, +46s measured on the runner's own hardware | | R-15 | Predecessor-verdict rule | **A** standing doctrine, scoped to authorization not building | To rule: reply with the item and choice — `R-1 A · R-3 B · R-8 C`. Anything left unruled stays PENDING and blocks only the wave named in its **Blocks** line. ## Standing constraints honored - The PR #138 fabrication findings stay **measured and pinned, fix held for ADR + ratification**. R-10 recommends merging #138 because it is measurement-only; the two known mutations are not in scope anywhere in this plan. - The two ratified-ADR amendments (ADR-0146, ADR-0252) are **not applied** in either PR — they are drafted in full inside R-12 and land on that ruling, because editing a ratified ADR is Shay's authority even when the edit changes no decision. --- `[Verification]:` base `forgejo/main` @ `ed06dd64`. In-worktree (`core-wt-wave0`): `uv run core test --suite smoke -q` → **641 passed in 175.06s**. Pre-push gate on this push: smoke **641 passed**, warmed_session lane **10 passed in 141.61s**, deductive suite green. Docs-only diff; no code path touched.

core-labs added 2 commits 2026-07-28 00:48:05 +00:00

docs(assessment): Wave 0 — the execution plan and the ruling packet (R-1…R-14) 372bdf987d

Phase 6 of the holistic assessment: what follows from it, and what it needs
ruled before anything else can be sequenced.

`50-execution-plan.md` — five waves (scrub/rule → delete → simplify/enforce →
accelerate evidence loops → automate last) plus five frontier tracks, covering
every G-1…G-20 and H-1…H-12 entry, with four hard dependency gates and nine
risks stated before they are incurred.

`50-rulings.md` — R-1…R-14. One decision per section: the evidence verified at
ed06dd64, the options enumerated, a recommendation with its reasoning, and the
exact diff that follows from each choice, so ruling costs one word. Nothing in
it recommends reversing a ratified decision; R-12 amends two ADRs' records
without touching either decision.

§0 of the plan carries SEVEN corrections to the assessment, all found by
reading code, workflows and ADR supersession banners — none by re-reading
documents. Four change planned work:

- N-3 (new) the local smoke suite (23 files) and smoke.yml (13) have diverged
  by 10 files. Severity is LOWER than this plan's first draft stated: AGENTS.md
  makes the in-worktree run the merge gate and CI secondary observability, and
  the local gate is the superset — so nothing is unguarded. What is real is one
  in-code comment claiming an equality that does not hold, and the push that
  skipped the local gate, for which CI is the only automatic check.
- N-4 the L10 soak HAS been run — 5000 beats, reboot at 2500, all four gates
  pass (contract.md, landed aed273b1). G-5's "never produced an artifact" is
  wrong. The debt is the ceremony: no committed report, no pinned
  deterministic_digest (the contract's own unmet closing instruction), no
  cadence. Prose with no pinned digest is testimony, not evidence.
- N-5 G-10's blocker does not exist. ADR-0264 §4.1 carries a self-supersession
  banner: R5 removed the 16-premise cap on 2026-07-26, and four bands would
  earn SERVE the moment a ledger is sealed. PR-13 is WITHDRAWN and the whole
  throughput frontier reduces to one ruling (R-8).
- N-7 the flag count is 28 of 32 RuntimeConfig booleans, not seventeen.

Plus N-1 (the orphan scan artifact: TEST_SUITES["full"] is a directory),
N-2 (the L10 pins run twice a day, post-merge and nightly), and N-6 (H-8 has a
fourth instance inside the code — two flag docstrings assert a production
profile the production profile does not have, which moves R-3 decisively
toward "incomplete flag set").

Docs only. No runtime behavior, no flag, no test changed.

docs(assessment): the pre-push hook makes the same parity claim (R-14, N-3) c3f1ddb643

scripts/hooks/pre-push — the automation of the AGENTS.md local-first protocol
— opens by describing its own step 1 as "the smoke suite — exact CI-gate
parity". It runs 23 files; the CI gate runs 13. That is the second in-repo
assertion of a parity that does not hold, the first being core/cli_test.py's
audio block, and it is the strongest evidence available that the drift was
never intended rather than a deliberate narrowing.