Kaname Delivery
Kaname is not sprint-based. Work flows continuously through defined stages governed by explicit policies. A delivery cycle begins when Use Cases are committed and ends when the Delivery Gate passes. What happens between those two points is the delivery cycle.
The Board
Backlog
Gate 1
Specify
Spec Owner
spec.md
Gate 2
Plan
Plan Reviewer
plan.md
Gate 3
Implement
Task Implementer
tasks.md
Review
Spec Owner
Gate 4
Done
Delivery Coach
Vertical lines are human gates - work cannot cross them without named human approval.
Stage by Stage
Use Cases exist but are not yet Spec-Ready. The Spec Owner is aware of them and may be authoring them, but they have not yet entered the active specification pipeline.
Entry
A stakeholder intent or product need has been identified.
Exit
Use Case is submitted for Spec Review Session assessment.
Specification Gate
Spec Owner + Constitution Guardian verify: Each Use Case is complete, constitutionally aligned, and implementable without clarification.
spec.mdThe Spec Owner writes and refines Use Cases until they meet the Spec-Ready standard: every input, output, variant, and failure condition is defined. The Spec Review Session runs at cadence here.
Entry
Spec Owner pulls the Use Case into active specification.
Exit
Use Case satisfies Behavioral Intent commitment - a Task Implementer can execute it using an AI agent without requesting clarification. The Use Case is Spec-Ready.
Plan Gate
Plan Reviewer verify: AI-generated plan.md is architecturally sound, constitutionally compliant, and covers all Use Cases in scope.
plan.mdAn AI agent generates plan.md from the approved specification: component structure, data model, API contracts, and implementation sequence. The Plan Reviewer inspects - they do not author.
Entry
Gate 1 cleared. Spec-Ready Use Cases committed to the delivery cycle.
Exit
Plan satisfies Architecture Alignment commitment - every Use Case maps to a technical component, no constitutional violations.
Implementation Gate
Task Implementer verify: AI-generated code satisfies the linked Use Case acceptance criteria. Applied per task, not per delivery cycle.
tasks.mdTask Implementers pull tasks from tasks.md according to WIP limits and execute them with AI coding assistants. Each task carries its Use Case reference and acceptance criteria. Ambiguity returns to the Spec Owner - it is never resolved unilaterally.
Entry
Gate 2 cleared. Task pulled from board as capacity allows.
Exit
AI output reviewed against Use Case acceptance criteria. Task satisfies Implementation Completeness commitment.
The Spec Owner performs end-to-end verification of all implemented Use Cases in the delivery cycle. This is not a code review - it is behavioral verification: does the delivered system do what the spec said it would?
Entry
All tasks in the delivery cycle have passed Gate 3.
Exit
All Use Cases verified end-to-end. Gate 4 is ready to be exercised.
Delivery Gate
Spec Owner verify: All Use Cases in the delivery cycle are satisfied. Release is authorized. Triggers the Delivery Review event.
Gate 4 has passed. The Delivery Review event is triggered - stakeholders inspect the delivered system and provide feedback. Their input enters the next Spec Review Session. The delivery cycle formally closes.
Entry
Gate 4 cleared by Spec Owner.
Exit
Delivery Review concluded. Feedback captured. Cycle closed.
The Artifact Chain
constitution.md governs spec.md governs plan.md governs tasks.md. Each artifact carries a binding commitment evaluated at its gate.
Six Events
Formal opportunities to inspect the artifact chain and adapt. Triggered by defined conditions, cadence, or both.
The four human gates are defined in detail in the Gates section.