Compliance export
The hash-chained record of every screening, verdict and action Fuga Labs took, with whole-chain verification on export.
Hash-chained, verified end to end
Each record commits to its predecessor, so a deletion or an edit anywhere in the history breaks verification at export rather than passing silently. The export states the chain it verified.
- GET /v1/audit/export
- GET /v1/audit/summary
What is in it
Every screening and the source it consulted, every verdict and the evidence behind it, every action taken and the principal who authorised it, every configuration change including the ones that widened coverage.
What it is not
It covers OUR decisions. It is not a books-and-records export, it does not reconstruct your ledger, and it does not substitute for either. An examiner asking what you held needs your systems; an examiner asking what was screened and when needs this.
Where the boundary sits.
In the same type as everything above it, and paired with the control that covers it. This is the part your auditor reads first.
Put Compliance export on your perimeter.
Engine-level detail and the full catalogue are provisioned with your engagement, alongside the console your team works in.