
Proof, before and after.
Evals gate what ships. Every action is classified, signed and traced. Approvals sit where the stakes are — and the evidence pack exports when the auditor asks.
Security teams approve agents when they can see every action. Make that the default and the pilot conversation ends.
Classification coverage, signed actions, one export.
EU AI Act classes with counts, the share of actions signed, and the proposals still waiting on a named person.
High-risk actions always require a justification and a human.
1,284 of 1,284 · hash chain verified
What the governance layer does.
Evals as acceptance criteria
Code-based where possible, calibrated judges where needed, human review last. Every change runs the suite.
Review routed by stakes
Pre-action approval for the irreversible and the costly, post-action audit for the reversible, sampling for the rest.
One trace, three audiences
The person affected, the regulator, and your own team — from the same record.
Obligation → control → owner → evidence
A compliance register that resolves to named owners, and an evidence pack that is a signed, verifiable snapshot.
Where this shows up in the work.
Audit-trail explorer
Click any field and walk the decision back to the page it came from.
Open the explorer →Trust Center
Residency, certification status and model risk, with dates rather than logos.
Read the Trust Center →Traces & cost
Tokens, latency and cost per run, with anomaly alerts at 150% of the seven-day average.
Onboard your first agent in three weeks.
One process first, live in under three weeks, with the evidence from day one.