The examination packageEvidence a third party can check .
One command exports a period-scoped, signed bundle for a stated reporting window. A second command checks that bundle standalone, with no database, no configuration and no key of ours.
What the bundle is
A bundle is not an export of a console view. It is drawn from a record written at the moment each decision was made, one that cannot be quietly edited afterwards, and it carries three properties a recipient can act on.
The window it names, and nothing else
You state the reporting window at export, and it is fixed from then on. A reviewer who asked for one period receives exactly that period, not a filtered view of a live system that could be filtered differently tomorrow.
Byte-for-byte what was exported
The bundle is signed. If anything in it changed after export, whether in transit, in a mailbox, on a share or in the recipient’s own hands, verification says so rather than passing quietly.
Where the records came from
Each entry is written by the component that made the decision, at the moment it was made, rather than assembled afterwards from a console view.
Two commands
The export runs where your evidence lives. The verifier runs anywhere. That is the point: whoever you hand the bundle to can check it without access to your systems.
Export, then verify
$ redactwall export-examination-package # produces a signed bundle for the reporting window you state $ redactwall verify-examination-package # checks that bundle standalone: no database, no configuration, no key of ours
What a verification result tells you
A verification run does not answer with a bare pass or fail. It states what the bundle covers. The chain verifier works the same way, and names what it covered rather than only whether it passed. verified, tail uncovered means the whole record checked out, and the most recent entries are not yet covered by a signed checkpoint. Reporting that as a plain pass would let you read the run as covering more than it did.
Using it in a review
- Export at the close of the period rather than in the week the request arrives. The scope is fixed at export, so a bundle produced under time pressure is no more authoritative than one produced calmly.
- Hand the bundle to whoever asked, and hand them the verifier with it. They check what they were given before anyone relies on it, on their own machine.
- Run the chain verifier separately on your own systems and compare the result. The bundle check shows the bundle is unchanged. The chain check shows the record behind it has no gaps.
- Know what the package is for. It gives you material to hand to a reviewer. Disclosures states what RedactWall claims today.
See the coverage table for what each surface does, or start a pilot and export a bundle from your own window.