approval-gate / default

To add an operator approval gate, use the approval-gate stage to assemble a structured decision card from the action’s plan, drafts, and context references. The workflow pauses for operator input, records the decision, and proceeds safely based on the selected recommendation.

Workflow gating for artifact review is a stop-signal mechanism that pauses automated pipelines to assemble an operator-ready decision card. It loads required context refs and artifact excerpts, ensuring operators have complete information before approving or rejecting irreversible actions.

You maintain an audit trail for human-in-the-loop decisions by capturing operator inputs in a structured operator_decision block. This records the selected recommendation and re-entry data, enabling downstream calibration and dataset analysis to learn from past approvals.

Yes, you can use workflow gating for both reversible and irreversible artifacts with financial or stop-signal risks. The gate applies to approval gates across arbitrary playbooks, resolving context refs and artifact refs to support correctly-scoped go/no-go approvals.

An operator approval decision card should include canonical recommended options: approve, reject, need-context, and human-required. The card structures information into WHAT, SO, SEE, and LINK sections with required per-option descriptions to clarify what is being approved.

Context loading fails at the approval stage when the gate cannot resolve required context refs or select SEE excerpts from the latest draft trail. The gate depends on resolving these references to prevent missing critical information and satisfy schema-valid awaiting operator requirements.