phase-transitions

Forward-only phase transitions enforce orderly document progression by validating against allowed paths like draft to review to published. This prevents skipping stages and ensures context is preserved as documents advance through their lifecycle.

Blocked states in a document lifecycle workflow are handled by marking blockers, tracking their resolution, and resuming transitions once cleared. This explicit blocked-state transition support prevents stalled documents from blocking the entire project pipeline.

Phase transitions apply to ADRs, strategy documents, visions, initiatives, and tasks. A predefined phase map maintains consistent progression rules across all these document types, ensuring each follows its appropriate lifecycle path.

Exit criteria validation for document phase progression uses an exit_criteria_met flag to verify readiness before advancing. Documents cannot transition to the next phase until this flag confirms all required criteria have been satisfied.

Documents get stuck between lifecycle phases when exit criteria are not met or when blockers are unresolved. The phase progression system explicitly tracks these blocked states and validates exit_criteria_met flags before allowing forward transitions to proceed.

A predefined phase map is required to manage document lifecycle transitions consistently. It codifies allowed phase paths for each document type and provides the reference-driven guidance that ensures transitions follow established workflow rules.