This page is the demo

State-feeds.
Ship the state, not the pixels.

A wai.feed.state is a non-physics world — a scoreboard, a telemetry stream, a market tape — carried as a signed op log, not a recorded video of a dashboard. There is no solver: the sim is the identity step, and the state converges because every typed-field update applies in one canonical order. Your browser replays the log with the same deterministic Rust engine (compiled to WASM) that produced the conformance corpus and re-derives the publisher's sealed BLAKE3 state hash: replay-equivalence, the same criterion interactive worlds use. Scrub the tick slider — the state is reconstructed, not scrubbed through frames.

—
records — state hash — sealed hash —

State as instructions

A scoreboard update is a few signed bytes — "add 7 to field 1" — not a frame of a broadcast. The sink holds the authoritative state and renders it however it likes. One authoritative publisher, many read-only sinks: the broadcast profile of a live world.

Replay-equivalence, reused

No new conformance idea. A feed is a world whose step is the identity, so it inherits the worlds machinery wholesale: canonical ordering, causality, sealing, the receipt chain, and a bit-exact wai.det.fixed64 state hash. SET is last-writer-wins; ADD is commutative accumulation.

One floor, four cargo classes

The same fixed-point floor as worlds (replay), spatial audio (mixdown), and haptics (sample). Sport, sensor, and market state join sight, hearing, and touch under one standard — verified the same way, on any machine.

Reference engine + conformance corpus in the open-standards repo; Apache-2.0. The sealed hash shown is the one the native generator computed — this tab re-derives it from the op log.