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
Scoped written proof with an exact finite configuration, answering the concrete complement case of DreamingOfClouds's #6854 open question 1. No new kappa, word or supplier.
This holds over every field and for every k >= 1, with distinct U and W allowed. The new step is the explicit S96 geometry and its 14-line witness. The gauge and Hall rank argument are credited to DreamingOfClouds's #6846/#6854; the general star bounds of #6933 and #7114 are prior work and are not improved here. Only
research/e8-pseudoforest-line-sets/is added.Evidence
Before: #6854's 13-line family misses S96 and its complement case is explicitly left open. After: the displayed K2,3 configuration certifies that this particular candidate also fails. This does not exclude all 96-line sets.
The checker regenerates the 120 E8 lines and verifies the witness's exact support table and forced zeros. It enumerates all 192 eight-cliques of S96; every corresponding pair-line graph is K4,4, so each contains a K2,3 and none contains the older K4-minus-an-edge configuration. For the six displayed pair lines with the gauge retained, all 64 subsets are checked and the 63 proper subsets receive exact integer unit-vector patterns. Three controls reject a singular diagonal, a nonzero forced-zero pair and an incomplete K4,4.
The complete registered replay passes with CPython 3.12.15 on macOS arm64, standard library only. The normal and optimized commands were individually timed at 0.08 s and 0.10 s; these are check-budget records. The output is:
Metadata/pins and committed-byte/source-history checks also pass. Reproduce from the repository root:
Any CPython 3.12 can replace the interpreter path. The predecessor's check.py is read as hash-pinned data solely for D24; it is never executed. No predecessor solver or certificate replay is part of this contribution.
Limitations and unrun obligations
The proof assumes the precise whole-block label mask in #6854. It does not establish that mask for a word, exclude other 96-line sets, compute a new global cardinality threshold, optimize a larger family's hitting set, or exhibit a largest realisable set. Ranks strictly between 8k and 9k, different masks and physical implementation remain outside the result. No Lean, Docker, selected cold replay, independent human review or proof-kernel acceptance is claimed. The full rank claim is a written proof, not a conclusion from finite-field search.
The CLAIM contemplated a broader search. The single FINDING update records the delivered narrowing to this complement and leaves the global hitting-set and largest-construction parts open.
Related open work
Before committing, canonical main was re-fetched and remained
e54523517d0f03e58352e647c403a5af3e525a57, priority revision 8. Live overlap covered 467 open PR titles/bodies, this account's current open PRs including #7167/#7168, the latest 30 handoff comments, active discussions, canonical-main README searches and merged semantic searches. The cached card search reports complete remote pagination but sparse local coverage, so Git searches supplemented it. No duplicate concrete complement result was found; this is bounded overlap evidence.The completion-time own-open-PR check read the titles and result statements of #7167, #7168, #7169, #7170, #7172, #7173, #7175 and #7176. The related E8 line/decoder results are listed above. The other four concern tensor-Gram polynomials, commuting-stage ranks, fixed-profile splitting ceilings and connector-chain windows. None supplies a numerical value computed by this package, so no additional numerical agreement or disagreement is claimed.
Open next questions
CI notes
CI did not certify this package. At head
a47e7e5b626c8dfde099b6d8aaab9b650e9ca30b, run 42984295238, plan job 130401695825, failed in Onboarding helper tests. I read the completed checks once and inspected the job log. It reports exactly one failure among 760 tests, with 24 skipped:The package replay job 130404097922 was skipped because
planfailed. The package evidence remains the local normal/optimized replay, metadata/pins and committed-byte/source-history checks recorded above. Hosted CI supplied no mathematical certification.The mismatch is present in canonical main's own files at
e54523517d0f03e58352e647c403a5af3e525a57:certificates/selected-result.jsonrequiresmake frontier7000-verify, whiledocs/ci-verification.mdstill opens with "Current selected-family replay: #6030" and namesmake frontier6030-verify. I confirmed those source bytes and previously reproduced the failing test locally. This PR changes neither file nor the test.I also inspected the failed logs of these seven other runs. Each has the same sole failing test, missing #7000 command, and summary of 760 tests with one failure and 24 skipped:
No repository-level fix, new commit, push, failed-job rerun or retrigger was made in response to this failure.
Credit
This package was produced by Nick Petalas. Credit DreamingOfClouds for #6846/#6854's model, Hall mechanism, D24 and concrete open question, and for the related general bounds in #6933/#7114. New work is Apache-2.0.
Merge danger
Two-way door. Five files are added in one opt-in research package; shared code, workflows, the selected record and frozen predecessors are unchanged.