neuwirth
/
pmacs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: bound R7's observation window so the tally stops re-counting itself 

The previous commit recorded "in-gate 2 failures in 4 runs" and named
the final verification gate. Re-running the gate on that very commit
made both wrong: a fifth in-gate run, green, and a new log id. Every
docs fix forces a re-gate, and the re-gate invalidates the docs fix.

R7's window is now explicitly the four in-gate runs of 2026-08-29 up to
and including the first green, plus the 17 out-of-gate runs taken
between them. Later verification gates are excluded by definition. A
ratio that grows with review activity measures review activity, not the
phenomenon.

The ledger stops naming the head and log id at all. It records that
every review round ends with a green head-exact gate and points at the
PR body for the current values --- which is the same reason SS5b stopped
recording an ahead-count: a line naming a moving value is stale the
moment it is written, and that lane learned it twice.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016bqGA6s9tTUFzYpbeW3tai
This commit is contained in:
Levi Neuwirth 2026-08-29 18:11:02 +02:00
parent acd6cee693
commit 054a427e74
No known key found for this signature in database
2 changed files with 23 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
docs/active-work.md
View File

@ -330,16 +330,17 @@ from #171 and #215.
*exclusions* — is corrected there: nothing outside the gate has ever *exclusions* — is corrected there: nothing outside the gate has ever
reproduced this, so matching one gate condition at a time outside it reproduced this, so matching one gate condition at a time outside it
cannot isolate an in-gate cause. In-gate is 2 failures in 4; cannot isolate an in-gate cause. In-gate is 2 failures in 4;
out-of-gate is 0 in 17 — **and a fourth in-gate run, this lane's out-of-gate is 0 in 17, over a **bounded observation window** the
final verification gate, was also green, so the cumulative figure is registry defines so the ratio cannot drift with review activity.
2 in 4**. Recorded in the registry; **not this lane's to solve**. Recorded there; **not this lane's to solve**.
- **PR #244** — https://github.com/levineuwirth/pmacs/pull/244, opened - **PR #244** — https://github.com/levineuwirth/pmacs/pull/244.
at head **`2d76984`**, which is exactly the head the gate ran on. - **Every review round ends with a head-exact 8-stage gate**, green
- **GATE GREEN, head-exact**: all 8 stages, log each time, with `HEAD` and a clean worktree captured before and after
`20260829T152824Z-673477`, with `HEAD` and a clean worktree captured and the result read from the eight stage logs rather than inferred
before and after. Zero `FAILED` lines and zero non-zero-failure from stage exits. **The PR body carries the current head and log
result lines across all eight stage logs, read from them rather than id**; they are not duplicated here, because a docs commit answering a
inferred from stage exits. review moves both, and a ledger line naming them is stale the moment
it is written — the lesson §5b learned twice.
- **Still owed, separately:** `workflow_dispatch` on `ci.yml`, and U9's - **Still owed, separately:** `workflow_dispatch` on `ci.yml`, and U9's
discriminating control — pin test-binary concurrency to 1, then load discriminating control — pin test-binary concurrency to 1, then load
a lone `--lib` binary — which has been named since 2026-08-09 and a lone `--lib` binary — which has been named since 2026-08-09 and

18
docs/ci-red-signatures.md
View File

@ -561,12 +561,18 @@ isolate an in-gate cause. All these runs establish is that none of the
four conditions **by itself** reproduces the failure. They do not show four conditions **by itself** reproduces the failure. They do not show
that any of them is uninvolved when the gate supplies the rest. that any of them is uninvolved when the gate supplies the rest.
**What the observations actually support**, stated at the strength they **THE OBSERVATION WINDOW IS BOUNDED, deliberately.** It is the four
carry: in-gate is **2 failures in 4 runs** — the failing pair, then two in-gate runs of 2026-08-29 up to and including the first green —
greens, the second of which is this lane's final head-exact `20260829T144541Z`, `T150011Z`, `T152024Z`, `T152824Z` — plus the 17
verification gate (`20260829T152824Z-673477`) — while out-of-gate is out-of-gate runs taken between them. **Later head-exact verification
**0 failures in 17**. That asymmetry is suggestive and it is not a gates on this lane are NOT part of it and do not move these numbers.**
clean split, Without that boundary the tally re-counts itself every time a review
round adds a docs commit and the gate is re-run, which is a ratio that
drifts with review activity rather than with the phenomenon.
**What the window supports**, at the strength it carries: in-gate
**2 failures in 4**; out-of-gate **0 failures in 17**. That asymmetry
is suggestive and it is not a clean split,
because the third in-gate run passed. because the third in-gate run passed.
**The method for the next occurrence follows from that.** Varying **The method for the next occurrence follows from that.** Varying