The audit is the log.
No upload. No screenshot.
OSCAL 1.1.2 bundles. Cedar predicates over the receipt stream. Compliance as a property of receipts, not a process performed on them.
Two ways in
One scenario. One artifact.
Eleven OSCAL controls satisfied. Derived from 31 receipts.
OFAC screening, beneficial-ownership disclosure, FinCEN Real-Estate Reporting Rule, CSRD energy disclosure. Every check is a Cedar predicate over receipts already in the log. 6 joules to compose the bundle.
OSCAL bundle viewer + Cedar playground.
Pick a control. See the predicate. Trace it to the upstream receipts that satisfy it. Edit the predicate, re-derive.
The receipt
Every operation. Every joule. Signed.
This is what ComplianceOS returns. Not just a result — a signed JWP ReceiptPayload with the energy consumed, the standard cited, and the cryptographic signature that makes it audit-grade.
What this platform believes
Three statements. Each is the proof of the next.
OFAC screening, beneficial-ownership disclosure, FinCEN Real-Estate Reporting Rule, CSRD energy disclosure. Every check is a Cedar predicate over receipts already in the log. 6 joules to compose the bundle.
Watch it happen →Pick a control. See the predicate. Trace it to the upstream receipts that satisfy it. Edit the predicate, re-derive.
Open the artifact →Same identity, same format, same billing unit (joules), same wire transport. ComplianceOS ships the part that handles predicate.
See the receipt format →