Repository navigation
Research: flag-43 head-step repair co-hosts at update 3364 with no added channel mass (no new kappa) - #3508
Merged
Mister-Meeseeks merged 2 commits intoOct 18, 2026
Conversation
… (no new kappa) Retarget nine published transports of Y59, D17, Y103 and D28 so that Y59's last update (event 3364, the ADD that settles X21's final coefficient) runs in a chart co-hosting basis head 15 while X21 is full and live. The published check_native.validate() passes on the repaired word with eight newly lowered edges. Events, ADDs, transport occurrences, rank mass and distinct edges are unchanged; the paid profile moves by -3H1+5H2-H3-H4, majorized by the published ranks. A two-register comparison (R1) costs one added transport. In the order-preserving zero-added-rank class, 3364 is the only head-hostable Y59 update and forces exactly these four registers.
This was referenced Oct 18, 2026
Mister-Meeseeks
pushed a commit
that referenced
this pull request
Oct 20, 2026
… two added rank units (no new kappa) Answer #3451's open question 1 for present-head flag 1 (X0 -> Y7, head 232) with two natively validated repaired words: R0 keeps the event order (+1 event, +1 transport, +2 rank on D17) and R1 relocates the delivering ADD into D17's full window (0 events, 0 transports, +2 rank on Y7). An exact least-frame sweep shows zero added non-private mass is infeasible for all six order-preserving Y7 updates and for 868 of 1,115 relocation slots, so +2 is the parity floor there. Method follows #3508; selected kappa unchanged.
Mister-Meeseeks
pushed a commit
that referenced
this pull request
Oct 20, 2026
Adds research/p104-flag43-side-correction-bill/. On #3508's R0, the (59,21) entry of I - G/2 (-1/2 X21 into Y59) is applied by four natively validated corrections at R0's terminal Y59 transport: target lift T (+1 transport, +1 ADD, +2 rank), source detour S (+2 transports, +2 rank), one private-copy lifetime P (+1 rank) and the whole Y59 row T48 (+48 ADDs, +2 rank, row becomes y59 + x59). In #3508's event-preserving class no placement of the correction ADD has zero added rank mass: events 625 and 884 force X12's head 131 into X21's frame, and 131 lies outside Y59's final hyperplane. The strict minimum is exactly 2, equal to the end-cut detour, so head co-hosting gives no rank discount. Selected kappa unchanged.
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 scope
Bounded follow-up under priority revision 6, card
p104-side-correction. #3456 shows that on present-head flag 43 (X21→Y59, head15) no publishedY59update co-hosts the basis head. This package answers its open repair question with a concrete changed schedule R0 and an exact channel bill.R0. Keep every published event in order with the same ADDs and coefficients. Retarget nine transports of
Y59,D17,Y103andD28(each changed frame = published frame plus15). Then event 3364 (Y59 += D17/4) — the ADD that settlesY59's finalX21coefficient1/2— runs in chart[95,447,6,32,20,15]whileX21is still live. The publishedcheck_native.validate()passes on the repaired word (eight native edges swapped for eight newly lowered ones; 280 framed rows, 72 dirty-helper restorations, 208 endpoint adapters hold).Bill. Events (4,058), ADDs (2,624), transport occurrences (1,410), rank mass (2,368) and distinct native edges (740) are unchanged. Paid profile delta
-3H1 + 5H2 - H3 - H4. Published ranks of the changed transports majorize the repaired ranks, so the delta is ≤ 0 under any convex per-rank price and exactly 0 under any affine one. Under a strictly concave per-rank price the same profile delta can be positive; that case is left symbolic.Obstruction (same class). Among repairs that keep event order and ADDs, keep endpoint frames and add no rank mass (inserted refinements allowed), 14 of 15
Y59updates are blocked; only 3364 is admissible and it forces exactly the four registers above. Comparison schedule R1 (reorder + one rank-1 lift) also validates natively at +1 transport.Scoped repair bill. No new kappa. Selected κ stays 0.001672660197076918. Does not reprint drop/arrive chronologies of #3456/#3451/#3443. Does not supply the
I − G/2side correction (still open).Result
Package:
research/p104-flag43-head-step-repair/.Tip:
69b13ac1f39d647c9375582541c5a30bc6419354.Content tip:
cc77db2b62d1eaa6a1f7b9ffec7e694a910bba54.Base:
6f100d4bb5083f8c35d96fd95a539811c62f245c.Validation
Expected:
Default verify is read-only. Admission uses
need()and still fires under-O.Overlap and credit
Closest prior: #3456 (flag 43 published obstruction; this answers its repair OQ). Cites #3451/#3443/#3392/#3349 only. Soft-overlap checked against open #3363 (relay census / coefficient convention reused; event-level delivery split recomputed only for co-hosting). Does not reopen #3441/#3436/#3421/#3411, deferred peeled-leaf/rho=0/V45, or the merged readout series through #2883.
Credit Nick Petalas / #2981, Chafik Boukhalfa (witness/checker/compiler), #3456, and #3363. Prepared by Wentao Li (VictorLiwentao, @Is__Victor) with substantial AI assistance, under Apache-2.0.