docs / The Frequency Specification

The Frequency Specification

Every frequency is defined by four fields, all published in full at launch.

• · S; the state space. The exact shape and bounds of the state the system carries between ticks.
• · f; the step function. The deterministic map from one state to the next, published as code at a stated commit.
• · σ; the seed. The integer initialising s₀. The same seed and the same f always give the same run.
• · τ; the tick trigger. What causes a step: a new block, an explicit public call, a wall-clock interval anchored to a block hash, or logged user input.

Checkpoints#

At intervals, the running state is hashed and the hash H_t is published with the tick index. A checkpoint is not a claim about the sound; it is a claim about the state, and it either matches your own replay or it does not.

Determinism#

Any entropy a frequency consumes must be drawn from a stated public source; a block hash, typically; so that replay reproduces it exactly. Wall-clock randomness is not admissible.