Governance · allowed · gated · denied
Three words decide what leaves the building.
Every action an agent can take is allowed, gated, or denied by its role. Allowed runs. Denied stops. Gated pauses the run and asks the Board. That is the whole model, and an agent cannot change it.
| Action | Default | Applies to |
|---|---|---|
| Read CRM | allowed | Research, Comms |
| Draft email | allowed | Comms |
| Send email outside the org | gated | Comms |
| Post to a public Slack channel | gated | Comms |
| Open a pull request | allowed | Code |
| Merge to main | gated | Code |
| Deploy to production | gated | Code |
| Spend over $5 in one run | gated | All |
| Make a purchase | gated | Browser |
| Delete a record | denied | All |
| Change own policy | denied | All |
| Hire an agent | denied | All |
Gated
The run pauses. You get one card.
What the agent wants to do, on what, for how much. Approve, reject, or edit and approve. The decision, the approver and the timestamp are written to the run.
One direction only
Policies can be tightened by anyone on the Board. Loosened only by an owner.
An agent has no path to either. There is no tool call, prompt or Skill that reaches the policy table.
Budgets are gates too
Hard stop, not a warning.
Per agent per month and per run. When the cap is hit, the run pauses at the next tool call and asks for more. It does not finish quietly over budget.
Hold the gate yourself.
The sample run on the landing page stops and waits for you.