artifact-channel

What problem does it solve?

The Artifact Channel provides a disciplined, per-cycle write substrate that prevents cross-role drift by ensuring each role writes to its own canonical artifact within the cycle directory, while predecessors' artifacts remain immutable after merge. It uses a git-backed channel at .cdd/unreleased/{N}/ on origin/cycle/{N}, with the release-time move to .cdd/releases/{X.Y.Z}/{N}/.

Core Features & Use Cases

• Enforces per-role artifact ownership (γ, α, β) and a strict α→β→γ sequential flow.
• Supports cycle-scoped records from γ scaffold to γ close-out, including mid-flight rescue artifacts, and the final release snapshot.
• Provides a canonical, auditable trail for post-release reconstruction by freezing the cycle directory and migrating it at release time.

Quick Start

Ensure a gamma-scaffold.md exists on origin/cycle/{N} and then follow the sequential writes to .cdd/unreleased/{N}/ for α, β, and γ, ending with a single release move to .cdd/releases/{X.Y.Z}/{N}/.