recuriant

Governance is not a dashboard bolted on after the fact.

Every agent action in Recuriant passes through the same policy enforcement point before it runs — whether the agent is inside Recuriant or calling in from your terminal over MCP.

The policy enforcement point

Every step — an agent dispatch, a connector action, a workflow transition — is evaluated against policy before it executes. If the policy engine cannot reach a decision, the step is denied, not allowed. Nothing runs on a timeout or a missing config.

agent.dispatch role=support-agentallow
github.repo.deletedeny · no policy match
stripe.charge amount=$1,200.00L2 · pending
knowledge.queryL1 · allow

L1 / L2 / L3 tiers

L1

L1 — reversible, low blast radius

Runs immediately. Logged like everything else.

L2

L2 — higher impact or harder to reverse

Pauses for a durable human approval — a Temporal signal with a single-use token — before it executes.

L3

L3 — highest blast radius

Requires explicit, scoped authorization; the platform will not proceed on an assumed or inherited grant.

Per-dispatch, role-scoped identity

Every dispatched agent gets a short-lived, role-scoped identity minted for that run. A parent agent's scopes are the ceiling: a child agent it spawns can only receive a subset of them, never more. Tokens expire; nothing is long-lived by default.

# parent role: sre-oncall
scope: deploy:*, incident:*, chat:send

# spawned child — narrowed, never widened
run_agent(role="sre-triage")
scope: incident:read, chat:send
ttl: 15m

Every decision, logged

Every policy evaluation, approval and denial is written to a decision log — what ran, under which identity, at which tier, and why. A global kill switch can halt all agent execution immediately.

Replay and evals

Recorded runs can be replayed against policy and workflow changes before they go live, and a self-checking harness verifies workflow outcomes against their declared verify: conditions.

Cloud or your own VPC

Run Recuriant Cloud, or self-host in your own VPC with the same policy engine, approval flow and decision log. Enterprise plans add SSO / SCIM, audit retention and export, and compliance packs.

Read the governed workflow example

See an L2 approval gate in an actual workflow definition.