backdown custody
The chain of custody: every copy, move, deletion, link and merge BackDown made, in a hash-chained log sealed with this installation's key. Export it as a signed bundle, verify one, or check the log in the index.
On this page
backdown custody [OPTIONS] <COMMAND>backdown custody export
Write the chain of custody as a signed JSON bundle, sealing it first. With a filter, the events that don't match are elided: only their number, digest and hash are kept, so the chain still checks from end to end without showing their paths.
backdown custody export [OPTIONS] --out <FILE>Options
--out <FILE>- The file to write (never overwritten), or - for standard output.
--since <DATE>- Only show what was done from this day on (UTC): 2026-10-01, or 2026-10-01T14:30.
--ref <JOB>- Only show one job's events: plan:N, wipe:N, dedup:N, merge:N, rescue:N or mirror:N.
--path <PREFIX>- Only show what was done to files in this folder (or to this file).
backdown custody verify
Check an exported bundle: every event against its hash and the one before it, every seal's signature, that the seals reach the last event, and the bundle's own signature. Exits 1, saying what doesn't check out, if anything doesn't.
backdown custody verify [OPTIONS] <FILE>Arguments
<FILE>-
Options
--json- Print it as JSON, for scripts.
backdown custody check
Check the chain of custody in the index the same way: whether anyone changed the database behind BackDown's back. Exits 1 if anything doesn't check out.
backdown custody check [OPTIONS]Options
--json- Print it as JSON, for scripts.
All of them also take the global options --db and --local.
See also
Last updated · What's released, and what's next