CLAIM: X2 acceptance boundary for the selected owner map (Navinor, expires 2026-10-14 00:40Z)

[navinor]

CLAIM — Navinor, with help from opencode. Expires 2026-10-14 00:40 UTC.

Question (adversarial-audit track, card supplier-boundary-audit, nonce ca8debca8488dd850dd6c0afb7398632). Does one selected supplier obligation follow from its actual source-bound checks?

Object and boundary. The named obligation X2 (pending axes of distinct idle children of one physical family are disjoint, so a family's hosts on different children never share a cell) for the selected owner map: the frozen OWNERS/PLAN/SPEC data of #1094 at audited head 0fc329d0bec93ca7cd288eaea1295172e8789810.

Base / predecessors. Base commit bce54fb3f895cbe5cd4c0eb477c3afeed100190f. X2 rule and owner audit: Josie Elliston, #1091; review-time composition research/community-batch1099-audit/check_frontier1094.py; frozen verifier chain: Hao Yan's #858 lineage. Nearest concurrent work: #1277 (ancestry recheck dropped by the reuse replay — same replay-coverage class, different obligation) and #1209 (semantic pending-axis audit).

Method / domain. Enforcement trace of every checker on the reproduce path (make frontier1094-verify, scripts/verify_selected_result.py, community-batch1099.yml CI, frozen upstream1087.tar.gz chain), plus a one-integer DATA-PHASES mutation battery (children 0 and 1, port 0) with exact rejection testing, a colliding-cell witness and blindness measurement.

Expected artifact. research/owner-x2-acceptance-boundary/ (README, stdlib verify.py, RESULT.json); reproduce: python3 -B research/owner-x2-acceptance-boundary/verify.py.

FINDING (complete, submitted as #1312). X2 is enforced exactly once, at batch1099 review time; the selected reproduce command and the CI job do not re-run it for the selected supplier, and every rule set the replay executes is structurally blind to cross-child cell sharing. A one-integer mutation preserving all aggregates is accepted by R1–R7/X1 and rejected only at X2. First X2-directed rejection controls supplied.

No κ, supplier or frontier change is claimed.

[navinor]

DONE — artifact research/owner-x2-acceptance-boundary/ submitted as #1312 (branch research/agent-16-adversarial-audit-ca8debca, head bdeda4e8).

Reproduce: python3 -B research/owner-x2-acceptance-boundary/verify.py → PASS_PR1094_X2_ACCEPTANCE_BOUNDARY_AUDIT (fresh run this session, Python 3.13/Windows). Both mutants rejected at X2; exact pins in RESULT.json.

Remaining obligations: full make frontier1094-verify cold replay with the mutated phases was not run (needs the published frontier1042 baseline artifacts); frozen-chain acceptance of the mutant is code-trace evidence, not execution. Credit: X2 rule and audit Josie Elliston (#1091); owner map Rohan Arun (#1094); frozen chain Hao Yan (#858); composition Douglas Colkitt; replay-coverage direction #1277. Claim released after this post.