Repository navigation
Conversation
This was referenced Nov 12, 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
Prove one diagonal sign conjugacy for every independent real body-sign profile of the fixed 20-factor Type A circuit in ToikY's #7439. Claim type: scoped computer-assisted proof with an exact character-ring certificate. No new κ.
The earlier one-body gauge extends to all 17 simultaneous signs. Consequently the cited unit-body 19-factor witness transfers to every real body-sign profile. The predecessor's witness, minimum-length theorem and paid comparison are cited premises, not replay deliverables. The new result, proof and checkers were produced by Nick Petalas.
The package retains the exact literal caller from #7439 head
ba83c9bebd99502cd64bb1cab2bc4e5336d9d7b2, originally supplied by rohanarun in #7113. It needs no foreign Git commit or network during replay. Credit ToikY for the selected circuit and real-body opening, rohanarun for the signed caller, Clear1nsight for #7334, and the retained P104/native lineage.Card
p104-side-correctionchanges scope to this body-sector interface. Base is canonical maine54523517d0f03e58352e647c403a5af3e525a57; selected #7000 remains unchanged. Live PRs, main, merged work and Discussion claims were checked before reservation and commit.Evidence
D8=-1gauge. After: the new exact rational sign-character calculation proves the common gauge for all independent signs, including every zero displacement entry.Exact reproduction from the repository root:
Use a local CPython 3.12 path on another machine. See
research/p104-real-body-factor-gauge/PROOF.mdfor the exact claim and proof.Limitations
Only the fixed normalized circuit, real body signs and central signs
q=±1are covered. Arbitrary complex bodies, imaginary central sectors, native host reuse, physical sign synthesis, ownership/restoration and complete pricing are unproved. No selected-supplier replay, independent human review, proof-kernel acceptance or complete multiplication theorem is claimed. The price obstruction in #7439 and fixed-frame host-reuse obstruction in #7457 remain intact.Open next questions
Related open work
CI notes
CI did not certify this package. At unchanged head
bbaac094a8368bcb49c586d95e2c7975ac43f119, run 43291118984, plan job 131437302165, failed inOnboarding helper tests. I read the job log: exactly one of 760 tests failed, with 24 skipped. The failing test istest_research_current_status.CurrentCiNavigationTests.test_current_ci_section_matches_selected_record, attests/test_research_current_status.py:58. Its AssertionError says that 'make frontier7000-verify' is not found in the CI verification document, whose current section still describes #6030.This mismatch exists in canonical main
e54523517d0f03e58352e647c403a5af3e525a57:certificates/selected-result.jsonnamesmake frontier7000-verify, whiledocs/ci-verification.mdstill names #6030. Both files and the test are unchanged by this PR. I also read the failed-step logs of run 42905094314 and run 43291152300; each has the same single failing test, the same missing-command assertion, andFAILED (failures=1, skipped=24)after 760 tests.The package
replayjob was skipped becauseplanfailed. The successful package checks described above are local evidence only. No fix, retrigger commit or job rerun was made; the repository-level repair is left to maintainers.Merge Danger
Door: two-way. This adds one isolated research package.
Blast Radius: package. Shared code, selected records and predecessor packages are unchanged.