verify_consistency
Verify append-only integrity by re-deriving each chain tip and confirming it extends consistently from a prior anchor, catching rewrites, rollbacks, or re-signed history without trusting the operator.
Instructions
Detect an APPEND-ONLY VIOLATION against a prior_anchor an auditor recorded out of band: re-derive each
chain's tip and confirm the store is a consistent forward-extension of the witnessed anchor (nothing was
rewritten, rolled back, or re-signed away). Returns {consistent, problems}. This is the operator-adversarial
check verify_writes() cannot do on its own — it catches a store operator who forged history and re-signed it,
because the forged tip won't reconcile with the tip an outsider already pinned. Deterministic, no LLM.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"prior_anchor": "<prior_anchor>"
},
"name": "verify_consistency"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| prior_anchor | Yes |