The point where "we noticed it" becomes "we decided about it"
Govern is three different jobs kept in three different rooms on purpose: the rulebook that says what's allowed, the live feed of every decision it makes, and the place a human makes the call when the rulebook alone isn't enough.
A feed of decisions, not a feed of noise
Every allow, block, flag, and notify decision the policy layer makes, in real time, attributed to the rule that triggered it. In the last 24 hours: 68 blocked, 5 flagged, 12 allowed — a live ratio.
Stopped, and still on the record
Three states take an agent out of operation — rejected, suspended, blocked for cause — each preserving identity and full history. Containment isn't deletion.
| State | How it happens | Path back |
|---|---|---|
| Rejected at intake | A reviewer declined it during classification. | Re-review |
| Suspended | An operator paused it from the agent's own record. | One-click reactivate |
| Blocked for cause | Stopped because of something it actually did. | Re-review only — no one-click return |
Quarantine vs. block
Quarantine acts on the entity; block acts on a single action. Confuse them and you stop the wrong thing — or the right thing in a way that won't hold up.
Quarantine vs. suspend
Quarantine is the state; suspend is the action that puts something into it, taken from the agent's own page. One is a place, the other is a decision.
Nothing quarantined is ever deleted, because a regulator asking what happened to a specific agent needs an agent still there to ask about.
Scope is honest — the platform never claims control it doesn't have.
Four instruments. Not four flavours of the same one.
Block, hold, flag, or notify — each does a different job; we won't blur them into one severity dial. A rule shows how many agents it affects before you save it.
Block
Stops the action outright. The only instrument the coverage reporting counts as real enforcement.
Approval gate
Holds for a named human. The action pauses; it doesn't proceed until someone decides.
Flag
Allows, but marks for review. Useful, and honestly weaker than blocking — the product doesn't pretend otherwise.
Notify
Allows, and tells the governance team. Awareness without interruption. Counted as monitor-only, not enforcement.
Conditions combine with AND/OR logic, and scope is shown before it's saved — a rule never quietly governs more agents than the person writing it intended.
Where a person, not a policy, makes the final call
Anything a policy holds lands here, waiting on one named approver, not a timeout that resolves itself. This queue records every judgment call the system declined to make alone.
Approval today is single-approver by design — multi-stakeholder sign-off is roadmap, not shipped. A request cancelled because its policy was removed is recorded as cancelled, not folded into "approved."
Bring us the rule you can't currently enforce
The most useful first conversation is a policy you already want and can't apply today. We'll build it live and show you exactly which agents it would catch.