Establish organizational control without taking autonomy away from the teams that build agents.
Organizational control over every agent in production, without turning every change into an approval queue. The organization defines who owns each agent and what it can do; teams keep shipping at their own pace, within those limits.
Keep visibility into agents, owners, environments, versions and status.
Every agent has an owner and a passport per environment, with each answer marked as declared, enforced or not covered. If the passport does not allow it, deployment to production is blocked.
Manage permissions, resources and boundaries. Approval is a step in the flow, with its own expiry and audience: four-eyes review is part of the agent's design, not a hook added after an incident.
Keep a traceable history of prompts, policies, configurations and versions.
Connect governance to the runtime: pause, step through, breakpoint, and a kill switch that cancels in-flight runs, per tenant.
The same policy, the same passport and the same trail, enforced at the model gateway, the tool proxy and the trace.
A sensitive action waits for two people, with a deadline. Nobody decided in time? It is denied. Nothing depends on someone remembering.
Who asked, which rule, who approved and why, hash-chained and reproducible. The regulator gets the run, not a log search.