Canonical Use Cases
Purpose: Design-phase use cases identified during architecture and design planning
Location: docs/architecture/use-cases/
Type: Canonical (planned, designed before implementation)
Overview
Canonical use cases are design-phase use cases that are:
- Planned and intentional
- Part of original design/architecture
- Documented before implementation
- Stable and well-defined
- Part of framework/product design
These use cases inform system architecture, requirements engineering, and design decisions.
Quick Navigation
- Canonical Use Cases - Design-phase use cases
- Template - Template for creating canonical use cases
- Methodology - Complete use case methodology guide
Use Case Types
Canonical Use Cases (This Directory)
Location: canonical/
Definition: Use cases identified and documented during the design/planning phase, before implementation.
Characteristics:
- Planned and intentional
- Part of original design/architecture
- Documented before implementation
- Stable and well-defined
- Inform architecture and design decisions
Examples:
- Framework adoption patterns
- Workflow execution patterns
- Versioning patterns
- Kanban organization patterns
Related Documentation
- Discovered Use Cases - Implementation-phase discovered use cases (in knowledge base)
- Use Case Methodology - Complete methodology guide
- Architecture Standards (versioning policy) - Architecture decision records and standards
Creating Canonical Use Cases
- Use
CANONICAL_USE_CASE_TEMPLATE.md - Create in
Canonical/directory - Follow naming convention:
UC-XXX-[title].md(UC implies canonical) - Update
Canonical/README.mdindex - Link to related architecture documents and design decisions
This section is part of Architecture documentation. Canonical use cases inform system design and architecture decisions.