Know which rules applied.
Trace the request to its governing policy and verdict. Keep an approval decision distinct from an execution outcome.
Know where your AI agents need oversight.
See who is responsible, what agents are doing, and where actions need review. Connect activity to governing rules and the evidence behind each decision.
Start with the agents already at work.
Start with who is responsible for each agent.
Review registered agents alongside automation found in connected evidence. Keep unclaimed activity distinct until someone deliberately establishes ownership and rules.
Agent inventoryOwnership and connection evidence
Support assistant
Registered- Responsible
- Customer operations
- Connection evidence
- Governed action path
Account assistant
Registered- Responsible
- Customer success
- Connection evidence
- Observed activity
Report workflow
Discovered- Responsible
- Unassigned
- Connection evidence
- Imported log
Review the action alongside the authority behind it.
Follow a request to its rule and recorded decision. For imported activity, inspect what the source reports and what it cannot establish.
Enforced evidencePermit
The request passed its required checks.
- Request
- A $240 refund with a supporting customer ticket.
- Rule
- Refunds up to $500 may proceed when the required checks pass.
- Recorded decision
- Permitted through the governed path.
Outcome evidence
Execution has not yet been recorded for this request.
Follow the execution result before treating the refund as complete.
Human intervention
Pause the governed path while you review.
Authorized operators can hold an agent’s governed requests or apply a workspace-wide pause. Keep the reason, scope, and timing of the intervention on record.
The pause applies to that governance path. External runtimes and activity outside it need their own controls.
Explore operating limits and controlsKeep oversight explainable after the decision.
Activity changes and agents come and go. Preserve the authority, interventions, and evidence that explain the work at the time.
Follow what the team changed.
Review pauses, rule changes, and recorded lifecycle decisions with the responsible actor and timing attached.
See what the evidence establishes.
Separate enforced decisions from observed activity and missing records. Keep those limits in the review.
Give the reviewer the business context.
Bring relevant commitments, customer history, and source evidence into the conversation. People and connected agents can draw on shared knowledge within their permissions.
Have questions?
Do we need to move our agents to a new runtime?
No. Register and oversee agents you already run in your tools and environments. Connect supported activity sources for visibility and route supported actions through the governed path for enforcement. The controls available depend on how an agent is connected.
Can we find agents that have not been registered?
Where discovery and supported activity imports are enabled, connected evidence can reveal unregistered automation. It remains discovered and unowned until an authorized person deliberately claims it and establishes ownership and rules. Discovery depends on source coverage and is not a complete scan of every agent in the business.
Does registration mean every action is governed?
No. Registration establishes the agent’s identity, ownership, and governing configuration. Enforcement depends on the path each action takes. An imported event remains observed evidence even if the agent is registered, so reviews need to assess coverage at the action level.
What happens when an action needs approval?
A supported request through the governed path is held for an authorized reviewer. The request, applicable rule, and supporting context stay together in the approval gate. Approval does not bypass other permissions or operating limits, and a permit is distinct from evidence that execution completed.
What does pausing an agent stop?
An authorized operator can pause a registered agent’s governed actions or apply a workspace-wide governance pause. New attempts through that path are held while the pause applies, and the pause and resume remain on record. A governance pause does not shut down an external runtime or retroactively block activity imported after execution.
Can we retire an agent without losing its history?
Where decommissioning is enabled, an authorized person can retire a registered agent and revoke its governed authority while preserving its history and receipts. Recommissioning is a separate recorded action. Upstream credentials and external runtimes still need their own offboarding steps.
What can we establish from an agent’s record?
Review the recorded actor, request, rule, verdict, supporting evidence, and any reported outcome. Rule changes, pauses, and lifecycle events help explain the context at the time. Receipt verification checks record properties such as integrity and attribution; it does not prove that every event was captured or certify compliance.
Bring clearer oversight to the agents you run.
Connect ownership, activity, and governing rules with a record you can follow.