Rules the workflow enforces. The AI can't skip them.
Governance sits inside the workflow, not bolted on after the fact. The AI drives the conversation. At approval steps it pauses and waits for your yes. Every step is logged.
The proposal is ready. Sending it to the client is an approval step, so I'm pausing for your go‑ahead.
The AI can't advance this step on its own. It waits here until you reply with your yes.
- 7
- Gate types enforced structurally
- 100%
- Audit trail coverage
- 0
- Manual compliance docs needed
Conversation steps. Approval steps. The workflow decides which is which.
Every step in a workflow is either a conversation step or an approval step. The AI knows the difference because the workflow defines it — not because you prompt for it.
- Conversation step — the AI drives, you respond naturally as the work progresses.
- Approval step — the AI pauses and waits for your explicit yes before advancing.
- The workflow engine enforces the distinction. There is no prompt trick that skips an approval.
The AI cannot advance past an approval step without you.
Approval steps are not reminders or suggestions. They are halts. The conversation stops at the step, the workflow waits, and the AI has no path forward until a human says go.
- Rules live in the workflow — not in a system prompt the AI can reason around.
- Checkpoints are structural. The conversation cannot route around them.
- You decide where approvals go. Full autonomy between them.
Seven kinds of checkpoints. All enforced by the engine.
Every gate type the workflow supports is structural. The AI does not choose whether to honor a gate — the engine does. These are the seven, each doing one job well.
- Requires human approval — the conversation stops until a human says go.
- Child tasks must finish first — a parent step waits for every sub-task.
- All phases complete — a plan cannot close until every phase is verified.
- Task must be the right status — steps only run at the status the workflow expects.
- Task must be the right type — certain steps only apply to certain kinds of work.
- Wait for dependencies — a step waits until its listed dependencies are done.
- Sequential child order — children execute in the order the workflow defines, never in parallel.
Every step. Every change. Every decision. Logged automatically.
The audit trail is not a feature you turn on. It is the shape of the platform. By the time a compliance team asks for the record, it is already there — who did what, when, and the before-and-after values.
Pick the gate that matches the work.
Grid of the seven gate types — rendered as compact cards. Each gate is a primitive the workflow engine understands natively.
- Human approval — explicit yes required
- Child completion — parent waits for children
- Phase completion — plan waits for phases
- Status precondition — step requires a specific status
- Type precondition — step requires a specific task type
- Dependency wait — step blocks until dependencies close
- Sequential order — children execute in declared order
Rules the workflow enforces. The AI can't skip them.
Governance sits inside the workflow, not bolted on after the fact. The AI drives the conversation. At approval steps it pauses and waits for your yes. Every step is logged.