Alphabeta Math
Pipeline-generated
How statement and proof provenance work

The first chip identifies the source of the statement or construction; the second identifies the source of its local proof or verification.

  • Literature-sourced: the exact statement appears in a cited source; only wording and notation differ.
  • AI-adapted: a semantically identical restatement of literature-sourced material, modulo indexing, notation, and boundary cases adopted by the library.
  • AI-generated: a genuinely novel statement formulated by AI, with no source for the claim itself.

These labels describe origin, not correctness: citations and verification chips remain separate evidence.

Planar-diagram codes and knot-table enumeration — Examples and Counterexamples

1 · Prerequisites

2 · Logical flowchart

3 · Definitions, theorems and proofs

None yet.

4 · Examples, counterexamples and false statements

CounterexampleConstruction: AI-generatedVerification: AI-generatedjudge pass (gpt-6-luna)verified 2026-10-22 (gpt-6.1-sol)Open item page →

A crossing label occurring once is invalid

Statement refuted

For every positive integer c, every finite signed word with labels in {1,…,c} in which each declared label occurs at least once is a Gauss code of a closed regular oriented diagram.

Statement references

Planar-diagram, Gauss, and signed Dowker–Thistlethwaite codes — each crossing label occurs exactly once over and once under.

Planar-code validation and diagram reconstruction — visit-count check and its ordered failure reason.

Planar-code validation and reconstruction procedure properties — exact invalid-code return behavior.

Knot Atlas, “Gauss Codes” — each crossing is recorded on both visits, with over/under signs.

Hass–Lagarias–Pippenger, §3 — a regular diagram crossing is a four-valent vertex.

Facts & Assumptions

Given: The declared crossing count c=1 and the one-entry word −1.

[F1]

Planar-diagram, Gauss, and signed Dowker–Thistlethwaite codes: for each crossing label j∈{1,…,c}, a Gauss code contains exactly two visits to j, one over and one under.

[F2]

Planar-code validation and diagram reconstruction: for a nonempty Gauss input, after range checking, the procedure counts the two over/under visits and returns invalid-crossing-visit-count at the first label whose counts are not (1,1), before any graph or face test.

[F3]

Planar-code validation and reconstruction procedure properties: each invalid return is the first failed predicate in the stated procedure order.

Counterexample

Given: The declared crossing count c=1 and the one-entry word −1.

1.1givenF1algebra

The only declared label is 1, which lies in {1}. The word has one entry, and its negative sign makes that entry an under-visit. Hence its visit-count pair is (0,1), not the required (1,1) in [F1].

2.1givenF1F2F3step 1.1∎

The range check passes, so the validator reaches its Gauss visit-count check. By [F2] and [F3] it returns invalid-crossing-visit-count with (0,1) before constructing a crossing graph or computing faces. Therefore mere presence of every declared label does not make a signed word a Gauss code.

ExampleConstruction: Literature-sourcedVerification: AI-generatedverified 2026-10-22 (gpt-6.1-sol)Open item page →

Trefoil Gauss traversal and rotation reconstruction

Example

Use the based signed Gauss code −1,+3,−2,+1,−3,+2, where a negative visit is under, a positive visit is over, and the separate algebraic crossing-sign vector is (+1,+1,+1). This is a cyclic shift and the relabeling 2↔3 of the right-trefoil signed Gauss code. Its normalized PD records in clockwise order beginning with outgoing over-dart are X1=(e1,e2,e3,e4),X2=(e2,e5,e6,e3),X3=(e5,e1,e4,e6). Its face cycles are F0=(1:e1,2:e2,3:e5),F1=(1:e2,2:e3),F2=(1:e3,3:e4,2:e6),F3=(1:e4,3:e1),F4=(2:e5,3:e6). Selecting F0 as the outer face gives a valid one-component three-crossing code, and the bounded enumerator includes its reconstructed candidate at crossing bound 3.

The figure displays the positive two-strand braid closure with the same spherical crossing and face data. Its unbounded face is F1=(1:e2,2:e3), bounded by the two exterior closure arcs; it is not the plane realization obtained above by selecting F0 as outer face. The braid strands are oriented downward, the closure arcs upward, and the crossings are labeled from top to bottom 1,3,2; the upper branch is the right-to-left branch at each positive crossing. The proof below verifies the code and face cycles from finite dart data and does not infer them from the drawing.

+1+3+2

Example references

Planar-diagram, Gauss, and signed Dowker–Thistlethwaite codes — signed visits, normalized PD records, and face-cycle convention.

Realizability and face validation for planar-diagram codes — Euler test for spherical realizability.

Enumerate diagrams up to a crossing bound — bounded normalized-code enumeration.

Knot Atlas, “Gauss Codes” — trefoil traversal −1,3,−2,1,−3,2.

Fish, “Codes, Links and Racks,” §5.2.1 — right trefoil signed code and crossing-sign convention, pp. 67–68.

Erickson, “Planar Graphs” — rotation-system face cycles and outer-face selection.

Facts & Assumptions

Given: The based signed Gauss word −1,+3,−2,+1,−3,+2, the sign vector (+1,+1,+1), and the page's normalized dart and face conventions.

[F1]

Planar-diagram, Gauss, and signed Dowker–Thistlethwaite codes: a positive Gauss visit is over and a negative visit is under; each crossing occurs once over and once under; a positive normalized crossing has clockwise record (Oout,Uin,Oin,Uout); face cycles are those of α∘σ.

[F2]

Oriented crossing signs, diagram writhe, and blackboard framing: the algebraic sign is sgn⁡det⁡(vover,vunder), and the positive Artin half twist has sign +1.

[F3]

Realizability and face validation for planar-diagram codes: a nonempty connected code with consistent local crossing data has a spherical realization when V−E+F=2, and a chosen face gives its plane model.

[F4]

Planar-code validation and reconstruction procedure properties: the validator accepts exactly codes satisfying the incidence, strand, connectedness, face-count, and outer-face predicates and returns their crossing-disk/edge-band model.

[F5]

Enumeration up to a crossing bound procedure properties: the enumerator includes every normalized connected one-component code up to the specified crossing bound that passes validation.

[F6]

Fish, “Codes, Links and Racks,” §5.2.1, p. 67: the right trefoil signed Gauss code is o1+,u2+,o3+,u1+,o2+,u3+, and crossing signs are unchanged between the two visits to a crossing.

Proof

1.1givenF1F6algebra

The visits of the given word are, in order, under at crossing 1, over at 3, under at 2, over at 1, under at 3, and over at 2. The source code in [F6], started at its fourth visit, is u1+,o2+,u3+,o1+,u2+,o3+; exchanging labels 2 and 3 gives exactly the stated word and the same positive sign at each crossing. Thus the word is the stated based traversal of the right trefoil.

2.1givenF1F2step 1.1construct

Let xi be the directed edge from visit i to visit i+1, with indices modulo 6. Then x1 joins 1:Uout to 3:Oin, x2 joins 3:Oout to 2:Uin, x3 joins 2:Uout to 1:Oin, x4 joins 1:Oout to 3:Uin, x5 joins 3:Uout to 2:Oin, and x6 joins 2:Oout to 1:Uin. At each crossing the sign is positive by the given vector and [F2]. Reading each crossing clockwise from its outgoing over-dart therefore gives X1=(x4,x6,x3,x1), X2=(x6,x2,x5,x3), and X3=(x2,x4,x1,x5). Scanning crossing 1 then 2 then 3 assigns canonical edge names e1=x4,e2=x6,e3=x3,e4=x1,e5=x2,e6=x5, yielding the three normalized records in the statement.

3.1givenF1step 2.1construct

Write j:ek for the dart labelled by edge ek at crossing j. Applying ϕ=α∘σ gives 1:e1↦2:e2↦3:e5↦1:e1,1:e2↦2:e3↦1:e2,1:e3↦3:e4↦2:e6↦1:e3,1:e4↦3:e1↦1:e4,2:e5↦3:e6↦2:e5. For example, 1:e1 advances clockwise to 1:e2, whose paired dart is 2:e2. The five displayed cycles are disjoint and contain all twelve darts, so they are exactly the face cycles. Hence V=3, E=6, F=5, and V−E+F=2.

4.1givenF1F2F3step 2.1step 3.1construct

Each edge occurs at its two ends once incoming and once outgoing by the six directed segments in step 2.1. Each crossing record has its two opposite oriented strands, the over/under designation, and the positive cyclic order from [F1]–[F2]. Traversing from 1:Uout follows x1 to 3:Oin, then the opposite over-dart follows x2 to 2:Uin, then follows x3 to 1:Oin, then x4 to 3:Uin, then x5 to 2:Oin, and finally x6 to 1:Uin; the opposite under-dart there is the starting 1:Uout. This single cycle covers all six visits, and the edge graph connects crossings 1,2,3. By [F3], the Euler count gives the spherical realization; choosing F0 yields the selected plane model.

5.1givenF4F5step 4.1∎

The code therefore passes the validator's ordered checks, and [F4] returns its diagram with these face cycles and outer face. Its normalized crossing signs, edge pairing, and selected cycle occur in the enumerator at c=3; the one-cycle component trace passes the knot filter. By [F5], the reconstructed candidate is included at bound 3.

Sources