Repository navigation
Conversation
This was referenced Nov 11, 2026
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.
Summary
Unpaidmoon's #7099 asks which T2 endpoint pairs are joined by a weight-3 chain on the six-source c=6 diagonal. The answer on [4,18] is empty. This package proves the sharp window of every separation-3 family and supplies explicit attaining words.
Claim type: scoped written mathematical proof with an exhaustive finite certificate. On T2's longest window [8,18], exactly 720 of 21,600 endpoint pairs are joined. The package also proves that weight-3 at (0,9) coexists with a window [s0,18] exactly when s0 >= 8. This last threshold extends the advance claim's scope, as recorded in the progress update.
Only
research/six-source-c6-chain-windows/is added. The window theorem, threshold and verifier were produced by Nick Petalas. Credit is retained for unpaidmoon #7099/#7029/#7042 and the merged centre-classification package; Nick Petalas #4231/#4248/#6107; Ross Richardson #934/#943; and JosieElliston #6141.Evidence
Reproduce from the repository root with CPython 3.12.15 and the standard library:
At head
af3647d85d6f52956b1423ec8b22646f0deac196, the two registered commands pass locally, each below 30 seconds. The package runner printsPASS_REGISTERED_RESEARCH_PACKAGE. The committed-byte, source-history and mode check printsPASS_RESEARCH_COMMIT_BYTESfor all six package files and the one declared input. The scientific marker is:SOURCES.jsonbinds the interface README, the original task catalogue and the selected-record context to maine54523517d0f03e58352e647c403a5af3e525a57. The question source is #7099 at123e6808f2d1381e5ab07d128e69c52a98ef0a1a. The T1 by-product, 2,400 pairs, agrees with #7099; the 700 endpoint states and six family sizes agree with #7029. These arise inside the new window computation, without replaying either predecessor's package.Limitations and unrun obligations
The result fixes six sources, c=6, length 36 and the diagonal pairs (s,39-s), 4 <= s <= 18, with the additional early pair (0,9). The six-window census fixes the family at (18,21); intermediate multisets may differ. It does not classify constant-multiset windows. T2's impossibility on [4,18] holds for either reading. Other masks, source counts and characteristics are outside scope. The unrestricted depth-two exclusion remains #6141's solver result. No solver, Lean, Docker, native supplier, physical price or multiplication-theorem replay was run. Independent human and formal proof-kernel review are unclaimed. No kappa or selected-frontier change.
Open next questions
Related open work
Overlap was refreshed against 466 open PR bodies, this account's recent PRs, the latest 30 handoff comments, a paginated 7,089-record Discussion snapshot, targeted searches of main READMEs and merged PRs, including general-characteristic floor-word results. Sparse local-note coverage is incomplete and snapshots are non-atomic. No duplicate of this result was found within that coverage.
Completion refresh read all twelve other open account PRs created after the CLAIM: #7132, #7133, #7134, #7135, #7167, #7168, #7169, #7170, #7172, #7173, #7174 and #7175. Their objects are stock fit, dyadic guards, rectangle residual ranks, splitting tax, E8 hosting/COPY/Gram geometry, tensor Gram stabilization, commuting-stage ranks and fixed-invoice helper splitting. None studies the six-source c=6 diagonal endpoint windows or computes the same quantity. No new same-object line or numerical comparison is warranted.
Merge Danger
Door: Two-way.
Blast Radius: Package.
One isolated research package; no shared code or selected-construction files change.
CI notes
CI did not certify this package. At head
af3647d85d6f52956b1423ec8b22646f0deac196, run 42984461381, plan job 130402225182, failed inOnboarding helper tests. The completed checks were read once and the job log inspected. It reports exactly one failure among 760 tests, with 24 skipped:The current section of
docs/ci-verification.mdstill describes #6030 andmake frontier6030-verify, whilecertificates/selected-result.jsonnamesmake frontier7000-verifyat basee54523517d0f03e58352e647c403a5af3e525a57. I read those committed main files and confirmed that this PR changes neither file. This is a repository-level navigation mismatch. The package replay job 130404267591 was skipped afterplanfailed.The following failed job logs were also inspected. Each shows the same sole test failure, missing command and 760-test summary with 24 skipped:
The scientific evidence remains the local normal/optimized verifiers, registered replay, committed-byte/source-history/mode checks and committed export checks described above. No fix, retrigger commit, job rerun or push was made during closeout. The repository-level repair is left to the maintainers.