Governance and human approval
Currently a single skill fills this role: leaving an explicit pause so a person can approve or reject an artifact before the flow continues.
lippia-neo-relay-human-approval
When to use it
As a human approval gate within a declarative plan (M4, crowdar-engine-mvp engine),
when the caller sets requires_approval: true on an artifact generated earlier in the
plan (for example, a regression test). Its only function is to relay a decision that a
person already made outside this invocation — it never makes or infers that decision itself.
Interim design
This is an interim design while ADR-015 (approval workflows engine) is still pending: the
current engine doesn't have native pause/resume, so the plan stops in the stopped state on the
first trigger (no decision yet) and is invoked again in full once the person has
decided.
{
"input": {
"regression_test": { "path": "tests/regression/US-045-cupon.spec.ts" },
"approval_decision": "approved",
"approver": "qa-lead@crowdaronline.com"
}
}
| Input | Type | Description |
|---|---|---|
input.regression_test |
Required | The artifact approval is being requested for (it's also used to build the summary). |
input.approval_decision |
Optional | "approved" | "rejected"; missing or null means there's no human decision yet. |
input.approver |
Optional | Name or handle of the person deciding, for traceability. |
input.approval_notes |
Optional | Comment from the approver (reason for rejection, conditions, etc.). |
Output
| Field | Description |
|---|---|
approved |
Boolean, true only if input.approval_decision == "approved", never inferred. |
status |
approved | rejected | pending. |
reason |
Explains the status (reason, confirmation, or what's missing to unblock the pending state). |
summary |
2-3 line summary of what's being approved, built only from content present in regression_test. |
approver |
The value received in the input, or null. |
requested_changes |
Present only if status == rejected. |
Chains with
Acts as a gate after a previous step of the M4 plan has generated the regression_test; if the
status stays pending or rejected, the plan stops, and it's the caller (for example, the
CI adapter) that triggers the full plan again after capturing the human decision.
Currently none of the plans published in crowdar-engine-mvp/plans/ include this gate yet.