Work is run against real conditions while a person is still watching it.

Managed AI Operations, after launch.
Control operates one standard-risk production environment from $900 per month after launch. No per-agent fees. You keep a legible workflow boundary, transparent AI usage, named approvals, and recovery context. Control includes Map.
- Signal Watch
- Decision Route
- Proof Record
Governance holds the decision boundary.
Control keeps delegated work moving because the operating boundary, authority, and exception path are written down before the run begins.
Scope, authority, and stop conditions are declared before the first run.
When the work leaves known conditions, Control waits for a named owner.
Shipped, blocked, or recovered — with the receipt and the next owner attached.
Control is one operating decision, made once and kept.
Control shows one operating decision at a time. Set the workflow boundary, see where judgment moves, choose a review rhythm, and keep every state in one owned system.
One governed workflow keeps one shared definition.
Map supplies the approved workflow definition. Control adds live Signal intake, Decision routing, Proof, policy, approvals, runs, blocked states, receipts, and recovery without creating a second system of record.
- Standalone subscription
- One governed workflow
- One shared definition
Three operator surfaces form one governed product.
Signal, Decision, and Proof are included operating surfaces, not separate licenses.
Capture the source, owner, affected system, and reason the work needs attention.
- Operator Inbox
- Source context
- Named ownership
Decide whether work can run, must wait for approval, or should stop with a reason.
- Run / wait / stop
- Approval state
- Policy reason
Keep the evidence, decision, outcome, receipt, rollback note, and next owner together.
- Audit trail
- Recovery context
- Workflow receipt
Pay for accountable operation, not an agent roster.
AI usage stays in your account when practical or is separately metered and reported. At 75% of forecasted monthly coverage, we schedule a capacity review—not an automatic charge. New workflows and integrations are separately scoped through Build.
For one standard-risk managed production environment. No per-agent fees. Control includes Map.
- Runtime oversight
- Incident response
- Monthly operating review
Keep the same governed product while risk, volume, and service expectations are reviewed explicitly.
- Control includes Map
- Annual boundary review
- Higher-risk operation is custom
See the operating boundary before work runs.
Inspect what the workflow depends on, who can act, what changed, and which evidence supports the current state. Unknown and stale claims stay visible instead of becoming implied permission.
See the operating boundary before work runs.
Public worked example. No production tools or private client records.
Define the workflow or bring the one already running.
Use Map when the system still needs a shared definition. Use Build for new workflows and integrations. Bring a launched workflow to Control when it needs accountable operation, approvals, evidence, and recovery.
- Owner
- Workflow operator
- Authority
- Named approval boundary
- Proof
- Map + run + receipt
- State
- ready