topologicalCodes
plain-language theorem explainer
Topological codes encode information in global topological properties of the ledger, rendering local errors irrelevant to the encoded state. Information theorists deriving error bounds from 8-tick phase structure cite this definition when linking Recognition Science redundancy to surface-code constructions. The entry is a direct string definition with attached explanatory comments on the toric code and homology classes.
Claim. Topological codes store information in global topological invariants (e.g., homology classes on a torus) such that local errors leave the invariants unchanged; in Recognition Science the ledger topology supplies this protection, as realized by surface codes on a 2D lattice.
background
The module INFO-005 derives error-correction bounds from the 8-tick structure. Eight-tick phases supply natural redundancy: each bit is distributed across correlated phases, and Shannon capacity is recovered once phase correlations are accounted for. Upstream, PhysicsComplexityStructure establishes that J-cost minimization is convex with a unique minimum at unity and that each tick updates at most eight local neighbors, furnishing the local dynamics that topological codes exploit.
proof idea
One-line definition that directly assigns the string literal to the identifier, followed by inline comments describing the toric-code construction (qubits on edges, logical qubits as homology classes, syndrome measurements). No lemmas are invoked; the entry simply records the conceptual label.
why it matters
The definition supplies the conceptual anchor for the sibling bounds (hamming_bound_8tick, singleton_bound_8tick, eight_tick_redundancy) inside the same module. It connects the 8-tick octave (T7) to error protection by noting that ledger topology inherits the phase redundancy already derived in EightTick and PhysicsComplexityStructure. No downstream theorems yet consume it, leaving open the explicit mapping from topological invariants to quantitative capacity formulas.
Switch to Lean above to see the machine-checked source, dependencies, and usage graph.