Offline, read-only validation of exported policy decisions and override events. The original decision is a separate record: an override refers to it and carries an originalResult copy, which must agree with that record. The audit assesses a supplied time, so its output is reproducible.
This walkthrough uses the tool's public README and checked-in example files. Run the command from a repository checkout with Node.js 22+; inspect the source before using it on your own files.
Run the checked-in example
node bin/manual-override-auditor.mjs --root examples --input passing.json --as-of 2026-01-02T00:00:00Z
node bin/manual-override-auditor.mjs --root examples --input failing.json --as-of 2026-01-02T00:00:00Z --human
npm run checkRead the result
--root names the evidence directory. --input is relative to it. --as-of is a required exact UTC timestamp. Optional --out report.json writes the same JSON report inside the root after destination checks. JSON always goes to stdout; --human adds a brief summary to stderr. --help lists options. A bad CLI option/configuration gives exit 2 with empty stdout. An unreadable, non-UTF-8, malformed or unsupported input gives an incomplete JSON report and exit 2.
Where this check stops
This local walkthrough does not establish the state of a live production system or replace the limits documented in the repository.
Before adapting the command to your own workflow, review the accepted inputs, exit codes and safety boundaries in the README.
Compiled with AI assistance from checked-in public documentation and example scripts. Run the example and review the repository's current documentation before relying on its result.