Overview

🚀Validate Workflow Transitions

Experimental / currently blocked

Supply branch and version boundaries for Custy's experimental workflow-policy engine.

Commandcusty workflow branch

📦Category

Experimental Workflow

🚀Quick Command

custy workflow branch [OPTIONS]

---

branch policyversion transitionbeta

---

🔄

Category

Experimental Workflow

❌

Readiness

Currently Blocked

⚠️

Known Issue

finalize name mismatch

🛡️

CI/CD Use

Not Recommended

Overview

The intended command can validate a transition without enforcement or apply configured policy enforcement using explicit branch and tag boundaries.

🛡️Known pipeline-construction issue

In the current source, this command requests finalize; the registered step is finalize_step. Execution may stop before transition behavior begins. The pages in this section document the accepted interface and intended workflow, not a production-readiness guarantee.

---

Intended Responsibilities

✨Experimental Transition Interface

🌿Resolve Boundaries

Accept explicit source and target branch or version boundaries.

🛡️Validate Policy

Evaluate configured transition rules without enforcement when requested.

⚠️Enforce Policy

Apply configured transition behavior only after the implementation is corrected and validated.

📦Synchronize Backup

Request eligible workflow-related backup synchronization.

---

Related Commands

🚀Related Commands

Commands commonly used together with this command.

custy validate

Use stable repository validation while workflow policy remains experimental.

custy run release

Use the standard release profile without experimental finalization.

custy run full

Review the separate registered finalize_step path.