godzone ledger

every number on this page is a field of the append-only ledger, or it says unknown
predictions — what the router expected before sending. not revenue.
The gap between these and the realised figure above is the engine’s error, not its earnings. A prediction is never summed into realised profit anywhere on this page.

funnel

attempts → built → submitted → resolved → landed → measured
A bundle id means the block engine accepted the transaction into an auction. That is all it means. It is not inclusion, not a trade, and not a win.
Landing is not profit either: solve returns Ok when it declines to trade, so a landed transaction can be a no-op that moved the signer by exactly −(tip + fee). Only the last stage — a landed row carrying an on-chain pre/post balance pair — may be called profit.

decline histogram

Scope, precisely. This counts only attempts that reached a ledger row. Router-level declines — no_candidate_pools, under_water, over_lock_budget, size_collapsed, implausible_edge and the rest — are tallied in the engine’s in-process counter and printed to its log; they are never written to the ledger, so they cannot appear here and this page will not pretend otherwise. To separate “no edge at this latency” from “the lock budget is wrong” you need the engine’s own decisions line, not this histogram.

live tape

time
slot
route
size
predicted
outcome
realised