Reconciliation certificates — at1 reconcile
Does the bank statement agree with the till tape? at1 reconcile run joins two sealed archives under a hashed rule set and emits a signed certificate: the matches, and the residuals — the genuinely unmatched rows on each side. An independent auditor runs at1 reconcile verify and re-confirms the verdict from the certificate alone— no raw rows, no our binary. The certificate proves the matched and residual rows together account for every row, so a silently-dropped unmatched line is made cryptographically impossible.
Use it
# reconcile two archives under a rule set -> signed certificate + attested residual list
at1 reconcile run bank.csv pos.csv --rules R.json -o cert.json --residuals-out X.csv
# an independent auditor re-checks the verdict from the certificate alone (free, no raw rows)
at1 reconcile verify cert.jsonWhat it proves
- Partition-completeness — matched rows and residual rows together cover the whole archive, disjoint, per side; no row can vanish.
- Residual authenticity — the attested unmatched list on each side is the thing an audit shop actually buys.
- Reproducibility — money is carried as integer cents and dates as day-ordinals, so the certificate hash is byte-stable and re-running the same inputs reproduces it exactly.
Honest scope: membership, partition-completeness and residual authenticity are cryptographically unconditional; match-honesty is a probabilistic Fiat-Shamir spot-audit(challenge-selected matches re-checked, so the prover cannot cherry-pick which). This is not zero-knowledge — the spot-audit reveals part of the matched rows by design.
Part of the Regulated Archive family alongside AT-1 Ledger and Regulated Archive. See the Reconciliation product page.