Kaname Events
Events are formal opportunities to inspect the artifact chain and adapt. They are triggered by defined conditions, by regular cadence, or both.
Failure to hold events as defined results in specification drift, unreviewed architectural decisions, or accumulated delivery debt. An event that is optional is not an event - it is a suggestion.
At a Glance
Spec Review Session
Regular cadence
Queue Replenishment
When Spec-Ready queue is insufficient to sustain the next delivery cycle, or at regular cadence
Plan Review
After AI generates plan.md
Delivery Review
After Gate 4 passes - not calendar-driven
Flow Review
Regular cadence, when blocked items accumulate, or when lead time increases significantly
Constitution Review
Proposed amendment, architectural findings from a Delivery Review, or scheduled post-delivery inspection
Advance Use Cases in the specification toward Spec-Ready quality and maintain a sufficient queue ahead of Queue Replenishment. The Spec Owner receives structured feedback on in-progress Use Cases, resolves open questions, and agrees with stakeholders on what to specify next. Running at a regular cadence, it prevents the Spec Owner from becoming a bottleneck upstream of implementation.
Attendance
Constitution Guardian and at least one Task Implementer. When a delivery cycle is being prepared: Plan Reviewer and stakeholders also attend.
Output
Use Cases assessed. Next Use Cases to specify agreed. When serving as a pre-delivery review: selected Use Cases confirmed Spec-Ready or blocking items recorded.
Additional role
When a delivery cycle is about to begin, the Spec Review Session additionally serves as the formal review at which Use Cases selected for Queue Replenishment are confirmed complete and constitutionally aligned.
Select Spec-Ready Use Cases for the next delivery cycle and commit them toward the Specification Gate. Queue Replenishment does not include estimation, technical planning, or architectural discussion.
Attendance
Spec Owner and stakeholders provide priority input. Only Use Cases confirmed Spec-Ready through the Spec Review Session are eligible.
Output
Use Cases committed to the current delivery cycle.
Inspect the AI-generated technical plan for architectural soundness and alignment with the specification and constitution. The Plan Review concludes when the plan is approved or when required revisions are recorded.
Attendance
Spec Owner and Constitution Guardian.
Output
Plan approved or required revisions recorded.
Inspect the delivered system against its Use Cases and gather stakeholder feedback before the next delivery cycle begins. Each implemented Use Case is presented to stakeholders, who assess whether the delivered behavior matches their intent. Feedback that reveals gaps, new needs, or changed priorities is captured as input for the next Spec Review Session. The Delivery Review does not include technical planning or architectural discussion.
Attendance
Stakeholders, Task Implementers, and the Delivery Coach.
Output
All Use Cases reviewed. Stakeholder feedback recorded. Delivery cycle formally closed.
Inspect the system of work - not individual work items - to identify policy changes that would improve delivery flow. The full team inspects the board, lead time distribution, and blocked items. The output is a change to WIP limits, gate criteria, or work handling policies - not an action item for an individual.
Attendance
Full team.
Output
Policy change ratified, or explicit record that no change is warranted.
Inspect constitution.md for completeness and continued relevance, and to ratify proposed amendments. It concludes when the proposed change is ratified, revised, or rejected, and constitution.md is updated accordingly.
Attendance
Constitutional amendments require the explicit ratification of the Constitution Guardian.
Output
constitution.md updated. Amendment ratified, revised, or rejected.
Events keep the delivery system healthy between gate transitions.