Receipts
Four shapes of receipt.
A receipt is more honest than a benchmark. We print four kinds.
01 · The joule receipt
Every call returns its joules.
A metered call doesn’t return a value. It returns a value and what it cost. You know what your pipeline costs before you ship it to a battery-powered drone.
- RSS safety envelope 37.2 pJ
- DAM-VLA route 6.2 µs · 4.1 pJ
- CAD transition (closed) 1.8 ns · 0.2 pJ
- Diffusion step 11.4 µs · 8.7 pJ
- Verifier (e-value · accept) 0.8 µs · 0.6 pJ
- Per-step total 219.7 pJ
02 · The epistemic receipt
Every claim labels its source.
A confident answer about what was true at training cutoff is a different object than a confident answer about what is true now. The substrate enforces the distinction.
03 · The evidence receipt
Verification earns its stop.
Evidence accumulates as an e-value. Stop when the bound is crossed. Easy claims halt in one step. Hard claims get the full check. The verifier never runs more compute than the evidence justifies.
04 · The routing receipt
Checkpoints that are byte-reproducible.
The router teacher is the cascade replayed as an oracle. No external model. No field-trace collection. Two independent runs with the same seed produce the same file, byte for byte.
The worked proof
Three solvers. One puzzle. Cryptographic hashes confirm they agree.
The sudoku exhibit runs this end-to-end — constraint-propagating CSP, brute force, and Z3, each emitting a typed receipt with wall time, ops counted, and joules spent.