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

docs(evidence): the manifest fix in revision 9 never landed 

74dbd34 corrected the framing so that "the difference is not captured"
attaches to the uniform-same endpoint verdicts rather than to mixed ---
mixed means intermittency --- but the manifest kept the wrong pairing.
The edit's anchor did not match and the script reported success anyway,
so the commit touched only active-work.md and the framing.

The manifest now defers to §7 D0a for the governing contract and states
the three verdicts with the conclusions that actually belong to them:
clean split permits the bisect, mixed means intermittency under fixed
source, both-uniform-same means the difference is not captured by those
two commits.

Process note, since this is the third silent no-op of its kind in this
lane: an unasserted string replace that misses its anchor is
indistinguishable from one that succeeded. Every edit here now asserts
the anchor before writing and re-asserts the result afterwards.

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-19 10:41:13 +02:00
parent 74dbd342a6
commit f99250e8cd
No known key found for this signature in database
1 changed files with 19 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
docs/probe-sigint-evidence.md
View File

@ -175,10 +175,22 @@ log digest. Two constraints learned the hard way:
`7599661` (last observed green) and `724b785` (first observed red) — `7599661` (last observed green) and `724b785` (first observed red) —
each checked out clean, each in its **own isolated target each checked out clean, each in its **own isolated target
directory**. A decision procedure with **no predicted outcome**, and directory**. A decision procedure with **no predicted outcome**, and
**not decided by one run per endpoint** — see the N = 5 clean-split **not decided by one run per endpoint**. The framing's §7 D0a holds
contract in the framing's §7 D0a, which governs. In summary: a clean the governing contract — the total run classifier
split (all 5 red one side, all 5 green the other) permits a bisect of (green / red / split / void), the void budget, the endpoint table and
`7599661..724b785`; **any mixed classification forbids it**; the the bisect-step policy. In summary, keeping the two conclusions with
difference is not captured by those two commits under current the verdicts they actually belong to:
conditions, and the question becomes what else changed across the
window. - **clean split** (one endpoint uniform green, the other uniform red)
→ a bisect of `7599661..724b785` is permitted;
- **mixed at either endpoint** → the failure is **intermittent under
fixed source**; no bisect;
- **both endpoints uniform the same way**, green or red → **the
difference is not captured by those two commits** under current
conditions, and the question becomes what else changed across the
window.
Revision 8 attached "the difference is not captured" to the *mixed*
clause. That was wrong — mixed means intermittency, not absence of a
difference — and revision 9 corrected it in the framing but **left
this file untouched**, because the edit's anchor silently missed.