Plans¶
Implementation plans for phases or multi-session tickets. A plan breaks a chunk of work into ordered, verifiable steps.
When to write one¶
When work spans more than one session or has more than ~5 commits. Captures the order, the dependencies, and the verification step for each chunk so the next session can pick up cleanly.
Conventions¶
- Dated filenames:
2026-04-26-month1-prototype.md,2026-05-15-issue-21-llm-extraction.md - For ticket-specific plans, include the issue number in the filename
- Mark steps with
[ ]/[x]so progress is visible at a glance
Index¶
| Date | Title | Status |
|---|---|---|
| 2026-04-26 | Month 1 prototype | Done — shipped as v1.0.0-rebuild |
| 2026-04-28 | Issue #34: tech stack audit + forward research | Active |
| 2026-04-28 | Issue #32: category scope — M1/M2/M3 roster | Active |
| 2026-04-28 | Issue #44: security review + threat model | Active |
| 2026-04-28 | Issue #43: KPIs, observability, performance budget | Done |
| 2026-04-28 | Issue #47: AI discoverability (LLM-citable surface) | Active |
| 2026-04-28 | Issue #41: monetisation + pricing model | Active |