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

docs(framing): remove the last three contradictions in revision 10 

Three statements survived the narrowing and contradicted it, plus one
ellipsed path in the supposedly exact command block.

  - §4b's heading still read "the source hypothesis is eliminated" ---
    the exact claim the section body withdraws. It now reads "the
    commits do not discriminate today".
  - §4a said the endpoints settle whether 7599661..724b785 contains a
    regression. They do not: they settle only whether a BISECT IS
    CURRENTLY JUSTIFIED. Those are different questions, and D0a's
    both-uniform-red answers the first while leaving the second open.
  - §4b claimed execution "under the approved contract" while the same
    revision acknowledges uptime was never captured. The departure is
    now stated up front, before the results rather than after them:
    uptime is UNKNOWN for all ten runs, everything else held, no
    classification depends on the missing field, and D1/D2's harness
    must capture the full list.
  - The manifest's <TD> definition still abbreviated the second target
    directory as .../d0a-B inside a block labelled exact. Both paths
    are written out; no ellipsis remains in it.

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 13:45:55 +02:00
parent 5f5fde6dde
commit e82bff71fe
No known key found for this signature in database
2 changed files with 15 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
docs/gpu-probe-sigint-framing.md
View File

@ -274,9 +274,11 @@ distinguishes:
`724b785`.
And an older ancestor outside the interval behaving badly is simply
**irrelevant** to whether `7599661..724b785` contains a regression —
that question is settled by the endpoints themselves, under the N = 5
clean-split contract in §7 D0a. (Revision 6 wrote "needs only that the
**irrelevant** to whether `7599661..724b785` contains a regression. The
endpoints, under the N = 5 contract in §7 D0a, settle only **whether a
bisect is currently justified** — not whether the interval contains a
regression. Those are different questions, and D0a's outcome
(both-uniform-red) answers the first and leaves the second open. (Revision 6 wrote "needs only that the
two clean endpoints differ *now*", which is the superseded one-run
rule; a bare difference decides nothing.)
@ -284,12 +286,17 @@ rule; a bare difference decides nothing.)
move**, as endpoint reproduction — which is a decision procedure, not a
prediction.
## 4b. D0a result — the source hypothesis is eliminated
## 4b. D0a result — the commits do not discriminate today
Executed 2026-08-19 under the approved contract: 10 runs,
Executed 2026-08-19 under the approved contract **with one departure,
stated up front**: the contract's captured-conditions list names
`uptime`, and the harness kept only the load averages from it. `uptime`
is therefore `UNKNOWN` for all ten runs. Everything else held — 10 runs,
counterbalanced `A B B A A B B A A B`, N = 5 per endpoint, clean
detached worktrees, isolated target directories, `dirty=0` verified per
run. **Zero voids, zero splits.**
run, **zero voids, zero splits** — and no classification depends on the
missing field, so the verdict stands. D1/D2's harness must capture the
full list.
**A (`7599661`) uniform-red. B (`724b785`) uniform-red.** By the
endpoint table this is *both endpoints uniform the same way*: the

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

@ -181,8 +181,8 @@ precondition then the `sweep-crdt` command. `dirty=0` verified per run.
**Exact commands.** Every run, in full. `<WT>` is
`/home/jeans/Repos/personal/pmacs-d0a-A` (detached at `7599661`) or
`/home/jeans/Repos/personal/pmacs-d0a-B` (detached at `724b785`);
`<TD>` is `/home/jeans/build/pmacs-gate-targets/d0a-A` or `…/d0a-B`
correspondingly:
`<TD>` is `/home/jeans/build/pmacs-gate-targets/d0a-A` or
`/home/jeans/build/pmacs-gate-targets/d0a-B` correspondingly:
```
env TMPDIR=/home/jeans/build/pmacs-gate-targets/tmp/d0a \