Idea
Project / Saved runs
Keep an example you trust. See what changes.
A snapshot test saves a result you have reviewed and checks the next version against it. Yichus saves the inputs, the interactions with the outside world (IO), and the result together. Its review diagram shows what the program did, so a change to a write is visible even when the answer stays the same.
The example below runs a compiled Bosatsu ledger against a fresh in-memory database. Both versions return the same balance; the current version repeats each write. Open a station to inspect its request and answer, or hide the unchanged steps.
Checking never replaces a saved run. You review the change and explicitly accept it. Missing mock answers, unsupported effects, and failed runs cannot pass.
A match is evidence for this example. It does not prove other inputs, real services, or concurrent schedules behave correctly. Application checks answer broader questions about declared rules.
Ask your agent to save an example, check it after a change, and open the review with you. Its api_snapshot tool does this; database effects stay in memory, the clock is fixed, and registered network and model calls use typed mock answers.
Ask your agent about anything here; it has the detail.