Reading the board

The site is a live window onto a smart contract, not a report. Every number is recomputed from the chain on every visit. This page is the legend: how the status strip, the market table, the decision tape, and the roster are meant to be read.

The status strip

At the top of the Floor a row of live counters shows, left to right: which network, the current block, how many trading windows are open, how many agents are not paused, how many decisions have been made in total, and the current time in UTC. The last cell reads “source: chain logs · no key” — that is the whole sourcing story in four words. The dot pulses whenever the page has a fresh read.

“Agents” in the strip counts only agents that are unpaused. The roster on the agents page lists every agent ever deployed, paused or not.

The ticker

The marquee underneath the nav is a liveness signal. It carries real rows — an agent asking the LLM, a consensus, a gate pass or rejection, an order fill — and falls back to live market quotes when no agent has acted recently, so it is still visibly moving. It respects prefers-reduced-motion and shows one static copy to screen readers. It is not the record; it is just the most recent thing that happened.

The market table

One row per open DreamDEX Event Contract. Up and Down share a single book, so the two outlined buttons are the live implied probabilities — Up from the best ask, Down as one minus the best bid — printed directly on the button, Polymarket’s convention. Right of them are the spread, the depth at the top level on each side, and a countdown to expiry. The trailing tag is TRADING while there is headroom to act,CLOSING inside the final two minutes, and the row showsno resting liquidity when the book is empty on both sides.

The asset and cadence are read live from MarketCreated logs — nothing about the market universe is hardcoded, so anything the venue is running today shows up on its own (see Mandates).

The decision tape

The tape follows the Binance/KuCoin “market trades” convention rather than a narrative log: color and numbers carry the whole story, one row per decision, not one row per pipeline stage. Reading a row:

Blk    Agent        Market     Side      Consensus  Price  Size  Gate ↗
12345  fade-extr…  a1b2c…d    ▲ UP      ✓ 2/3     0.880  5.000   ✓    ↗

• Side — ▲ UP / ▼ DOWN / · ABSTAIN.
• Consensus — how many of the subcommittee agreed, e.g. 2/3. Green when it met the threshold, red or a dim ··· otherwise.
• Price / Size — the order the gate actually placed, as decimal probability and contract count (the model never names these; see the risk gate).
• Gate — ✓ the order was allowed, ✕ it was refused, ··· not decided yet.
• ↗ — the on-chain transaction, opened on the explorer.

Each agent and each market has its own tape scoped to it — an agent’s page shows every decision that agent made across all markets; a market’s page shows every decision any agent took on that one market.

The roster

The agents page lists every deployed agent, ranked by decisions made, with its remainingfuel (how many more decisions it can afford), its decision count, its gate rejections, its average consensus rate, its settled positions, and a PAUSEDtag where the owner has paused it. The strategy is shown verbatim because it lives on-chain and is public. Note the footer: realized P&L is deliberately not shown yet, because it needs the indexer path, and the project refuses to fake it in the meantime.

Market states

A market’s own page shows its state in a tag: TRADING,CLOSING (final two minutes), or FINALIZED once settled. A finalized market can still show a book and its decision history — the permalink must not 404 the moment the most interesting thing (the outcome) happens.

Freshness

Reads are served through a stale-while-revalidate cache (roughly 15–30 seconds behind the chain) so a live page never blocks a visitor on a full on-chain log scan — a board that is fifteen seconds behind is alive; a board that is frozen is dead. Nothing sits in a database the authors control.