The decision set being compared
A replay corpus is a declared set of pinned decision cases: for each case, the exact rule bytes, the exact input bytes, and the expected receipt lineage. Replay compares each case's recorded evidence against the baseline you name — a version or a directory of receipts — and reports whether the recorded behavior changed.
Despite the shared word, vouch replay has nothing to do with replay
prevention. This command re-checks recorded decisions; preventing an old
grant or report from being reused is an application control that Vouch never
provides.
Freeze the evidence before comparing
- Freeze the corpus inventory before comparison, and classify every item as agree, mismatch, or not-comparable.
- Preserve runner identity, rule bytes, input bytes, and result observations so the comparison can be reproduced.
- Review mismatch cases as behavior changes; do not regenerate old receipts to erase history.
Compare with a baseline
lispex vouch replay gallery \
--against <baseline-version-or-receipts-dir>Read every reported mismatch and not-comparable case. A clean summary is useful only when the corpus and baseline were chosen before the outcome was known.
A common mistake
Not-comparable is a disclosed boundary, not a mismatch silently counted as agreement. A case that could not be compared tells you the comparison did not happen — never read it as a pass.
Keep going
Keep the Vouch overview nearby: it separates authentication, request binding, current execution agreement, and a local grant.