Demos are claims
Every demo names the claim it illustrates, the receipt it cites, and the boundary it does not cross. A demo that cannot fill those three is decoration and does not ship here.
1 · the ticket check (shipped)
Claim: the 32-byte ticket re-derives from the canonical record bytes. Receipt: the issue object and its canonical bytes, verified in your browser. Boundary: it proves the ticket names these bytes, not that these bytes are the ones first published.
2 · the twenty-one layers (static scene)
Claim: the subsumption table has 21 layers. Receipt: docs/BUSINESS BINDER/SUBSUMPTION_TABLE.md. Boundary: a map of what exists in the tree, not an adoption or benchmark claim.
3 · the browser benchmark (shipped)
Claim: a ticket verification is a sub-millisecond operation on a modern browser. Falsifier: the reader runs it; over 1,000,000 ns it prints FAIL. Conditions and the JSON receipt are on the page. Boundary: a reader-side measurement of the island algorithm, not the office
4 · the race (static scene)
Claim: Next 16.1.1 ships 553,643 B of client JavaScript; the house arm ships 0. Receipt: issue 0002 and its evidence file. Boundary: one fixture, different content, not a latency ratio. Interactive aeon-3d comes later; this deterministic SVG is the fallback readers get today.
5 · the workbench (external)
The gnosis-church in-tab workbench runs thirty-two registry-backed languages in gnexec-wasm from per-language shards, with async compile above 8 MiB. Boundary: it is the church surface, not this office, and a language demo there is not a pressroom claim until an issue cites its receipt.