Data and provenance
REAL, PAPER, MOCK: how to tell real money from a simulation.
Every figure
REAL, PAPER, MOCK
Every figure carries a provenance label. Nothing is shown without one, and missing data is shown as missing, never as zero.
- REAL
- Observed on chain or from a live market source.
- PAPER
- Real market data, simulated fills on a paper ledger. No transactions are sent and no real funds move.
- MOCK
- Fixture data and a rules-based allocator, not an AI: tests, demos and visual QA. Never real.
- UNAVAILABLE
- The source returned nothing, so the screen says so instead of showing a number.
A label shows once for a whole page or section and again only where a figure differs from it, so the odd one out stands out.
The band at the top
Runtime modes
The band at the top of every page says what happens to money on this deployment, read live from the API. Hatched means no real funds move. Figures older than their source's refresh are flagged Stale.
- Paper
- Simulated fills. No order or transaction is sent and no real funds move.
- Devnet
- Solana devnet and venue testnets: test tokens with no value.
- Dry run
- Mainnet data. Orders and transactions are built and checked, never sent.
- Mainnet
- Orders and transactions are sent on mainnet with real funds.
MAINNET needs an explicit second opt-in by the operator, and nothing ever falls back to mainnet on its own. In PAPER and DRY RUN nothing is signed, and any data source the API reports as MOCK gets its own MOCK plate in the band.
Line grammar
How to read the screen
Solid. Observed, settled or enforced: REAL data, finished stages, limit walls.
Dashed. Simulated: PAPER data and paper fills.
Dotted. Has not happened yet: pending stages, the next cycle, options marked SOON.
Hatched. Not real money, or an estimate: the band in PAPER, DEVNET and DRY RUN; cost and runway estimates.
Colour follows the same discipline: orange means live, now or attention; green and red only ever mean gains and losses, long and short, filled and failed.
On every coin's page
What is public
- Policy versions and their hashes, from the launch on.
- Each decision's input snapshot, whose hash the page recomputes in your browser.
- Decisions, risk verdicts, orders and fills, as they happen on the live console.
- Creator-fee collections, buybacks and on-chain events.
The console shows the model's short public summary, never its prompts or raw reasoning. How a cycle runs: one cycle, step by step.