Component

Approval gate

Pause the workflow until the required review is complete.

Inputreviewer · anchor · rubricOutputpass · reason · status

Inputs

FieldTypeContract
reviewerstringhuman | agent. Default human.
anchorstringwhat is being decided about.
rubricstringREQUIRED when reviewer: agent.
escalateOnstringobjection hands a failed check to a person. Default objection.
modestringcheck is RESERVED — refused.

Outputs

FieldTypeContract
passbooleanreviewer: agent — the verdict.
reasonstringreviewer: agent — why.
statusstringreviewer: human — the run is waiting_human until qloop approve continues it or --reject fails it.

Behavior and limits

Human-Gate or Agent-Gate. One kind, two modes; they differ only in who decides. reviewer: human parks the run as waiting_human. reviewer: agent is a machine check whose verdict is {pass, reason}; today that check is an LLM judge. mode: check is RESERVED and refused. A human gate is optional. Without a key the agent-gate does not wave anything through — it escalates to a human.

Try it in context

Use the linked loops to inspect actual configuration and how output is passed to the next step. Keep credentials in your local environment.

Validation and run evidence

Run evidence not supplied. Release acceptance: pending.

No new validation or execution is performed by viewing this page.

No output artifact is available for this material.

Loops using this component

Explore example uses

Illustrative scenarios based on these loops. These are ideas to adapt, not verified customer results.

Make it your own

One prompt to your result

Your agent handles setup, configuration and checking the result in your project.