Repository navigation
Bind length-22 census receipts to the derived split domain - #4871
Merged
Mister-Meeseeks merged 1 commit intoOct 23, 2026
Merged
Conversation
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
Add
research/f7-l22-receipt-domain/, answering #4221 Open next question 2 without editing frozen packages. The successor checker independently reimplements #3708's necessary-condition arithmetic instead of trusting a copied eleven-split table, then binds the derived domain to four completed prior receipts plus seven deep receipts.It checks unique split identity, completion/hits, 251-prefix coverage, recorded totals and exact source identity, with adversarial acceptance controls. No giant census, engine-soundness proof, newly established f(7)=24, new κ or selected-frontier change.
Task and overlap
Card
census-pruning-audit, refined to acceptance-domain binding. Scientific baseb58ad9ef4d4e861b0eaa5dba41742bdc072dca51, revision 7. Exact source pins in SOURCES.json. Nick Petalas's #4221 head9d21222c67ecd40f49935a1e56b11f2b50d54613and #3708 headba1aff20ee3ce3dce35e4978feab0b6be08c7168are credited predecessors.Canonical main remains
624de9dc66858af0945e5f8a0942488d62280d43; guidance, selected record and scientific inputs are unchanged. Publication-time overlap refresh at 2026-10-22 22:27 UTC covered 392 open PRs, 3,875 Discussion records and all 5,862 tracked notes in the searched worktree. Exact-term matches were predecessor/own notes; neither publication branch had an existing PR in an all-state head lookup. Separate all-state title/body searches checked differently named contributions. This is not proof of novelty. Discussion post failed; no public reservation is claimed.Validation
CPython 3.12.13, standard library:
Metadata and registered normal/-O runs pass:
domain=11 prior=4 deep=7 controls=30 no_census_replay. The historical node sum 173,808,188,827 is authenticated recorded evidence, not freshly executed work. No C compilation, giant census, Lean build or selected construction replay. Separate read-only AI review found no blocking mathematical or acceptance defect; no independent human/formal endorsement.Committed-byte/source-history preflight, deterministic package export integrity, and a Git-free cold export replay in normal and optimized modes also pass. The refreshed canonical launcher reproduces the same acceptance result.
Limitations
The explicit engine hash binds the seven deep rows. Prior receipt engine provenance is retained history, and three prior-complete rows are unsharded control runs rather than per-shard logs. Necessity proofs and engine soundness remain inherited.
Credit
Retains Nick Petalas, Ross Richardson, Aaron Wang, Nicholas Stone, navinor and the predecessor lineage named in README. Prepared for codyw912 with substantial OpenAI Astra assistance and separate AI review; Apache-2.0.
Open next questions
Open next questions are independently replaying the deep exclusions and formalizing the pair-identity/rotation implication, each separately scoped and budgeted. No devenv or agent configuration is included.