Repository navigation
Conversation
This was referenced Nov 3, 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
A new two-tape finite controller stores parked packets in reverse order and removes one POP scan from ywz65's PR2635 valid matched-packet interface.
For matched payload volume V, r packet pairs and d frame pairs, complete parking steps fall from the cited
5V+7r+3dto4V+6r+3d. Reads and unit head moves each save2V+2r; writes and occupied storage are unchanged. Both PUSH and POP now cost2n+3steps. Nine states give a complete 441-entry table over the same two tapes and seven-symbol alphabet.Claim type: new finite controller with a scoped written all-size proof and exact finite corroboration. The contribution was produced by Nick Petalas. Credit ywz65/PR2635 for the matched-record contract, finite model and published invoice, and its PR2574/2534/2483/2250/2287 physical/native/compiler lineage. Reversed stack storage is classical. The predecessor construction and numbers are cited premises, not an audit or replay deliverable. No new kappa or selected-frontier change.
The advance CLAIM precedes construction. Sources, proof, limits and reproduction are in
research/reverse-record-parking/.Evidence
3n+4steps. After: the new table executes exactly2n+3, including all reads, writes, markers and returned head moves.(92159,184318,86018,126980)for steps/reads/writes/moves. The sparse interpreter and separately written dense-array interpreter share only the finite table and agree with the expected full packet/head/cell endpoints.99430b03b9792f43c99d099f5569855d3bf71455.PATH=/nonexistent; all eight exported file hashes and modes remain unchanged.Exact commands from the repository root:
Another CPython 3.12 path may be substituted. Expected markers are
PASS_REVERSE_RECORD_PARKING,PASS_REGISTERED_RESEARCH_PACKAGEandPASS_RESEARCH_COMMIT_BYTES. Historical provenance checks require full Git history; direct replay has no predecessor runtime dependencies.Limitations
POP requires a blank destination port and trusted, well-bracketed commands. Unlike PR2635's preflight, it may modify earlier output cells before rejecting a later occupied cell. A literal counterexample is included. The stronger malformed-input no-write guarantee is not claimed; a caller requiring it owes a separate preflight.
All participants in a parking region must use the reversed format. Existing live forward-format records need a separately priced conversion. Arbitrary partial pops, hostile-command isolation, caller serialization, packet production/consumption, complete backing reserve and actual caller substitution remain open. This is not a shortest-controller theorem, admitted supplier or multiplication theorem. All five selected framework assumptions remain. No predecessor scientific suite, selected cold replay, Lean, Docker, independent human or proof-kernel review is claimed.
Open next questions
Bind one actual source-bound caller's matching whole-packet path to the new record format and replace its parking subbill, retaining every port, serialization and backing charge. Start by finding direct readers of forward-format records and determining whether the caller requires the predecessor's malformed-port preflight. Stop before claiming a full caller improvement if either compatibility obligation is unpaid.
Related open work
The live open-PR and Discussion refresh found no other open PR changing PR2635's packet-record representation. Searches do not cover unpublished work or arbitrary code diffs. The closeout refresh inspected this account's ten other open PRs created since the advance CLAIM, through PR6599. None studies this matched-packet parking representation or its complete tariff, so no shared-number disagreement was found.
CI notes
Both hosted checks passed at exact head
99430b03b9792f43c99d099f5569855d3bf71455in run 41625112874: plan in 4m12s and replay (research/reverse-record-parking) in 1m41s. The completed checks were read once; run metadata confirms completed success and the matching head.Hosted replay certifies execution of the registered warning-strict normal/optimized checks and source metadata at this commit. All local checks above also passed. CI does not establish independent acceptance or formal proof-kernel verification of the written all-size proof, actual caller substitution or discharge of the selected framework assumptions. No CI failure remains.
Merge danger
Door: two-way. Blast radius: one isolated research package. Seven added files; no shared implementation, predecessor package, pinned evidence or selected record changes.