Skip to main content
The evidence is one SQLite file, /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 in changes. 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;
  • timestamptz reads as 2026-11-17T10:00:00+00:00, and timestamp as 2026-11-17T10:00:00 (UTC);
  • dates read as YYYY-MM-DD, and Unix times as integers;
  • numeric reads as REAL;
  • a value nested past 126 levels, or a number past a double’s range, reads as its JSON text.
A row counts as changed when the text Postgres wrote for it changed. So rewriting a numeric to a new scale (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):
A share of target rows reaches a value, for partial credit (reassign-stale-deals):
Rows the agent inserts, matched by content (log-call-activities):
A row deleted (merge-duplicate-contacts):
Baked rows that must go, counted with the identity of rule 2 (Gitea’s offboard, where the generator knows how many teams the leaver is on):
Text that must appear nowhere else, as a gate over every row the episode wrote (Gitea’s redact-secret, whose world holds the leaked key in one comment only):
A value the product sent (notify-new-owner, pay-invoice):
Nothing sent, or nothing sent elsewhere, as a gate (reassign-stale-deals; Gitea’s ship-release):
Answers: 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.