ArdenAlgo · Blog · Reading the ledger like an auditor
Guide

Reading the ledger like an auditor

24 Jul 2026 · 6 min read · ArdenAlgo Research · claims about the engine refer to mechanization v1 (frozen 16 Jul 2026) — changes land in the changelog

Our whole pitch is "audit it yourself" — so here is, literally, how. Ten minutes, no tools beyond a browser, no goodwill required.

1 · Check that records precede outcomes

Open the ledger and look at any open paper position: it has an entry, a stop and a target, but no outcome — because the outcome doesn't exist yet. Note its timestamp. When it closes, the row will gain an exit and a result while keeping the same opening timestamp you saw today. A service that fabricated records after the fact could not show you this intermediate state.

2 · Recompute a net figure

Pick any closed trade. The row shows gross bps, net bps and the cost model. Gross minus net is the modeled cost of that round trip — check it's in a plausible range for taker fees + slippage + funding (tens of bps, not zero, not fantasy). If we ever quoted a net better than its gross, you'd have caught us in one subtraction.

3 · Cross-check the tiles against the rows

The stat tiles at the top are computed from the same rows you can count yourself. Closed trades, target hits, summed net — all of it reproducible from the table below it. No hidden aggregation.

4 · Watch one signal arrive

The strongest check takes patience: keep the ledger open (it refreshes itself) and wait for a new signal. You'll see it appear with its full plan while the outcome is genuinely unknown — to us as much as to you. That's the moment the whole model either means something or doesn't.

5 · Hold the labels against us

Small sample? The page says so. Engine down? The LIVE chip turns STALE by itself. Evaluation pending? Every page repeats it. If you ever find a claim on this site that the data behind it doesn't support, that's not a gotcha — it's a bug report we owe you thanks for.

Keep reading