Add human stages on the Blueprint

Declare functional, code, and release gates in Designer so Command can open Human Review Tasks at runtime.

Last updated September 27, 2026

Add a human stage

  1. Open the flow in Build.
  2. Insert a human stage where a person must decide.
  3. Set the type: functional, code, or release.
  4. Assign a resolved reviewer. The task is not actionable until that principal exists.
  5. Attach the artifacts and environment the reviewer needs.
  6. Validate and compile.

Builder does not replace Reviews. The gate only becomes a Human Review Task when a Run reaches that stage.

Types

TypeUse when
functionalAccept behavior, often against a preview environment
codeAccept the candidate SHA
releaseAccept production and any v* tag

A release stage needs a production environment and a tag ruleset with an explicit bypass actor. See Environments and preview targets.

Decisions at runtime

On /reviews/:id the reviewer uses Approve, Request changes, or Reject. Reason is required unless Approve. Merge still needs native PR APPROVED on the exact candidate SHA.

Do not add a human stage and then leave reviewers empty to “decide later.” Compile fails closed.

Still stuck?Contact support