Skip to content

Shorten the two-axis witness from 16 to six records (no κ) - #7515

Open
petalas wants to merge 1 commit into
CrocSwap:mainfrom
petalas:research/w3-1113b-query-obstruction
Open

petalas wants to merge 1 commit into
CrocSwap:mainfrom
petalas:research/w3-1113b-query-obstruction

Conversation

@petalas

@petalas petalas commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Exact finite certificate: the two-axis witness using 16 records in unpaidmoon's #7286 elimination has a shortest recipe of six. The full 3,072-element affine-quadratic monomial group has directed diameter eight in the same eight-record alphabet, retaining absolute phase and charging inverse S/global-i as three unit records.

six-record witness: C01, X1, C10, S1, omega, omega
complete synthesis: literal actions -> distance table <- polynomial normal forms

This answers #7286 Open next question 1 at its requested n=2 first example. The result and attaining words were produced by Nick Petalas. Credit unpaidmoon for that question and witness, intqwq #4610 for the normal form and selected record alphabet, and the retained physical/native/compiler lineage. Finite-group enumeration and shortest-path certification are classical. No predecessor scientific verifier is imported or replayed.

Only research/two-axis-monomial-geodesics/ is added. The formal-interface-lemma card is explicitly changed to this finite synthesis side result. Canonical base and final upstream checkpoint are e54523517d0f03e58352e647c403a5af3e525a57, priority revision 8; selected #7000 is unchanged.

Evidence

  • Before: the cited synthesis uses 16 records for its n=2 extremizer. After: the displayed word attains its certified minimum six; every group element has an attaining word of length at most eight, with 93 elements requiring eight.
  • Both exact implementations cover all 3,072 states and all 24,576 labeled transitions. The primary implementation replays every attaining shortest word. The separate polynomial implementation checks all literal transitions, every edge distance inequality and every decreasing predecessor. The distance histogram is 1,8,42,162,467,884,940,475,93 at distances 0 through 8.
  • Canonical distance-table SHA256: 4aec51eef32c395d364567018d10626bc96fe507b0591fa312ef3c3688ce1d4c. Generated stdout receipts bind every package file. Four endpoint-changing controls, three invalid-certificate controls and three domain controls pass with the documented outcomes.
  • CPython 3.12.15 normal and optimized warning-strict checks pass. Each registered command was timed locally: 0.045, 0.047, 0.153 and 0.153 seconds, below its sixty-second timeout. These are checker durations, not a speedup claim.
  • Registered replay, source metadata, exact committed-byte/source-history preflight, official export/integrity, and all four scientific commands in a read-only Git-free export with empty PATH pass. The selected source-binding orientation also passes; no selected scientific replay is claimed.

From the worktree root:

/Users/nick/git/integer-mult-bounds/.venv/bin/python3.12 -I -W error -B research/two-axis-monomial-geodesics/verify.py
/Users/nick/git/integer-mult-bounds/.venv/bin/python3.12 -I -W error -B research/two-axis-monomial-geodesics/independent_check.py
/Users/nick/git/integer-mult-bounds/.venv/bin/python3.12 -B scripts/research_package.py --package research/two-axis-monomial-geodesics
/Users/nick/git/integer-mult-bounds/.venv/bin/python3.12 -B scripts/check_research_commit.py --package research/two-axis-monomial-geodesics --check-source-history

Any CPython 3.12 executable can replace that local path. VERIFY.json registers both direct commands with and without -O. The README also gives exact external-certificate export/check commands; default verification writes nothing.

Limitations

The theorem is a finite one-column optimum for two axes, exactly eight directed unit-price records and exact absolute phase. It does not cover extra workspace, different phase prices, a projective quotient, other alphabets or shortestness at other column counts. The displayed identities tensor-lift, but this does not transfer the distance lower bounds. No source-word rewrite is installed. Physical movement/restoration/tape costs, a selected caller and all five inherited assumptions remain outside the claim. No new kappa, supplier admission or complete multiplication theorem follows. Independent human and formal proof-kernel review are unclaimed. Lean, Docker and the selected cold replay were not run.

Open next questions

  • Pin one contiguous two-axis subword of an actual selected normalizer and test an exact replacement while retaining its complete endpoint, restoration and record prices. No source substitution is supplied here.
  • Determine the three-axis directed diameter using a certified reduction or bounded enumeration. The present result gives no all-n diameter formula.

Related open work

CI notes

At unchanged head 7de3d50abf18b67138374e6dc8a42e84cf944992, run 43442595153 failed plan in Onboarding helper tests, job 131943735290. I read the checks once and inspected that job log. It reports 760 tests, exactly one failure and 24 skipped. The exact failing test is:

test_research_current_status.CurrentCiNavigationTests.test_current_ci_section_matches_selected_record

Its line-58 AssertionError says 'make frontier7000-verify' was not found in the CI verification document. At inherited main e54523517d0f03e58352e647c403a5af3e525a57, certificates/selected-result.json names make frontier7000-verify, while docs/ci-verification.md still describes #6030 and make frontier6030-verify. Both files are unchanged by this isolated package.

I independently inspected the failed-step logs for rohanarun #7124's run 42905094314 and petalas #7511's run 43442114549. Each reports the same sole failing test, the same missing-command assertion, 760 tests and 24 skipped.

The package replay job was skipped. CI did not execute or certify this package. All local scientific, metadata, committed-byte/source-history and export checks remain as recorded above. No fix, new commit, push, retrigger or job rerun was made; the repository-level repair remains with the maintainers.

Merge Danger

Door: two-way. One isolated package; no shared code or selected record changes.

Blast Radius: package. The scientific claim is limited to the explicit finite alphabet and certificate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant