SS5: adversarial review of the filled paper — 1 mechanism defect fixed

Self red-team of the SS4-filled lead paper against the sealed SS3 results
(no new statistic, no raw-data touch, frozen prereg untouched). Documented in
docs/stage-08-adversarial-review.md.

PASS: number fidelity (every §5 figure matches stage06-results.json), Holm
arithmetic (family=7, multipliers 7/6/5/4, only RQ1-P1+RQ2-P1 survive @ .05),
spin/over-claim (no-leak framing for the below-chance AUC, honest-negative
reported with equal prominence, lab-scope disclaimers), blinding integrity
(§5-6 filled once post-seal), method faithfulness (bit-faithful --verify).

Defect fixed (prose only, ZERO numbers changed): RQ1-P1's marginally
below-chance AUC was incorrectly attributed to a bridge "padding stream
flattening" the profile. assembler.py sets padding_applied=(bridge==
"on+padding"), so the RQ1-P1 bridge-on NO-PAD arm carries no cover stream.
Corrected docs/stage-06-analysis.md and paper §5.2/§6 to state the offset is
an unexplained pooled-correlator artifact, explicitly not a padding effect.
Point estimate, CI, gate decision, and Holm outcome are unchanged.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
leetcrypt
2026-07-21 01:02:02 -07:00
parent f4e1975daa
commit 9d0dc5c183
4 changed files with 74 additions and 14 deletions
+5 -3
View File
@@ -60,9 +60,11 @@ this note would carry a `NEEDS-OPERATOR` banner and **no** AUC would be reported
(RQ1) is **not** supported. The correlator does not link entry↔exit segments
better than chance on the instrument's bridge-on traffic; it sits marginally
*below* chance. Rejecting the two-sided null at AUC = 0.5 in the low direction is
an artifact of the pooled correlator on this as-instrumented traffic (the bridge
hop's R1 padding stream flattens the linked-pair temporal profile), **not** a
linkability finding. We report **no measurable leak**.
an artifact of the pooled correlator on this as-instrumented traffic, **not** a
linkability finding. (Note: this is the bridge-on **no-pad** arm —
`padding_applied = (bridge == "on+padding")` in `assembler.py`, so **no** cover
stream is present here; the below-chance reading is an unexplained correlator
artifact, not a padding effect.) We report **no measurable leak**.
### Method note — RQ1-P1 CI is method-faithful, not method-substituted