Repository navigation
P104 leak corrections: third-engine check of #6067/#6069 on PR6030, and a scalar-level witness on PR5907 (no new κ) - #6108
Merged
Mister-Meeseeks merged 2 commits intoOct 28, 2026
Conversation
…07 witness (no new κ) Left-kernel tracker reproduces PR6067/PR6069 on the selected PR6030 word (4,009 information-lost, 22 no chart-local combination, 2 erased); on PR5907 one class is legalized at the scalar level by a 7-field chart-local combination program, checked by direct simulation. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Result
Scoped exact result, no new κ. Selected record unchanged (PR6030, κ 0.003125804, main
721c03822).Priority first. On the selected PR6030 word, the questions PR6045 left open were answered first: combination
carriers in #6067 (apoursh), and rewritten or arbitrary post-cut edits in #6069 (jon314159). Both report the
4,033 PR5718-shape leak classes as 4,009 information-lost, 22 with no chart-local combination carrier, and 2
(cuts 13637/13639, helper 572) erased. I built this package without knowing about them and found the overlap only at
submission. So it is offered as:
audited at every leak-class cut against the exact field matrix, plus 300 brute-force small words). It gives the
same 4,009 / 22 / 2. Its 24 residual classes match P104: certify fixed-word carrier and endpoint exclusions (no new κ) #6069's
global_screen.survivorsclass for class (localcomparison).
usable combination, and 2 are erased. One class is legalized at the scalar level: cut after 13776, chart 1031,
helper 699, leak to role 149. The seven-field combination
696 − 698 + 699 − 700 − 702 − 767 + 792is zero inthe original word and equals
z − ℓin the split word. Reading it into 697, 698 and 700 directly after the cutlowers to 18 ADDs, 1 SCALE and 1 COPY, all chart-local. A plain simulator shows every outside-V output equals the
original exactly, and
zreaches roles 698, 700 and 702. PR6040's pairing test passes, and three perturbedprograms are rejected. So the PR6030 exclusion depends on the word, and the combination model is not vacuous on
real data. This is not a split proposal: native maps (including the overwrite COPY), lifetimes, cost and the
caller are unchecked.
Package:
research/p104-post-cut-information-loss/only.Reproduce
python3.12 -B research/p104-post-cut-information-loss/verify.py # PASS_P104_POST_CUT_INFORMATION_LOSS, ~17 s python3.12 -B scripts/research_package.py --package research/p104-post-cut-information-loss python3.12 -B scripts/check_research_commit.py --package research/p104-post-cut-information-lossPassed locally on macOS, CPython 3.12.14, in normal mode and in
-I -W error -Omode, plus the package-metadata andcommit-bytes checks. Codex ran a read-only adversarial review. It found no blocking issue and two minors: the audit
scope wording, now "every leak-class cut", and the physical legality of the COPY, now stated as unchecked. Hosted CI
was not consulted.
Scope and remaining obligations
zreaches aV-final role.
saving
ℓinto an owned field) or other injections.not cover cross-time cancellation on the 24 PR6030 residual classes; P104: exclude two non-carrier ADDs across helper572’s chart seam (no new kappa) #6088 excludes one two-ADD seam family there.
why the chart-1031 relation exists on PR5907 but not on PR6030.
Credit
apoursh (#6067) and jon314159 (#6069) published the PR6030 exclusion and the information-collision argument first.
Also credited: Nick Petalas (#6040 census, pinned unmodified), Matarener (#5994), flyingviper (#5718), Ali Romman
(#5599), DreamingOfClouds (#5907/#6030 words), and #6045 (
leakfix.py, pinned unmodified). Prepared forJosieElliston by Claude Opus 5.5 (Anthropic) via Claude Code, as one session of an unattended overnight run. No human
review. Apache-2.0.
🤖 Generated with Claude Code