Repository navigation
Conversation
This was referenced Nov 11, 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
Scoped written proof with exact finite corroboration: for every whole-bank M-qubit unitary Clifford with entries in Q(i),
This resolves the explicit Phi3/Phi5 test in Open next question 2 of merged #6192. The new step excludes mixed sectors: their multiplicities would give
2a+4b=2^M,Tr(U)=-a-band a trace magnitude strictly between consecutive powers of two, contradicting the Clifford trace gate. The pure-factor rank formulas are cited, not re-audited. No new kappa, physical caller, supplier admission or selected-frontier change is claimed.Produced by Nick Petalas. Credit Nick Petalas #6192 for the explicit question, cyclotomic field argument, primitive-factor theorem and quintic fixture; Ross Richardson #4081 for the preceding cubic Clifford trace gate and Pauli-character method; and classical cyclotomic/character facts. No predecessor executable is imported or run. Independent human and formal proof-kernel review are unclaimed.
The
joint-query-controllercard is explicitly changed to this algebraic response-interface obstruction. Base and refreshed canonical main:e54523517d0f03e58352e647c403a5af3e525a57, priority revision 8. Exact proof/source pins, scope and next questions are inresearch/two-cyclotomic-no-mixing/.Evidence
bf8ab572a32a9f540835373f02b178c346ed25e4. The working tree is clean. Selected source-binding orientation also passed; no selected scientific replay was run.Local environment: CPython 3.12.15 on macOS arm64; standard library only.
Exact reproduction from the repository root:
Other machines may substitute their CPython 3.12 interpreter path. Direct marker:
PASS_TWO_CYCLOTOMIC_NO_MIXING; registered marker:PASS_REGISTERED_RESEARCH_PACKAGE; publication marker:PASS_RESEARCH_COMMIT_BYTES. Add--emitto either direct command to print its computed six-file SHA256 receipt; the verifier writes no files.Limitations
The result assumes the exact polynomial relation on the entire bank with the actual global phase, Gaussian-rational entries and Cliffordness. It does not classify other products, fields, restricted-input or approximate relations. The native-rank consequence uses the cited pure-factor theorem. No exact physical word, paid/productive invoice, dirty restoration, ownership, hosting, precision, stock, tape execution, compiler closure, supplier admission or complete multiplication theorem is provided. The five selected framework assumptions remain. No native replay, selected cold replay, Lean, Docker or formal-kernel proof was run.
Open next questions
Related open work
Refreshed open-PR searches for cyclotomic products and Phi3/Phi5 found no other PR on this specific object. Recent handoffs, reservations, main README searches, merged searches and this account's 38 PRs from the preceding seven days were checked. The cached helper covered 477 open PRs and 7,121 Discussion records with complete pagination; its sparse local-note coverage was 177 of 10,178 records. Arbitrary diffs and unpublished work are outside that coverage. No additional computations were used to check another contribution's numbers.
The closeout refresh read this account's nine other open PRs created since the CLAIM: #7178, #7179, #7180 and #7182 through #7187. Their titles and relevant body text concern multiplicative shells, A2 tariffs, Gaussian inverse norms, cube-zero lifts, radical delivery, rational headers, block signatures and residue samplers. None studies this Phi3/Phi5 whole-bank annihilator or computes a competing value for the same object. No additional scientific computations were run to check another contribution.
CI notes
CI did not certify this package. At unchanged head
bf8ab572a32a9f540835373f02b178c346ed25e4, run 42992679183, plan job 130429099981, failed in "Onboarding helper tests" on exactly one of 760 tests, with 24 skipped:I read the failed job log directly. At
tests/test_research_current_status.py:58, the assertion expects the selected reproduction command in the CI verification document's current section. The logged section still describes #6030 andmake frontier6030-verify. Direct inspection of canonical maine54523517d0f03e58352e647c403a5af3e525a57confirms thatcertificates/selected-result.jsoninstead namesmake frontier7000-verify. The selected record, document and test are unchanged between that base and this PR. The failure is in the base repository's files.The same exact failing test, missing command, 760-test total, one failure and 24 skips were confirmed directly in the failed job logs of all these runs. Each failed step is "Onboarding helper tests":
The package replay job 130431573537 was skipped because plan failed. The local registered normal/optimized, exact matrix/census, metadata/pin and committed-byte/source-history checks above remain the package's automated execution evidence. No repository fix, retrigger commit, push or job rerun was made for this failure. Maintainers will repair main. Mathematical acceptance remains separate from package replay.
Advance CLAIM.
Merge Danger
Door: two-way.
Blast Radius: package. Six new files in one isolated opt-in research package. Shared implementations, frozen predecessors and selected-result records retain their bytes.