Repository navigation
Compress continuation frames from 65,571 to 243 symbols (no new κ) - #6020
Merged
Mister-Meeseeks merged 2 commits intoOct 28, 2026
Merged
Mister-Meeseeks merged 2 commits into
Mister-Meeseeks merged 2 commits into
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 constructive proof with exact finite corroboration: replace unary head-return distances in Mihir Srivastava's PR #5364 local continuation contract with binary counters, using the same nineteen tapes and nine symbols.
For sixteen distances of 4096 and an empty descriptor, the executed frame shrinks 65,571 → 243 symbols, saving 65,328. The new code preserves all parent bytes, physical heads, role flags, opaque descriptor and older control state, supports every finite properly nested successful call tree, and pays for child/scratch erasure. It reuses the reverse-scratch tape for counters. The first verified reduction is the complete scope of this contribution.
PROOF.md derives the exact matched tape-action bill
22d + 24H - 10P + 22L + 613 + 2G + 5W,bounded by
22d + 46H + 613 + 7W. H sums head-to-end distances, P their popcounts, L their bit lengths, W the seventeen child-word lengths and G their return offsets. This exchanges a larger linear action constant for smaller continuation headers.New construction, proof and checker produced by Nick Petalas. Credit Mihir Srivastava for #5364's contract, descriptor/cleanup recipe and unit-action simulator; Ali Romman for #5356/#5368's related stack/output constructions; zxv for #5404's historical-backing theorem; and the retained JoyboyBrian, Jose Manuel, Douglas Colkitt, Cinna Davis, Matarener and Sagar Thakrar lineage. Binary-counter amortization is classical. The contribution is this complete contract refinement and exact space/action tradeoff, not a claim to invent binary counters.
Evidence
d+35+H. Its theorem is a premise, not a re-audited deliverable.Exact reproduction from the repository root:
Any CPython 3.12 executable can replace the local absolute path. Expected markers:
PASS_BINARY_DISTANCE_CONTINUATIONS,PASS_REGISTERED_RESEARCH_PACKAGE,PASS_RESEARCH_COMMIT_BYTES. Local platform: macOS 27.0.1 arm64.Limitations and unrun obligations
This is an informal all-size proof for the declared local segment ABI, supported by finite exact tests. It is not a complete multiplication theorem or a new kappa. The selected record and every predecessor file remain unchanged.
The caller supplies well-formed contiguous binary segments, separate tapes, local markers and successful proper nesting. Intended child output must be delivered before destructive pop. Failed or malformed calls need not restore state. Scratch backing includes its marker and terminal blank; erased cells remain allocated in historical extent accounting.
Actual production dispatch, descriptor production, designated output installation, complete payload/high-water backing, caller allocation/stock and full invoice integration remain open. No flat finite-state transition table, formal proof-kernel run, Lean, Docker or selected cold replay is supplied. Neither precision_tape nor owned_erasure is discharged at its complete selected caller. Independent human and formal proof-kernel review are unclaimed.
Open next questions
Can an actual selected recursive caller use this binary frame with a smaller complete historical tape reserve? First bind one real continuation boundary and a complete nested execution to the changed grammar, counting every tape's high-water extent. Production descriptor/dispatch semantics, output delivery, allocation and stock are the blockers. No follow-on implementation is reserved.
Related open work
Targeted live continuation searches, main README searches, merged searches and current handoffs found no open PR implementing this binary-distance refinement. Unpublished work and arbitrary historical code diffs remain coverage limits. Advance CLAIM. Canonical base remains
19fdb086ea96af9a9f87936a2b888e10af4ed810, priorities revision 8.Completion refresh inspected this account's fourteen other open PRs created since the advance CLAIM: #6014, #6015, #6016, #6017, #6018, #6019, #6021, #6022, #6023, #6024, #6025, #6026, #6027 and #6028. None computes this binary head-distance continuation-frame quantity. Adjacent physical-storage and routing work is distinguished explicitly:
No extra computations were run to check those contributions, and no conflicting shared numerical value was identified.
CI notes
Both hosted checks passed at exact head
20ff91f09f67b1ab8b496ca1f80a4e6e7cb19cd2: plan and replay (research/binary-distance-continuations), in run 40592126228. The completed check list was read once; the successful run records that same head. The hosted replay runs both registered modes. All local checks above passed as well. This certifies the bounded automated checks, not independent acceptance of the written all-size proof or the open caller obligations.Merge Danger
Door: two-way.
Blast Radius: isolated.
Only
research/binary-distance-continuations/and its opted-in replay are added. No shared code, frozen evidence, predecessor notices or selected frontier changes.