Model Specification

A model defines a reusable engine. A World pins that engine to one configuration, execution history and associated token.

Executable model

Declare S, the complete serializable state; f, the transition rule; sigma, the initial state or seed; and the input and scheduling rules. The transition can be written as s(t+1) = f(version, s(t), accepted_inputs(t)). Identical pinned code, state and recorded inputs must reproduce the same next state.

State includes persistent variables and any generator state. Arithmetic, rounding, update order, tie handling, serialization, compiler and dependencies must be concrete. Bound CPU, memory, storage and event throughput. External market data, player actions and any AI outputs used as inputs must be recorded, rather than silently refetched or regenerated during replay.

Timing

Specify separately the simulated time represented by each tick, its real-time execution cadence, checkpoint frequency and presentation cadence. Public event ordering determines how inputs enter each tick. Declare pauses, catch-up behavior and terminal conditions.

World record

Bind model version and build hash, configuration, initial state, launcher, token and chain, fee splitter and creator weights, runtime quote and policy, and launch transaction. Public World rules and replay artifacts must be available before participants rely on them. Draft work can remain private before publication if the product supports it.

Changes

New model submissions produce new version records. Existing World history is retained. A live World can change versions only under a policy announced at launch, with authorization, effective tick and state migration recorded. Player actions under existing rules are distinct from changing the engine.