Evidence with citations
Every control finding is grounded in a source document and section. Reviewers and auditors can trace any claim back to where it came from - not to a model's recollection.
A governed AI-governance run, replayed end to end: source-grounded evidence, deterministic control checks across multiple frameworks, then a human approval gate where a governance officer signs off - obligations phase in over multiple milestones.
Read-only replay of an illustrative run - no inputs, no production credentials.
A real governed run, replayed in full below - ending in a human sign-off and an auditable proof packet.
Eight events, exactly as the platform recorded them - from intake to a human sign-off gate across frameworks. Nothing is simulated past what you see here.
An AI-system governance review was submitted across multiple control frameworks. The run is registered against flow ai-governance/v2 and begins under the workspace's controls - every step from here is recorded.
Three artifacts were parsed and source-grounded control evidence was extracted - each finding carries a citation back to the document and section it came from.
Deterministic checks ran against controls designed to support multiple frameworks. Most passed - one mitigation is outstanding, which the sign-off later accounts for.
Workspace policies were evaluated against the extracted evidence. One policy trigger fired on cross-border data transfer.
The findings were combined into a composite readiness score. The score is strong but a mitigation is outstanding, so the run is routed to a governance officer rather than auto-cleared.
Above the 75 threshold but with an outstanding item -> routed to a human sign-off gate. No attestation is issued automatically.
A governance officer examined the run and signed off at the gate across EU AI Act, NIST AI RMF, ISO 42001, and SOC 2 controls designed to support compliance. The outstanding mitigation is tracked with an owner and due date as part of the sign-off.
The run ended exactly where governance required: a person decided, the decision is logged, and there is a proof packet anyone can audit later. The sign-off is a human decision, not an automated attestation.
The replay is not a chatbot demo. It is the control plane doing its job: grounding, gating, and proof - the parts a regulator asks about.
Every control finding is grounded in a source document and section. Reviewers and auditors can trace any claim back to where it came from - not to a model's recollection.
A strong readiness score with an outstanding item routes to a governance officer, not an auto-attest. Here the officer signed off across EU AI Act, NIST AI RMF, ISO 42001, and SOC 2 controls designed to support compliance - with the mitigation tracked.
The decision, the officer, the reasons, and the cited evidence are written once to an append-only audit trail. Months later, you can prove exactly what was reviewed and signed off.
PrivateFlow is not certified under any compliance framework. Controls are designed to support compliance preparation. Where the EU AI Act applies, high-risk obligations carry penalties up to the EUR 15M / 3% of worldwide annual turnover tier; this run is an illustrative, synthetic example.
We'll stand up a governed pilot on your own data - sandbox first, no production credentials required. You decide what the gates do.