artifact-channel

Per-cycle artifact coordination isolates writes to a single cycle directory on a dedicated git branch, preventing cross-role drift when multiple roles contribute to a release. You need it when sequential handoffs between roles risk overwriting or desyncing immutable merged artifacts.

Enforce strict sequential role handoffs by gating pre-dispatch writes and freezing predecessor artifacts post-merge. Roles must follow the α→β→γ flow, writing only to their canonical artifacts within the unreleased cycle directory until release-time migration.

Move unreleased cycle artifacts by migrating the single cycle directory from .cdd/unreleased/{N}/ to .cdd/releases/{X.Y.Z}/{N}/ at release time. This freezes the cycle directory and creates a canonical, auditable trail for post-release reconstruction.

Yes, cycle coordination requires a dedicated branch structure using origin/cycle/{N} for active development. A gamma-scaffold.md must exist on this branch before sequential α, β, and γ artifact writes begin in the unreleased cycle directory.

Prevent cross-role drift by enforcing per-role artifact ownership within a git-backed channel, ensuring each role writes exclusively to its own canonical artifact while predecessors' artifacts remain immutable after merge and before release freeze.

After a release snapshot is created, the cycle directory undergoes a post-merge freeze until release. The directory is then migrated to the releases path, establishing a frozen, auditable trail for post-release reconstruction and preventing further artifact modifications.