Signal8
plain-language theorem explainer
Signal8 is the eight-component analytic signal type that carries the recognition operator over one eight-tick octave. It is a module-local alias of the forced signal type from complex-structure forcing, so bridge and ledger-compat code can name the carrier without importing that module directly. Anyone citing the analytic RecognitionOperator or the legacy LedgerState surface uses this name. The body is a one-line re-export abbrev.
Claim. Write $\mathrm{Signal}_8$ for the eight-component complex signal type supplied by the complex-structure forcing construction: the analytic carrier of one eight-tick recognition period (the fundamental octave of length $2^3$).
background
In Recognition Science the fundamental evolution period is the eight-tick octave (forcing landmark T7: period $2^3$). The analytic recognition operator acts on an eight-slot complex signal rather than on a discrete ledger of agents and bonds. That carrier is constructed upstream in the complex-structure forcing development and is tied to the Clifford picture: the 8-tick DFT grading matches the grading of $\mathrm{Cl}_8$ under Bott periodicity.
This module (Foundation.RecognitionOperator) makes that carrier the canonical state space of the operator. A short legacy note in the file records that older bridge code still expects ledger-shaped names (LedgerState, time, $Z$-patterns). Those names are reattached as harmless readouts on the same analytic signal so stale imports keep building; they do not restore a retired ledger implementation.
The fundamental time quantum is one tick ($\tau_0 = 1$ in RS-native units), so one full signal cycle is eight ticks.
proof idea
No proof. The declaration is a one-line abbrev that re-exports ComplexStructureForcing.Signal8 into the RecognitionOperator namespace. All mathematical content (component count, complex structure, eight-tick DFT identification) lives in the upstream definition; this line only stabilizes the local name used by the operator API and the ledger-compatibility surface.
why it matters
The recognition operator needs a fixed carrier before any spectral or cost analysis can be stated. Naming $\mathrm{Signal}_8$ here pins that carrier to the forced eight-tick object (T7) and to the Clifford/Bott identification of the octave with $\mathrm{Cl}_8$, rather than to an ad hoc $\mathbb{C}^8$. Downstream ledger-compat fields in the same file (LedgerState, time, $Z$-patterns, channels, bonds) treat this type as the analytic stand-in for the old ledger state, so foundation imports stay coherent without reviving retired ledger code. No used_by edges are recorded yet; the declaration exists as the public type hook for the operator and those compatibility projections.
Switch to Lean above to see the machine-checked source, dependencies, and usage graph.