Approval gates
Dual control, for agents.
Sensitive actions wait for a named reviewer. The decision, the rule, and the rationale go on the record.
Approval gates ship in the customer-cloud distribution. The public CLI records telemetry.
Approval queue
Illustrative · demo data

Every resolution lands in the audit trail.
01Controls evidenced
Three controls, one gate.
One approval record answers three tests: EU AI Act oversight, FFIEC dual control, DORA fail-closed.
- Catalog entry
How the session record supports it
Configured runtime gates hold actions for reviewers and record their decisions.
Approval decision records
- FFIEC.SOD-01Evidence mapping
Separate review duties
Information Security booklet: separation of duties
Catalog entryHow the session record supports it
Portal role checks restrict approval actions and support independent review.
Portal access checks
- Catalog entry
How the session record supports it
The runtime approval provider blocks configured actions on timeout or transport failure.
Approval decision records
02Decision loop
How every tool call gets evaluated.
Fixed rules decide first. A risk score weighs the tool, the policy, and past approvals. A model never decides.
Allow
Low-risk reads and checks run straight through.
Confirm
The action waits for a named reviewer.
Block
Policy violations stop before they run. The block is recorded.
03Why teams adopt it
Engineers keep their tools. Security keeps the gate.
- Approve before it executes
- Destructive commands and external writes pause for a named reviewer.
- One policy everywhere
- The same rules and audit format on laptops, CI, and cloud workers.
04Deployment
Validated on AWS today
Bedrock inference and IAM-scoped workers run in your AWS account. One-stack portal deployment is in progress. Azure and Google Cloud are roadmap.
Try it on one repo
Approvals and audit on one real workflow, with evidence for the controls above.