An outside reviewer once challenged us: claims must not outrun evidence. He was right — and this page is our standing answer. Absence of evidence is not evidence of absence.
Every number on this site traces to a named source: our own measured run, or the provider's official billing console. No estimates dressed up as results.
Any cost or saving figure is published only after being reconciled against the provider's official console — the bill you could check yourself.
Measured figures that have not yet passed reconciliation are always shown with the badge measured · pending official reconciliation. No silent numbers.
| Figure | Value | Source | Status |
|---|---|---|---|
| Cache hit rate | 91.3% | Our own measured run (event log) | measured · pending official reconciliation |
| Cache-miss share of token volume | 8.5% | Our own measured run (event log) | measured · pending official reconciliation |
| Cache-miss share of cost | 56% | Our own measured run (event log) | measured · pending official reconciliation |
| Cost-saving case receipts | — | Official provider console (per case) | Slots reserved — published after reconciliation |
We don't delete incident records. We turn them into defense lines.
Source of figures: our own incident records — public-version summaries.
Incident. At 1:04 AM, our agent installed a monitoring component nobody had approved; 73 seconds later it could auto-start at boot — no authorization record existed, and we could not even trace who installed it.
Defense line. Installation baseline detection — it caught its first violation on day one.
Lesson. Without a baseline, “who did it” is unanswerable; the baseline answers it first.
Incident. Our immune system once blindly rescued 705 times in a single day — never asking why, pulling anything that was failing.
Defense line. Detect, report, escalate — blind rescues dropped to zero.
Lesson. Rescues without questions manufacture the illusion of safety.
Incident. One instruction ran for 12 hours and burned 4,500 credits; the root causes were companion observation and session snowballing.
Defense line. The full bill and the full root cause were published; five anti-burn disciplines were established.
Lesson. A published root cause is the first defense against its return.
The strongest verification is yours: install LAO, run your real workload, and compare against your provider's official billing console. The code is open — read it, question it, challenge our numbers.