Replaying a Decision Corpus

Replay compares a frozen set of pinned decision cases and expected receipt lineage against a new rule or receipt set, and classifies every case as agree, mismatch, or not-comparable.

The decision set being compared

A replay corpus is a declared set of pinned decision cases. Each case holds 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, either a version or a directory of receipts, and reports whether the recorded behavior changed.

vouch replay re-checks recorded decisions. The host application owns replay protection for grants and reports through its freshness and one-time-use policy.

Freeze the evidence before comparing

  • Freeze the corpus inventory before comparison. The report classifies every case 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 and preserve historical receipts as the earlier baseline.

Compare with a baseline

SH
lispex vouch replay gallery \
  --against <baseline-version-or-receipts-dir>

The npm CLI provides this command. 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.

Comparison statuses

not-comparable records that the named executors produced no comparison for that case. It remains distinct from both agreement and mismatch in the report.

Keep going

Keep the Vouch overview nearby. It separates authentication, request binding, current execution agreement, and a local grant.

Lispex Vouch overview · Choosing Where to Run

Replaying a Decision Corpus · Lispex