Approvals & Budgets

Autonomy at machine speed,
judgment at human speed

Most agent actions should flow instantly. A few should wait for a person. govern.sh routes exactly those few to your team in Slack or email — and caps what every agent can spend along the way.

Human in the loop

One tap between an agent and a $400 refund

When a policy says a human decides, the action pauses and the request lands where your team already lives — with everything needed to decide in one glance. Approve and the call proceeds; deny and it never happens.

Approve or deny from Slack or email — no new dashboard for your team to babysit

Route by team, amount, or tool, and escalate automatically when the first approver is away

Unanswered requests expire to deny — pending never means permitted

refund-agent requestedstripe.refund · $412.00 · order #58201now
Policy evaluatedpayments-guardrail · approval requirednow
Approved by Dana K.Receipt rcp_8f2a…c41 signed & chainednow
refund-agent
Monthly budget
resets in 17d
$341.20of $500 cap
$0approval > $250$500
API tokens · daily
42%
Emails sent · daily
59%
Auto-pauses at cap · alert fired at 80%
Budgets

Spend caps that end runaway loops

Give every agent a budget the same way you give it scopes. Spend is metered inside the policy decision itself, so the cap is enforced on the call that would breach it — not discovered on the invoice.

Per-agent budgets by day, month, or campaign — across every tool the agent touches

Alerts at thresholds you set, automatic pause at the cap — before finance notices

Thresholds and caps compose — over $250 asks a human, over $500 stops cold

Workflow

Sign-off that keeps up with your fleet

Approvals are only useful if people actually answer them. Every part of the workflow is built to keep decisions fast — and to fail safe when they are not.

Slack-native approvals

Requests land in the channel your team already watches, with the agent, action, amount, and policy that triggered the hold.

Email fallback

Approvers outside Slack get the same one-tap decision by email — signed links, no login, no new tool to learn.

Escalation chains

Route by team, tool, or amount. If the first approver is away, the request escalates instead of expiring silently.

Fail-closed expiry

Unanswered requests expire to deny on a timer you set. Pending never quietly becomes permitted.

Budgets & caps

Per-agent spending limits by day, month, or campaign — metered across every tool the agent touches.

Signed outcomes

Every approval and denial lands in the audit trail as a chained receipt — including who decided, and when.

Put a human exactly where it matters.

Set your first approval threshold in minutes and let everything under it run at machine speed. Free for your first three agents.