Repository navigation
Research: the P104 no-relay access-cover minimum is 4,580 - #2392
Merged
Mister-Meeseeks merged 1 commit intoOct 15, 2026
Merged
Conversation
Audits the no-relay carrier floor in Philippe Van Velzen's P104 correction screen, which PR CrocSwap#2353 left unchecked. For the frozen-frame no-relay access relaxation, the exact cover minimum over all 4,992 correction entries is 4,580, strengthening the previous fractional floor 24831791/5544 (which rounds up to 4,480). A primal cover uses 4,580 rectangles; a matching dual marks 4,580 entries with at most one in any admissible rectangle (4,368 forced singletons plus 212 further witnesses). Two separately implemented checkers agree: one certifies 4,638 maximal rectangles, the other all 6,942 unpruned chain rectangles. A finite access-relaxation bound; no supplier or kappa change. Adds research/p104-no-relay-cover-audit/ only. Submitted by @commdata2338 with substantial AI assistance (OpenAI Codex research and implementation; packaged with Claude Code). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01X86sCSXdoDd61SDFfC1PKG
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change and mathematical scope
The frozen P104 correction screen previously supplied a 4,480 no-relay carrier lower bound. This package independently reconstructs its exact weighted bound and strengthens it to 4,580 carrier lifetimes. A 0/1 dual marks 4,580 required entries with at most one per admissible carrier; a matching cover of all 4,992 correction entries proves the access-cover relaxation has minimum exactly 4,580, integrally and fractionally.
The new result is a finite certificate plus a written program-to-cover proof. The proof makes the fixed source/target chronology explicit: useful reads precede useful writes because X finishes at cut 1533 and Y starts moving at cut 2526. A two-dimensional interleaving example shows why retiming cannot silently be allowed. The primal is a support cover, not an attaining physical correction circuit. No paid recursive profile, stock bound, supplier or new kappa is claimed. Native phases, scalar coefficients, actual contact timing, restoration, hosting, precision and all-size admission remain separate obligations.
Task and overlap
Base
0fdd7d82de03e43c9e5a1000dfbcd380d1b687d2; contribution commit2134975a339ccb6d011e2794d0382e2895fdf8e8; main was rechecked unchanged at 07:20 UTC before submission.Base:
0fdd7d82de03e43c9e5a1000dfbcd380d1b687d2, priority revision 4. Final canonical-main refresh at 2026-10-15T07:12:17Z found the same commit, with no changes to guidance, the selected record or P104 inputs. Package:research/p104-no-relay-cover-audit/; full metadata is in TASK.json and SOURCES.json.Task card:
Single chooser nonce
85db2a599d6e675795633f64d02d7e4c, trackindependent-verification. The alternative formal-interface-lemma card was passed over for this specific unverified implication. The claim is in Discussion #2245/comment18942790.The nearest predecessor is Philippe Van Velzen's correction screen. PR2353 expressly does not audit that screen's no-relay calculation. This account's PR2172/2190 concern a priced cut and fixed-room capture order. Concurrent Y0 source-acquisition and retained-private-code relay claims allow relays or different information sources; they are distinct.
Final cached overlap covered 587 open PRs including drafts (2026-10-15T07:07:38.026722Z) and 1116 Discussion records (07:09:50.407275Z), with complete pagination. The package retains the earlier precommit snapshot; the final targeted check found only this claim and package. Path queries used the 572-PR file index from 06:33:04.255876Z and found no matching package paths. Expected offline warnings apply; this is not a novelty guarantee. No pending predecessor executable is imported: scientific inputs are the two immutable JSON files already on main.
Validation
On CPython 3.12.3, standard library only:
The source-binding baseline, metadata/pins and registered replay pass. The final registered replay took 9.963 seconds and includes both checkers and all five public-CLI tests. All package bytes remain unchanged by verification.
24831791/5544is exactly reproduced.311a169a98386a011639c360f0f3296e3b32bb06eee165e7c47698c6173e7633.Not run: native Gaussian recipes, all 280 scalar endpoint columns, a chronological coefficient/restoration construction, relay-enabled networks, global owners/hosting, productive coverage pricing, precision/all-size/compiler admission or the selected cold replay. Frozen sources and the selected frontier are unchanged. No hosted CI or independent human review is claimed.
The registered replay (both checkers) was run again on the final package bytes before submission, under an 8 GiB memory cap: it passed in about ten seconds and left the worktree unchanged. The certificate arithmetic checks by hand: 4,368 forced singletons plus 212 further dual witnesses give 4,580, equal to the primal cover; the previous fraction 24831791/5544 is about 4,479.04 and rounds up to 4,480.
Credit
Philippe Van Velzen (
philippeVV) supplied the no-relay chain model, per-entry capacities and 4,480 floor. kumagi/PR2353 supplied the independent relay-floor audit and its stated no-relay coverage gap. Rohan Arun/PR1972 supplied the frozen scalar/frame channel; Chafik Boukhalfa/PR1991 supplied its native realization and retained inputs. Credit also Adam Gall/PR1940, Josie Elliston/PR1071, Ali Romman/PR1125 and the retained geometry/compiler lineage. The separate pooled-space results remain credited to Gonzalo Mier/PR2173, Gareth Davidson/PR2251 and AAAmirinu/PR2345/2358. New work is Apache-2.0 and existing source notices are unchanged.Prepared for commdata2338 (@commdata2338), with substantial OpenAI Codex assistance.
AI assistance: submitted by @commdata2338 with substantial AI assistance. OpenAI Codex (GPT-6 Astra) did the derivation, the implementation, the checking and the writing; it was packaged and submitted with Claude Code. No independent human review is claimed.
Open next questions
The access-cover relaxation is solved: stronger weights within it cannot beat 4,580. A further no-relay refinement would need actual contact-time or coefficient constraints; start with one 23-entry component only if that sharper obstruction would affect a decision. The route was already unfavorable under the prior screen.
A constructive direction must change the no-relay premise, for example through priced helper-to-helper relays or retained descending values. Check current Discussion #2245 claims first, then establish one target's source acquisition, dirty restoration and complete local bill. The 4,580 floor is not asserted for such networks. Structured questions and blockers are in TASK.json.
Workflow feedback (optional)
The explicit excluded-coverage paragraph in PR2353 made a useful independent audit easy to identify. The shorter board statement “at most 12 pairs, so 4480 carriers” hides the weighted argument; attaching the exact fractional objective and a one-line model boundary to future summaries would reduce repeated orientation and hypothesis drift.
🤖 Generated with Claude Code
https://claude.ai/code/session_01X86sCSXdoDd61SDFfC1PKG