paw-transition

To enforce session policy at stage boundaries, a gated transition mechanism validates the current state and checks preflight requirements before progressing. This ensures continuous flow or per-stage policies are applied before moving to the next activity.

Workflow orchestration validates required artifacts by performing preflight checks that verify files like WorkflowContext.md and ImplementationPlan.md exist. This artifact readiness validation ensures safe, auditable transitions between activities before queuing the next task.

A gated workflow transition is an automated validation step that decides the next activity to enqueue by checking current state, session policies, and artifact readiness. You need it when orchestrating multi-stage activities requiring safe, auditable progression.

You queue the next task by triggering the transition TODO within a subagent session. The system uses the Mandatory Transitions table to determine the next activity, validates preflight conditions, and outputs a structured payload for the orchestrator.

Yes, you can perform Candidate Promotion checks for final PRs during transitions. The system executes these checks and reports unresolved candidates for human review, outputting the results in a structured transition payload for the orchestrator.

A structured transition result payload includes session_action, pause_at_milestone, preflight status, and next_activity details. This payload provides the orchestrator with all necessary data to execute the validated workflow progression.