Repository navigation
Rule out identity from nested P104 transport refinements - #2136
Merged
Mister-Meeseeks merged 1 commit intoOct 15, 2026
Merged
Mister-Meeseeks merged 1 commit into
Mister-Meeseeks merged 1 commit into
Conversation
This was referenced Oct 14, 2026
This was referenced Oct 14, 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.
The P104 identity transfer remains impossible after arbitrary nested subdivision of every original transport interval, arbitrary interleaving and common-chart linear resynthesis. The source-to-target rank is at most 56 arrays: the 56 sources outside the span of the eight private-drop survivors can contribute at most eight arrays; the other 48 sources account for the remaining upper bound. Identity requires 104. This upper bound is not claimed sharp.
This closes a specific part of the changed-intermediate-frame handoff in #2113. Its fixed-path rank-eight bound does not already cover the newly admitted intermediate charts. The result also differs from #2127's added-storage theorem with retained unsplit transports: here the old occurrences may themselves be replaced by nested chains. Routes outside their original intervals, extra cross-chart transfers, branching/fusion and changed endpoint obligations remain outside the theorem. No native correction cost, supplier admission or new kappa is claimed.
Only
research/p104-nested-refinement-cut/is added. The proof colors a proper chart target-side when it lies in the survivor span or contains at least two survivor lines. All 1,402 upward intervals avoid a crossing under every monotone refinement; each of the eight downward lifetimes crosses once and carries one array. A transcript argument permits arbitrary common-chart mixing, feedback and fresh source-independent storage without multiplying the counted crossings. The README gives the model, proof, counterexamples, attribution and concrete next steps.Validation:
The scalar coefficients, original 280-column identity, native compiler, global hosting, precision and all-size/outer proof are inherited and are not replayed by this package. The generic transcript implication is written mathematics, not a proof-assistant certificate. Both independent implementations were prepared by the same author/assistant; no independent human review is claimed.
Credit Rohan Arun/#1972, Chafik Boukhalfa/#1991, Adam Gall/#1940/2090, Josie Elliston/#1071, Ali Romman/#1125, David Arias/#2082, Jeremy Diviney/#2113 and Ross Richardson/#2127. The earlier fixed-alphabet corroboration remains on a public fork branch without a competing PR. Prepared for Tairitsu-Aya with substantial OpenAI Codex assistance in mathematics, implementation, source reading and prose; Apache-2.0.
Task
p104-side-correction, explicitly changed scope from a construction attempt to a scoped obstruction. Scientific base is canonical main0fdd7d82de03e43c9e5a1000dfbcd380d1b687d2, priority revision 4. Canonical claim: #2113 (comment) . The selected frontier is unchanged. Exact task/overlap coverage and limitations are recorded inTASK.json.