stage-gatelisted

# Stage Gate ## Purpose Control progression by evidence and stop precisely at the user's Target Stage. ## Trigger Run when target-relevant work for a Stage appears complete, before entering downstream work, or when reassessing a paused/failed Stage. ## Inputs - Current Stage, Target Stage, Stage scope, Workflow Level, and Stage DoD. - Required Artifact IDs/revisions/statuses and validation evidence. - Applicable Clarification, Artifact, Component Quality, and Integration Gate results. - Traceability, open questions, assumptions, decisions, risks, deviations, and Current Minimum Necessary Path. ## Prerequisites - Normalize the stage/target and identify only Artifacts required for the declared scope. - Gate evidence must apply to current revisions. ## Procedure 1. Check whether all target-required Stage Artifacts are complete and sufficiently `VALID`. 2. Check Artifact Validation and all applicable lower-level Gate verdicts. 3. Check every Stage DoD item at the effective Workflow Level. 4. Check traceability, accepted risks, unresolved deviations, assumptions, and Clarifications. 5. Determine whether failures require rework, clarification, or rollback to a responsible earlier layer. 6. Determine whether Current Stage equals Target Stage. 7. Record `PASS`, `FAIL`, `BLOCKED`, or `USER_DECISION_REQUIRED` with evidence and next action. 8. On PASS below target, update State and expose only the next ready Minimum Path node. 9. On PASS at target, create a Checkpoint, set pro