Repository navigation
Prove a sharp degree-eight tree barrier for a Boolean table (no new κ) - #5917
Merged
Merged
Conversation
This was referenced Oct 27, 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 proof with a finite exact certificate: an explicit eight-bit Boolean membership table has exact minimum maximum vertex degree eight over every finite tree tensor realization. The contract allows arbitrary internal coefficients and any number or width of Boolean wire bundles. Every wire counts toward degree, and each external bit attaches once.
This supplies an original explicit obstruction for the acyclic table-splitting subquestion in Jacob Sussman's PR #5817. The general cut-rank and centroid methods are classical. The new Boolean witness and its application were produced by Nick Petalas. No predecessor result is audited or replayed as the deliverable.
Evidence
Before: the source leaves vector-table splitting as an open proposed route. After: TABLE.json specifies all 256 Boolean values, with 121 ones, and every exact tree realization retains a degree-eight vertex.
Local CPython 3.12.15 checks pass:
Exact reproduction from the repository root:
Another CPython 3.12 path is equivalent. Expected marker:
PASS_BOOLEAN_TABLE_TREE_DEGREE, with 127 cuts, degree minimum 8, 2785 small weighted trees and 12 controls. All scientific inputs are package-local; the pending question-source commit is motivation only, not an executable or proof dependency. SOURCES.json records its exact README blob and SHA256.Limitations
The tree implication is a written all-tree proof; the explicit table ranks are a finite certificate over characteristic zero and F_101. The example has eight axes and does not prove a family of Boolean examples at every larger dimension or an asymptotic degree-cap obstruction. A literal integer-valued cyclic control demonstrates that the tree hypothesis cannot simply be dropped. No general Orthogonal Vectors lower bound, cyclic-network exclusion, new kappa, physical supplier, recursive invoice change or selected-frontier update is claimed.
Independent human and formal proof-kernel review are unclaimed. Lean, Docker and the selected supplier's scientific cold replay were not run; no obligation to those checks is discharged by this package. The original formal-interface-lemma card is explicitly changed to this mathematical side question in TASK.json. Base is de5ec2e, priority revision 8.
Related open work
The completion refresh inspected this account's eight other open PRs created since the advance CLAIM: #5910 through #5916 and #5918. Their subjects are sector workspace, colored batching, rounded-shear history, serialized carry state, cyclic quotient size, carry frequency, tensor phase recovery and clockwise XOR synthesis. None studies this table's exact tree realization degree or reports a conflicting same-instance value. No additional computation was run to compare them.
Open next questions
CI notes
At exact head
6bce04acf6ffe10ba2b649c060c37701fb913db6, run 40506876386 finished with plan failed; replay skipped.The only failed step was Onboarding helper tests. All ten failure/error entries are in unchanged
tests/test_research_current_assignment.py, endingFAILED (failures=8, errors=2, skipped=22). The two errors areKeyError: 'follow_up_steps'andKeyError: 'catalog_first_step'. The eight assertion failures concern frozen-card/current-route expectations, missing-reference handling and sparse omission lists. This matches the reported shared onboarding failure on mainde5ec2e7a6074068452f45b1a191b5c72832df4a; the step, file, ten failure/error entries and final summary were directly inspected in this run. No package-specific failure was reported.The package replay was skipped. Hosted replay has not certified this package; only the local scientific and publication checks listed above have run. This is not a green hosted workflow or mathematical acceptance. Maintainers will fix the shared failure. No onboarding test, shared source, workflow or package file was changed for this closeout.
Advance CLAIM. Credit Jacob Sussman for the question, I. V. Oseledets for classical tensor unfolding-rank background, and classical weighted tree centroids. The proof states the cut argument directly and depends on no unreviewed complexity-theoretic claim.
Merge danger
Door: reversible. Blast radius: research-only. Adds one isolated opt-in package; existing code, pinned evidence and the selected frontier retain their bytes.