Automation infrastructure.
Create, inspect and control automated workflows — with a person in the loop wherever an action leaves the system.
Active workflows
Today
Synthetic- Runs
- 348 99.1 % succeeded
- Pending approvals
- 3 oldest 22 min
- Median run time
- 8.4 s all workflows
Steady growth with a weekly dip: the two troughs are weekends, when only the scheduled workflows run.
Scope of this pilot
What is real on this page and what is not›
Real: the interface and the execution model, including the approval gate before any outbound action, with keyboard navigation, focus states and reduced-motion support.
Not real: every workflow, run, agent and integration listed. Nothing executes; there is no engine behind this page.
Six steps, one of them a person.
The approval step is a node in the flow rather than a setting in a menu, because that is what makes the boundary enforceable.
Flow
Why a gate at all
An automation that can act without review is only as trustworthy as its worst input›
Putting approval in the execution model rather than in policy documentation is the difference between a rule and a control. A documented rule depends on everyone remembering it; a node in the flow cannot be skipped by forgetting.
Explicit tools, explicit permissions.
An agent’s reach is visible on the same line as its name, so an over-broad permission is noticed rather than discovered later.
Registered
Every run keeps its reasoning.
Inputs, decisions and outputs are retained together, which is what makes a failed run diagnosable rather than merely reported.
Recent runs
The gate between a decision and an effect.
Three runs are waiting for a person. Each one has stopped before its action, not after it.