/miroir/evidence/evidence.db. miroir collect writes it once,
after the agent stops, and the grader reads a copy.
What checks read
Read the tables the grader adds in memory, not the JSON inchanges. It builds a before and an
after table for every captured table, plus answer:
Rows absent from
changes are as baked. Ignored tables, ignored columns, tables created after the
bake, files and git refs are not in the evidence, so no check can read them.
Values
Values keep their JSON types:- booleans read as 1 or 0, and JSON objects and arrays as JSON text;
timestamptzreads as2026-11-17T10:00:00+00:00, andtimestampas2026-11-17T10:00:00(UTC);- dates read as
YYYY-MM-DD, and Unix times as integers; numericreads as REAL;- a value nested past 126 levels, or a number past a double’s range, reads as its JSON text.
1.5 to 1.50) is an update, even though both images read the same REAL.
The file
Check recipes
These patterns cover the fixture’s checks and the Gitea example’s. One row reaches a value (close-won-deal):
reassign-stale-deals):
log-call-activities):
merge-duplicate-contacts):
offboard, where the generator knows how many teams the leaver is on):
redact-secret, whose world holds the leaked key in one comment only):
notify-new-owner, pay-invoice):
reassign-stale-deals; Gitea’s
ship-release):
SELECT number = 3 FROM answer for a count, SELECT ids = '41,57,63' FROM answer for a
list of ids in any order or format, and SELECT value = '<text>' FROM answer for an exact text.