overview / commands / rabadon audit
rabadon audit [--days N]Verify the hash-chained spool. Every event carries prev = the seal of the previous line in its day file (HMAC-SHA256 under $RABADON_DIR/chain.key, or plain SHA-256 on a day opened without a key). This re-walks the chain and answers one question: was the ledger edited after the fact? A broken link is named by file and line.
maturity: stable — shipping and tested
Beside each day file sits a .head sidecar committing two facts under the same lock: the last hash and how many chained lines the file must have. A file carrying lines but no sidecar — a legacy writer, or a day older than chaining — is UNVERIFIABLE and reported as such, never folded into the clean count. "I do not know" must not read as "clean", which is why there are three exits and not two. (This page said "tolerated" and listed two exits for a fortnight after the code stopped doing that.)
Flags: --days N (window, default 7).
Exit: 0 every file verified against its sidecar · 1 at least one broken link (tamper) · 2 nothing broken, but at least one file cannot be verified.
How much disk does the ledger use? · Is the ledger really unedited?