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.
Trefoil Gauss traversal and rotation reconstruction
Example
Use the based signed Gauss code , where a negative visit is under, a positive visit is over, and the separate algebraic crossing-sign vector is . This is a cyclic shift and the relabeling of the right-trefoil signed Gauss code. Its normalized PD records in clockwise order beginning with outgoing over-dart are Its face cycles are Selecting as the outer face gives a valid one-component three-crossing code, and the bounded enumerator includes its reconstructed candidate at crossing bound .
The figure displays the positive two-strand braid closure with the same spherical crossing and face data. Its unbounded face is , bounded by the two exterior closure arcs; it is not the plane realization obtained above by selecting as outer face. The braid strands are oriented downward, the closure arcs upward, and the crossings are labeled from top to bottom ; 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.
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 .
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 , the sign vector , and the page's normalized dart and face conventions.
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 ; face cycles are those of .
Oriented crossing signs, diagram writhe, and blackboard framing: the algebraic sign is , and the positive Artin half twist has sign .
Realizability and face validation for planar-diagram codes: a nonempty connected code with consistent local crossing data has a spherical realization when , and a chosen face gives its plane model.
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.
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.
Fish, “Codes, Links and Racks,” §5.2.1, p. 67: the right trefoil signed Gauss code is , and crossing signs are unchanged between the two visits to a crossing.
Proof
The visits of the given word are, in order, under at crossing , over at , under at , over at , under at , and over at . The source code in [F6], started at its fourth visit, is ; exchanging labels and 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.
Let be the directed edge from visit to visit , with indices modulo . Then joins to , joins to , joins to , joins to , joins to , and joins to . At each crossing the sign is positive by the given vector and [F2]. Reading each crossing clockwise from its outgoing over-dart therefore gives , , and . Scanning crossing then then assigns canonical edge names , yielding the three normalized records in the statement.
Write for the dart labelled by edge at crossing . Applying gives For example, advances clockwise to , whose paired dart is . The five displayed cycles are disjoint and contain all twelve darts, so they are exactly the face cycles. Hence , , , and .
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 follows to , then the opposite over-dart follows to , then follows to , then to , then to , and finally to ; the opposite under-dart there is the starting . This single cycle covers all six visits, and the edge graph connects crossings . By [F3], the Euler count gives the spherical realization; choosing yields the selected plane model.
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 ; the one-cycle component trace passes the knot filter. By [F5], the reconstructed candidate is included at bound .
Depends on
- Planar-diagram, Gauss, and signed Dowker–Thistlethwaite codes
- Oriented crossing signs, diagram writhe, and blackboard framing
- Realizability and face validation for planar-diagram codes
- Planar-code validation and diagram reconstruction
- Planar-code validation and reconstruction procedure properties
- Enumerate diagrams up to a crossing bound
- Enumeration up to a crossing bound procedure properties
Used by
Nothing in the library uses this result yet.
Dependency tree · two levels
15 results within two dependency steps of this one, each drawn at its shortest distance from it. An arrow runs from a result to what uses it, so the chart reads left to right and ends at this result, which carries a heavier outline. Every node is a link to that result. Click elsewhere on the chart to enlarge it.
Sources
- Knot Atlas, Gauss Codes manual (standard reference, not scraped)
- C. Fish, Codes, Links and Racks, University of Warwick thesis (2001), Chapter 5, §5.2.1 (standard reference, not scraped)
- Jeff Erickson, Planar Graphs, Computational Topology lecture notes (2023) (standard reference, not scraped)