Convention Index

This document is the central entry point for the implementation-playbook style conventions in the Context-Action repository. The docs have grown enough that it helps to group which documents define the rules, which ones demonstrate the pattern, and which ones lock the verification model.

Short Recommended Reading Path

1. Implementation Convention
2. Canonical Order Form Example
3. Playbook Scenario Library
4. Explicit State Machine
5. Stability Test Cycle

These five cover:

• folder structure
• workflow transition rules
• domain-level expansion
• testing expectations

Grouped by Role

1. Documents that define the standard

• Implementation Convention
  • the standard implementation-playbook rule set
• Folder Structure
  • responsibility split across contexts / business / handlers / actions / hooks / views
• Handler Registry
  • handler registration and separation rules

2. Documents that explain logic and transitions

• Explicit State Machine
  • how to lock complex async flows as state + event + transition
• Context-Layered Overview
  • the high-level architectural picture
• Migration Guide
  • how to move older structures into this model

3. Documents that demonstrate the implementation

• Canonical Order Form Example
  • the base canonical example
• Access Request Playbook Example
  • approval/review workflow example
• Incident Escalation Playbook Example
  • incident/escalation workflow example
• Renewal Risk Review Playbook Example
  • renewal/customer-success workflow example
• Playbook Scenario Library
  • scenario extensions that follow the same skill and convention

4. Documents that define verification

• Stability Test Cycle
  • how to split contract tests, scenario tests, and stress validation

Reading Paths by Goal

For architecture alignment

1. Implementation Convention
2. Explicit State Machine
3. Stability Test Cycle

For implementer onboarding

1. Canonical Order Form Example
2. Access Request Playbook Example
3. Incident Escalation Playbook Example
4. Renewal Risk Review Playbook Example

For designing new scenarios

1. Playbook Scenario Library
2. Implementation Convention
3. repo-local skill: skills/context-action-implementation-playbook/SKILL.md

Read Alongside the Example App

The docs make more sense when paired with the live demos:

• /patterns/implementation-playbook
• /patterns/implementation-playbook/access-request
• /patterns/implementation-playbook/incident-escalation
• /patterns/implementation-playbook/renewal-risk-review

One-Line Summary

To turn this into a team convention, follow: Implementation Convention -> Explicit State Machine -> Canonical Example -> Scenario Demos -> Stability Test Cycle