Measure World correction detection delay

[eamirian]

What changed

• freezes one real FCC Federal Register correction pair (2020-28779 -> 2021-10670) as a network-free recorded-replay fixture
• appends exact original/correction Observations and correction-handling artifacts without rewriting prior history
• records independent correction reviews as exact observed results, including linkage, corrected instruction, prior-record preservation, and detection delay
• compares a 300-second treatment with a 21,600-second delayed control under a World-owned 600-second criterion
• classifies the two matched pairs as useful and emits only a non-effective, non-selectable promote proposal
• adds fail-closed controls for pre-availability detection and invented scores, plus exact replay and fresh-host determinism
• records the bounded work packet, immutable audit evidence, and restrained candidate roadmap status

Why

ACE 0.6 needs product-owned outcome evidence beyond structural citation coverage and contradiction attention. This packet makes correction handling and detection delay inspectable through the existing domain-neutral Core + Intelligence measured-impact contracts while keeping FCC/Federal Register/source policy in World.

This is stacked on World PR #9 and the Core measured-intelligence stack (#88, #89, #90). It does not merge, release, apply the proposal, pass SI4, close Core issue #38, or claim ACE 0.6 complete.

Verification

• focused P2C3-P2C7: 15 passed
• full World suite: 98 passed
• connector suite: 26 passed
• release contract: 7 passed
• public ace-core==0.5.0 boundary: 82 passed, 16 explicit candidate skips
• scoped Ruff check/format and git diff check: pass
• package build: unchanged 0.9.0 sdist and 45-entry inert data-only wheel; no Python or entry points; ace-core>=0.5.0,<0.6 unchanged

Repository-wide Ruff remains an inherited blocker: 15 lint findings and 20 pre-existing format targets, unchanged from the P2C6 parent.

Claim boundary

The availability and detection instants are frozen replay coordinates, not observed network-arrival times. This proves one exact correction pair under one product rule; it does not prove live monitoring, population detection performance, calibration, revision stability, legal truth, causality, general Brief quality, or human benefit. The proposal is not applied.

Core issue #49 F1, F3, and F5 still need explicit 0.6 release-owner disposition; this packet does not expand scope to implement or re-date them.

[eamirian]

Superseded by the direct-to-main convergence in #17 and the published World Intelligence 0.10.0 release. The release lineage composes the P2C3–P2C10 work and preserves its evidence; this stacked draft is now closed for repository hygiene.