P16 sync-every-two replication with complete audit
With full 2^32 exactness coverage, P16 synchronization every two launches reproduces the favorable signal of EXP-160.
Diagnostic work, exact algebra and local capabilities are not treated as end-to-end mining advantage.
What was tested?
With full 2^32 exactness coverage, P16 synchronization every two launches reproduces the favorable signal of EXP-160.
Why the test is meaningful
Correcting an invalid audit requires a fresh sealed replication; the earlier point estimate cannot be pooled or treated as prior evidence.
H_audit=67,108,864×64=2^32R_21=throughput(sync2)/throughput(sync1)promote iff R_21≥1.0001, CI95_low≥0.9995, retention≥0.999How it was tested
Repeat the frozen three-arm design on four new headers, correct audit repetitions to 64 and complete 24/24 balanced benchmarks.
What happened
All binaries found B32 nonce 3,842,969,478. Sync-two observed at 0.020290 s but reached 0.999878× versus sync-one, CI95 0.998655–1.001102, favorable on 3/4 and retained 0.999489 versus no-sync.
Exactness and statistical controls
Full 2^32 coverage, zero discrepancies, exact factors, 44 registers, zero spills and 24/24 benchmarks passed before timing interpretation.
What the result means
The invalid favorable signal did not reproduce. P16 sync-every-two is not promoted; P8-S0 remains default and P8-S1 remains an opt-in low-latency path.
Limitations
- The result is local to registered P16 geometry.
- It rejects promotion, not exactness.
- Other observability primitives require new hypotheses.
Evidence trail
Use 64 audit repetitions, verify the known B32 nonce in all arms and apply all three preregistered performance gates.
Canonical variants
CANONICAL-EXP-161PREREGISTERED-CAMPAIGNSEALED-AUDITSource: internally audited canonical reports. Local filesystem structure, private headers and operational identifiers are excluded from publication.