How it works

Every number on the terminal is derived from something, and every derivation makes a choice. These pages are those choices, written down with the measurements that produced them.

They are here for one reason. A leaderboard that ranks strangers by honesty is asking you to trust an unusual amount of arithmetic you cannot see. The least we can do is show the arithmetic.

Three rules that run through all of it

Unknown is not zero. Every field that could be null is null when the answer is not known. A dash on the screen means we do not know. A zero means we know the answer is none. Collapsing the two is the single easiest way to build a tool that lies quietly, and it is the failure this codebase spends the most effort avoiding.

Miss it rather than guess it. Where a value cannot be derived honestly, the transaction is counted as missed and published as missed. A guessed split across three pools is a wrong cost basis rather than a missing one, and a wrong cost basis propagates into every number downstream of it forever.

Measure before designing, and measure again after. More than one plan on these pages was thrown out by its own measurement. The coverage rewrite was designed around transfer netting until transfer netting was measured against V4 and found to cover thirty percent of it. The cluster detector was built on rarity until rarity was shown to hide the largest syndicates by definition.

What is deliberately not claimed

The engine publishes what it misses. Roughly 2.6% of position moving swap transactions are not booked, broken down by reason rather than rounded away, and the health endpoint carries the breakdown live.

Two counters on that endpoint are worth reading before you trust anything else, and both are covered in The Engine. One of them is a canary whose value should never be zero, because zero means the system has quietly reverted to a weaker method while continuing to look like it works.