Resources
AI Agent Governance at the Runtime Boundary
Much of “AI governance” happens away from the action: model cards, training-time controls, offline evaluations, and post-hoc audit logs. Those artifacts matter for diligence. They do not intercept the moment an agent tries to change institutional state.
The runtime boundary is that moment. A proposed payment, record change, or customer message either proceeds, is withheld, or is routed. OntoGuard occupies that boundary. It interprets the proposed movement, returns a decision, and records whether a protected effect formed.
Customer-production enforcement still requires a connected route: identity, endpoints, and fail-closed behavior. Public proof on this site is controlled and sanitized. It is not a claim that every customer path is already non-bypassable.
Continue with what Decision Authorization is.
Continue: Proof Explorer · Inspect the AgenTrust TRACE integration · Explore the Headless Decision Authorization Runtime.
FAQ
What is the runtime boundary?
The moment before an agent action becomes an enterprise consequence.
Are evals enough?
Evals and model cards matter. They do not intercept the exact state transition.