# REASONS Canvas — <Mission Title>

> Mission: <mission-slug>
> Generated: <YYYY-MM-DD>
> Charter activation: structured-prompt-driven-development (paradigm)

## Requirements
- Problem statement: <one sentence>
- Acceptance criteria: <bulleted list>
- Definition of done: <bulleted list>

## Entities
- Domain concepts and relationships: <list>
- Glossary terms (canonical): <list with definitions>

## Approach
- Selected strategy: <summary>
- Tradeoffs considered: <list>

## Structure
- Code surfaces affected: <files / packages>
- Components and dependencies: <list>
- Ownership boundaries: <list>

## Operations
- Ordered implementation steps: <list>
- Test strategy: <list>

## Norms
- Coding/style conventions: <list>
- Observability, testing, and team rules: <list>

## Safeguards
- Hard constraints and invariants: <list>
- Security rules: <list>
- Performance limits: <list>
- Things not to break: <list>

## Deviations (append-only)
- <date> — <wp> — <description> — <rationale>
