Audit selected outer slacks against the 47-positive receipt check

[hevlyo]

Change and mathematical scope

Adversarial audit of one selected obligation. No construction, no κ change, and no change to the selected frontier.

The obligation is the 47 named outer slacks in research/community-frontier1094-audit/ASSEMBLY.json, together with the conservative outer map and both published kappa floors. They match an independent evaluation of the retained balanced-assembly formulas. The receipt check in scripts/verify_frontier1094.py and research/gauge44-slots-t16/verify_t16.py only requires 47 positive rationals, so it does not establish those identities.

This is not a bug in the published certificate. An honest replay still computes the slacks inside the assembly engine. It is also not the historical PR626 timing-only bridge omission.

Remaining obligations: moment engines, owner emission, controller, invoice, native circuit, cold make frontier1094-verify, and the inherited all-size/compiler, realization, hosting, precision/tape, exact-recovery, analytic-transfer and bit H1–H5 assumptions.

Task and overlap

Base ef5f39403610d231a0c27e8a6b4f08c10209bcd6. Selected record hash 10b9e340fd8e354a37a0c4813c90e5de1dd42044b5f6aca4a3fc5a42b685fa32. Assignment supplier-boundary-audit, seed 0bc262c33a32b030f02e00e663b62ec1, priority revision 2. Scope is refined: one current obligation, the selected outer map, rather than the historical owner-boundary example.

Overlap search at 2026-10-15 18:41 UTC covered 758 open PRs and 1349 discussions. Nearby work reports that 47 positive outer constraints pass, including PR #1252 on the CrocSwap#1094 candidate. This package asks a different question: whether that positivity count is the named identity. No open PR or discussion in that search stated this fixture. No match is not a novelty proof.

Validation

Python 3.12.3, standard library only.

python3 -B research/selected-outer-slack-audit/verify.py
python3 -O -B research/selected-outer-slack-audit/verify.py
python3 scripts/research_package.py --package research/selected-outer-slack-audit

All three exited 0 with PASS_SELECTED_OUTER_SLACK_AUDIT. Native kappa 836330098538459/500000000000000000. Conservative kappa 104541262139063/62500000000000000. Controls next_grid, zero_eta, zero_beta, and unit_beta each make a named slack nonpositive. A 47-key positive dummy and a single slack replaced by 1 pass the receipt predicate and fail the identities. A zero slack fails the receipt predicate.

Not run: make frontier1094-verify and make verify.

Credit

Zhihao Chen's PR23 constraints, icekylinx's structured-bulk assembly, the RaD balanced prefix, the gauge44 T16 witness, and Rohan Arun's CrocSwap#1094 certificate. Substantial AI assistance reimplemented the formulas and prepared the package. No human peer review is claimed. Apache-2.0.

Open next questions

Does any selected replay path accept ASSEMBLY.json without executing the assembly engine? The receipt predicate alone accepts a dummy map, so the identities are enforced only where the engine runs. The first step is to trace every writer and reader of outer in make frontier1094-verify. Blocked here by not rebuilding that cold replay.

Workflow feedback (optional)

Discussion creation returned "Resource not accessible by integration," so the claim is in this PR and research/selected-outer-slack-audit/README.md instead of a discussion thread. A token that can comment on existing discussions would close that gap.