Documents

Sample output

What an evidence file actually looks like

The file below is not marketing copy. It is the evidence output the system produced for a single request: who asked, the rule set in force that day, the timeline, the script fingerprint, the risk rationale, the masking decision and the verified audit records.

The sections worth reading are "10. Exceptions", "12. Field Verification" and "13. Event Time and Ledger Commit Time". In this sample the organisation setting did not enforce segregation of duties and parse warnings were confirmed and bypassed; the file records both as exceptions rather than hiding them. All 116 fields read from the tables were compared with the ledger and matched. Governance is not measured by the absence of violations but by whether they surface.

The sample was produced by a real flow in the product's development environment and has not been modified since. User and server names belong to the test environment. You can download the whole package (zip) and check it yourself with the Verify.ps1 inside.

In a delivery this PDF does not travel alone. It goes inside a zip together with the machine readable form of the data, a manifest listing the digest of every file in the package, the RSA signature over that manifest, the public key, the verification script and, when timestamping is on, Manifest.tsr. The Auditor Kit document, which sets out the verification steps, is available on request.