opschain governance evidence verify

packs:security-governance

opschain governance evidence verify

Verifies the evidence ledger's hash chain end to end, per segment (GovernanceService.VerifyEvidenceLedger): every row's hash and link is recomputed server-side. A valid chain reports the row count, head seq and head hash; an unacknowledged break names the first seq whose hash or link failed and the command exits non-zero — the auditor's one-command integrity check.

A chain re-anchored after a data-loss incident (see opschain governance evidence re-anchor) verifies clean again, but its acknowledged discontinuities are always listed, never suppressed:

rows 1-41 valid
ACKNOWLEDGED DISCONTINUITY at 42 (re-anchored 2026-10-27T03:14:07Z by admin: database incident with sustained data loss)
rows 43-57 valid
ledger valid — 57 row(s) scanned, 1 acknowledged discontinuity(ies), head seq 57 (…)

Rows archived into sealed segments by the retention sweep (opschain docs retention) stay covered: verification seeds at the sealed boundary's recorded closing hash, so the chain verifies across the archives, and the typed verdict reports archived_through_seq and archived_segments.

-o json / -o yaml emit the typed verdict, including the verified segments, the discontinuities and the archived boundary.

Exit codes

Code	Meaning
0	The chain is valid; any acknowledged discontinuities are listed.
1	The chain has an unacknowledged break (the output names the first broken seq), or the read failed.
2	Usage error, including a missing server target.