Review Node
The Review node is a gate that pauses the workflow until a reviewer approves, rejects, or requests revision. It is the primary mechanism for mixing human judgment into an otherwise automated pipeline.
When to use
Section titled “When to use”Insert a Review node before any destructive or irreversible operation — deployments, data migrations, publishing content, submitting to external systems. You can also use it to check intermediate artifacts and ask for rework if quality is insufficient.
Reviews are always decided by a person, through the HQ dashboard. Any member of the project the run belongs to can approve (people who can only view the project can’t). Older workflows may still name a minion or a role as the reviewer; those reviews are treated as human reviews too.
Configuration
Section titled “Configuration”| Field | Description |
|---|---|
review.preferred_reviewer_id | Optional. The person to ask first: the review notification goes to them (if they are still a project member) instead of to every project member. |
criteria | What the reviewer should check. Shown in the dashboard next to the approve / reject / request-revision buttons. |
revision_target | Auto-populated when you draw a revision edge from the review node back to an ancestor. The node to rerun if revision is requested. |
The revision target must be an ancestor of the review node — reachable forward through non-revision edges. Otherwise the revision loop cannot actually revisit the node you picked.
Behavior
Section titled “Behavior”- When cascade reaches the Review node, it is inserted as
waitingwithreview_status: review_pendingand sits there. - The project’s members are notified, and one of them submits a decision in the dashboard:
- approved — cascade continues along the approved outgoing edge.
- revision — the revision target is re-executed with revised context; the review node itself will reopen once that target’s re-run settles.
- rejected — the graph halts at this node.
Validation rules
Section titled “Validation rules”reviewconfig block is required.criteriamust be non-empty.revision_targetmust reference an existing node that is a forward-ancestor of the review node.- The review node must have at least one approved outgoing edge (or an approved io-edge to the template Out marker, if inside a fan-out template). Otherwise the happy path cannot continue after approval.
- A revision edge must exist from the review node to the revision target.
Example
Section titled “Example”flowchart LR Draft["Skill: draft-post"] --> R{"Review"} R -->|approved| Publish["Skill: publish"] R -. revision .-> DraftThe revision edge (dotted) sends the flow back to draft-post when the reviewer asks for changes. When draft-post finishes again, the review reopens automatically.