Skip to content

Prove the no-edge irreducible joint-image bound is 3. - #6921

Merged
Mister-Meeseeks merged 1 commit into
CrocSwap:mainfrom
unpaidmoon:cursor/no-edge-irreducible-image-c27a
Nov 10, 2026
Merged

Mister-Meeseeks merged 1 commit into
CrocSwap:mainfrom
unpaidmoon:cursor/no-edge-irreducible-image-c27a

Conversation

@unpaidmoon

@unpaidmoon unpaidmoon commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Change and mathematical scope

A complete noncoordinate rank-one idempotent pool over F2, in a pattern space of dimension at most three that contains no matrix unit, cannot act irreducibly on a four-dimensional joint image. Dimension 3 is sharp at every ambient width, by an explicit three-projector pool. This is a scalar pool theorem. It is not a paid-profile improvement and no new κ is claimed. The selected value stays 781451/250000000.

The total-image bound dim V ≤ 4 is cited from #6838 and is not reproved. The new statement is reducibility at dimension 4.

Task and overlap

Base commit: 7c49fe32c55de02c2c873655c804b16e4c3fef0a.

Card bit-new-register-model, priority revision 8. Scope status: changed. The card asks for a larger or nonabelian register alphabet. The actual result answers the scalar question left open by #6838: whether a no-edge pool of pattern dimension at most 3 can be irreducible in joint-image dimension 4. No new alphabet or word is built. The original native acceptance gate remains unmet. The same card was already used for scalar pattern-pool questions in #5921 and #6838.

Nearest open work:

Overlap search on 2026-11-08 covered 825 open PRs and 6920 discussion records. The phrase pair "no-edge" and "irreducible" matched only this package. "zero-edge image" matched #6838. "irreducible joint" matched #6785 and this package. No match is not a novelty certificate; the distinctions above are from reading those PRs.

Validation

Python 3.12, standard library only. From the repository root:

python3 -B research/no-edge-irreducible-image/verify.py
python3 -I -O -B research/no-edge-irreducible-image/verify.py
python3 -B scripts/research_package.py --package research/no-edge-irreducible-image

Observed: PASS_NO_EDGE_IRREDUCIBLE_IMAGE and PASS_REGISTERED_RESEARCH_PACKAGE. check_research_commit.py --check-source-history passed at 6020400853abc110134804fad04b695adc360bcd.

The verifier enumerates GL(3, 2) (168 matrices, 18 survivors), the sharp pool on four coordinates, a one-extra-bit support check, the seven four-point caps, and negative controls: the #6838 parity pool is reducible, the normal-form triple is reducible, and dropping one sharp projector leaves an invariant line. Those finite checks do not replace the all-width case analysis in PROOF.md. No Lean, Docker, or historical replay was run. The selected baseline was not rerun.

Credit

Nick Petalas, #5921, for the fiber lemma. CubeJerry, #6838, for the total-image bound and the open irreducible question; #6782 for the edge-quotient context. Prepared by unpaidmoon with substantial Cursor Grok assistance. New work is Apache-2.0.

Open next questions

  1. After a valid relation, cube-span, and coordinate-call split, does bound 3 change the paid-rank accounting for a three-relation word? The scalar theorem does not prove that split. First state the hypotheses from Prove the two-relation rank bound at arbitrary helper width (no new κ) #6777 and Bound binary pattern cores and exclude the irreducible five-type saving (no new κ) #6782.
  2. Does the irreducible bound remain 3 in pattern dimension 4? The parity construction one dimension higher has total image 5, and the Fano-plane case split stops at dimension 3.

A complete pool with pattern dimension at most 3 and no matrix unit is reducible whenever its joint image has dimension 4, and an explicit three-projector pool attains an irreducible image of dimension 3 at every width. No new kappa.

Co-authored-by: unpaidmoon <unpaidmoon@users.noreply.github.com>
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.

3 participants