Repository navigation
Research: audit corrected P104 dual precision and private erasure - #2549
Merged
Mister-Meeseeks merged 1 commit intoOct 16, 2026
Merged
Mister-Meeseeks merged 1 commit into
Mister-Meeseeks merged 1 commit into
Conversation
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
Add
research/p104-clean-dual-precision/, an exact all-cut precision and private-erasure audit of the complete zero-restored corrected P104 dual.A sufficient 17-bit state-relative guard follows only with residual-tolerant disposal. Ideal zero restoration does not admit rounded strict-zero erasure automatically. Allowing sign defects has separately checked coefficients in the receipt. This is an interface audit, not a new corrected word or a supplier.
Card
p104-side-correction, priority revision 4, explicitly changed to the precision/lifecycle obligation left open by the completed word. Scientific base is0fdd7d82de03e43c9e5a1000dfbcd380d1b687d2.Credit ywz65 / #2497 at
7f2cf129d42030d3eb3975b7d1b07392c6d32a1bfor the exact 4982-event word and #2503 at6ea94fa4e547a2038deb3aa2064f6d4e4caa5bf5for the different original-dual precision precedent; Adam Gall / #2096 atf22626f334a06f6e842766e4a6647419e6821d2dfor the Hilbert-defect method; and #2458 plus the retained P104 lineage. The source word is preserved byte-for-byte, with exact pins and full credit in the package.Tested artifact
Evidence
After: with D31 initially a unit vector, a permitted rank-seven return defect at event 1825 leaves a nonzero collector at the erase boundary. This does not contradict the predecessor's exact theorem.
Checked with CPython 3.12.15 on Linux x86_64 / WSL2. Native unitary correctness is inherited from the pinned realization. No actual rounded child, strict-zero physical disposal, global invoice, remaining 102 corrections, all-size compiler, full selected cold replay, supplier or new kappa is supplied. The guard is sufficient, not a precision lower bound.
Merge Danger
Door: two-way
Blast Radius: research
Only this opt-in audit package is added. Selected records and frozen source inputs are unchanged. Residual-tolerant disposal must remain beside the feedback bound; deleting that premise would overstate the result.