RQ2-P3 STEP 2: run confirmatory battery OFFLINE + DETERMINISTIC — RESOLVED MIX
Operator-authorized (D1: freeze + run). New harness analysis/rq2p3_confirm.py
runs the frozen §4 battery entirely offline: all 9 sweep cells (B∈{2,4,8} ×
alpha∈{0,1,2}; B=50 anchor excluded) × R=30 × C=50 = 13,500 bridged circuits.
RQ2 entropy is analytic and pool bridge assignment is deterministic from the
seed, so no engine, no traffic, no grid, $0 — the same offline reconstruction
path confirm_load_rq2 uses for the lead RQ2. Seeds per frozen §6: run =
derive_seed(S0=20260719 ‖ cell_id ‖ run_index), per-circuit = the live
executor's real _circuit_seed rule (byte-identical). The frozen instruments
(stats.py, confirm.py, confirm_load_rq2.py, assembler.py) are UNCHANGED — the
only new code is seed enumeration, run-as-unit grouping, and an OLS-slope helper.
Frozen §8 analysis (effect + BCa 95% CI, never a bare p; 10,000 resamples;
α=0.05; run-level cluster bootstrap):
H1 pooled Spearman ρ(c_i,H_i) = +0.6244, CI [+0.5941, +0.6545] -> mix
H2 OLS dose-response slope = +0.7052, CI [+0.6195, +0.7903] -> mix (n=270)
H3 joint -> RESOLVED = mix (both exclude 0, agree in sign)
Holm over own family {H1-pooled, H2-slope}, size 2: both reject.
Honest disclosure (as commanded): the §7 dry pass already previewed this mix
(ρ 0→+0.838); the battery quantifies an effect already visible at calibration;
the two-sided pre-commitment stood. The +ρ MIX qualifies/corrects the lead
RQ2-P1 "shrink" headline as a unique-bridge artifact — a shared finite bridge
pool RAISES the per-circuit anonymity set, the opposite of the naive funnel.
That correction is the finding, reported openly. The lead RQ2-P1 result is NOT
re-litigated; any pool ΔH is exploratory (prereg §1).
Sealed immutably under output/ (gitignored → anchors force-added):
rq2p3-confirmatory-results.json (SHA-256 5fdcb379d8a2…) + SHA256SUMS;
byte-identical on re-run. Both prereg SHAs verified intact (lead f22331a72e…,
RQ2-P3 8db4e8a7ac60…). Tests: tests/test_sor_rq2p3_confirm.py 7 passed; full
SOR suite 201 passed, no regression. Defensive-measurement instrument only;
worktree-only on feat/sor-consent-relay.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -98,3 +98,7 @@ RQ2 RATIFIED (operator Andre, 2026-07-20, while blind) — observation-consisten
|
||||
- HOLDING — awaiting operator freeze/GO. Both build tracks complete; both confirmatory tracks blocked on HUMAN gates: RQ2-P3 battery → §10 freeze SHA-256; RQ3 battery + live added-latency → operator-GO + live isolated-docker grid. Standing down: no new stones, no speculative results, no confirmatory work until the operator delivers freeze/GO.
|
||||
- 2026-07-21 OVERSEER COMMAND (operator-authorized: Andre delegated per-gate command authority 2026-07-21, "make a command decision for each and proceed"). THREE command decisions recorded: **D1** — RQ2-P3 prereg → FREEZE NOW + run confirmatory battery. **D2** — RQ3 companion → GO on live confirmatory battery, grid permitting. **D3** — paper structure → ONE COMBINED companion paper (RQ2-P3 mechanism-correction is the LEAD section — the frozen-detector method caught the lead RQ2-P1 "shrink" as a unique-bridge artifact; RQ3 churn-resilience is the second half; Holm-7 over the full family is authoritative, supersedes the lead's partial embedding). NOT split into two papers.
|
||||
- STEP 1 DONE — RQ2-P3 prereg FROZEN. §10 filled (FROZEN 2026-07-21; APPROVED BY Andre delegated, executed by overseer; POOL/SKEW LOCKED B∈{2,4,8}, alpha∈{0,1.0,2.0}); no hypothesis/param changed (design LOCKED, §7 re-word already at 7ab3466 — froze AS-IS). SHA convention mirrors the lead (full-file sha256sum in a sidecar, not embedded inline → no self-referential fixpoint). **RQ2-P3 PREREG SHA-256: `8db4e8a7ac60f8b2861f2387249db68a3fd44822f6b3d9c7c6990ff65f261a3b`** (sidecar `docs/rq2p3-mechanism-prereg.sha256`). Re-verified LEAD prereg SHA `f22331a72e0d0ccf38b787e63acabbe9d666456ec76076787a6d545c3193425b` STILL intact (recomputed — has not moved). NEXT: STEP 2 (run RQ2-P3 confirmatory battery, offline+deterministic).
|
||||
- STEP 2 DONE — RQ2-P3′ CONFIRMATORY battery RAN, OFFLINE + DETERMINISTIC (`analysis/rq2p3_confirm.py`, new harness; frozen `stats.py`/`confirm.py`/`confirm_load_rq2.py`/`assembler.py` UNCHANGED). No live docker/traffic/grid, $0 — RQ2 entropy analytic + pool bridge assignment deterministic from seed (same offline path confirm_load_rq2 uses for lead RQ2). ALL 9 §4 cells (B∈{2,4,8}×α∈{0,1,2}, B=50 anchor excluded) × R=30 × C=50 = 13,500 bridged circuits. Seeds per frozen §6: run=derive_seed(S0=20260719‖cell_id‖run_index), per-circuit=executor._circuit_seed (byte-identical to the live executor's real rule). 10,000 BCa resamples, α=0.05.
|
||||
- **RESULT — RESOLVED MIX (§8 H1∧H2 agree +, both exclude 0).** H1 pooled Spearman ρ(c_i,H_i), RUN-LEVEL cluster bootstrap = **+0.6244**, 95% BCa CI **[+0.5941, +0.6545]** → mix. H2 OLS dose-response slope (per-run mean-H on per-run mean top-3 conc, 270 clustered pts) = **+0.7052**, 95% BCa CI **[+0.6195, +0.7903]** → mix. H3 joint **RESOLVED = mix**. Holm over own family {H1-pooled, H2-slope} (size 2): both reject (p_adj=0). Effect+CI reported, never bare p.
|
||||
- HONEST DISCLOSURE (as commanded): the §7 dry pass already PREVIEWED this mix (ρ 0→+0.838); the battery QUANTIFIES an effect already visible at calibration; two-sided pre-commitment stood. The +ρ MIX plainly **QUALIFIES/CORRECTS the lead RQ2-P1 "shrink" headline as a unique-bridge artifact** — concentration RAISES anonymity (shared bridge = mix), opposite of the naive funnel. That correction IS the finding. Lead RQ2-P1 NOT re-litigated; pool ΔH would be EXPLORATORY (prereg §1). Both prereg SHAs intact.
|
||||
- SEALED IMMUTABLY: `output/sor-rq2p3-confirmatory/rq2p3-confirmatory-results.json` (SHA-256 `5fdcb379d8a2…`) + `SHA256SUMS`; `/output/` gitignored → anchors force-added into the STEP-2 stone. Byte-identical on re-run (determinism verified). Tests: `tests/test_sor_rq2p3_confirm.py` 7 passed; full SOR suite 201 passed (no regression, frozen instruments untouched). NEXT: STEP 3 (RQ3 confirmatory — re-probe grid, launch live if up).
|
||||
|
||||
Reference in New Issue
Block a user