No pre-execution assurance.
Model validation happens before deployment. Audit happens after execution. Nothing checks the individual decision in between, where the consequences start.
OpenSAFR is an open schema, conformance suite, and reference implementation for SAFR, the industry reference approach for governing agentic AI in financial services at the point of action.
Financial institutions are moving AI from recommending to executing: payments, trades, credit decisions, filings. The SAFR whitepaper identifies three gaps in how that is governed today.
Model validation happens before deployment. Audit happens after execution. Nothing checks the individual decision in between, where the consequences start.
Human review is often an email alert or a dashboard flag, with no deadline, no defined decision, and no record of what was decided.
Where guardrails exist, each deployment built its own. The controls don't interoperate and the records don't share a format.
A shared schema is the fix for the third gap, and it makes the first two auditable. That's what OpenSAFR is building.
Every proposed action is declared, verified, assessed against controls, given exactly one outcome, and recorded.
A language-agnostic schema for the envelope and audit record, so records from different agents and vendors can be read the same way.
Test vectors and a runner that check whether an implementation produces the right disposition and a valid record for a given envelope.
Python and TypeScript libraries for emitting envelopes and validating records.
A working gate with a tiered policy pack, built first for cross-border private banking.
Following the pattern of OpenTelemetry and OAuth: a spec repository, separate SDK repositories, and a public conformance suite.
An agentic wealth-advisory layer governed end to end by SAFR components. The same agent, the same portfolio, and the same market signal across three clients produce three different outcomes: executed, queued for the relationship manager, or blocked. The mandate decides, not the model.
See the implementation →An open schema, conformance suite, and reference implementation for SAFR. What it is, why the schema comes first, and what it isn't.
The source document. Defines the envelope, the four components, and the four outcomes. Start here.
Practical guidance including agent-specific practices: least privilege, kill switches, searchable logging. SAFR builds on this groundwork.
Singapore's governance framing for agents: bounding use cases, limiting access, human oversight, accountability.
A three-layer model for agentic payments that identifies control and authorisation as the critical governance point.
SAFR's authors describe it as a starting point that should evolve through implementation experience. OpenSAFR is where that experience can become shared, testable artefacts. We're looking for engineers building agent platforms, risk and compliance teams at financial institutions, and auditors who will have to read these records.