ferraus verify
Check that a sidecar's inputs and outputs still match their hashes
Synopsis
ferraus verify <input> [options] [-o <output>]
What it does
Check that a sidecar's inputs and outputs still match their hashes
Examples
Confirm nothing changed since the run
ferraus verify take.tuned.wav.ferraus.json --json
Check a master against its provenance; exit code 9 if a hash differs
ferraus verify master.wav.ferraus.json
Silent check for scripts: only the exit code matters
ferraus verify stems/vocals.wav.ferraus.json --quiet
Global options
Every command also accepts the global options (-o, --json, --dry-run, --overwrite, --progress, ...). See Global options.
Exit codes
| Code | Meaning |
|---|---|
| 0 | Success |
| 1 | Processing failed |
| 2 | Usage or parameter error |
| 3 | Input missing or unreadable |
| 4 | Unsupported format or codec |
| 8 | Cancelled |
| 9 | Output verification failed (checksum, clipping guard, duration mismatch) |
| 70 | Internal error (bug) |
Common mistakes
- Forgetting that outputs are never overwritten: pass
--overwriteor a new-opath when re-running.
For models
- MCP tool:
ferraus_verify - Schema:
ferraus schema verify - Pipeline:
{ op: verify, args: { ... } }(flag names with_instead of-) - fx stage: no
{"command": "verify", "defaults": {}}