Evidence

The journal (append-only)

The journal is the engine’s record of itself: appended minute by minute, never edited, never pruned. It is the dataset the kill and graduate gates are counted from — a lane dies or graduates on what stands here, not on what anyone says about it.

What gets recorded

Every fire is recorded — including fires that were suppressed and never reached subscribers. Every non-firing minute is recorded too: the engine journals which gate stood it down, so a quiet session is a page of named stand-downs, not an empty page. Each entry carries its modeled costs to the dollar; no figure appears here without costs already counted against it.

Append-only means the record cannot be cleaned up after the fact. A bad fire stays. A suppressed fire stays. The 40-fire kill review and the 100-fire graduation review read this journal and nothing else.

The schema

Each journal row publishes the columns below. The feed itself is pending its API — the slot fills with real rows when it ships, and not before.

Journal column schema — feed pending API
TimestampAlert priceCost modelPAPER/LIVEOutcomeRunning cost-adjusted stats
JOURNAL FEED — PENDING API

Exports and the free feed

A CSV export of the full journal will be available, so anyone can run the arithmetic themselves rather than take a summary’s word for it.

The free tier publishes here as well: a delayed journal and stand-down feed — delayed or end-of-day, never real-time. Same record, same columns, later clock.

Every alert is an impersonal publication delivered to all subscribers identically and simultaneously — not advice, not tailored to anyone.

Pre-registered evaluation criteria — not a performance claim, projection, or promise of results. Risk Disclosure.