Plans
Architecture references and audit documents. Actionable implementation work lives in docs/projects/.
Reference Documents
| Plan | Description | Status |
|---|---|---|
| V2 Fact Engine | Master v2 fact engine architecture and implementation reference | Draft |
| Fact Engine API Gaps | Cross-cutting audit — spawned 4 projects below | Draft |
Moved to Projects
The following plans were converted to project folders in docs/projects/:
| Former Plan | Project Folder |
|---|---|
| Marketing Site (design + plan) | marketing-site |
| V1 Table Cleanup Phase 8 (design + plan) | v1-table-cleanup |
| CSV Config Pipeline (design + plan) | csv-config-pipeline |
| Railway Migration | railway-migration |
| Evidence Enrichment (6 API plans) | evidence-enrichment |
| API Gaps (Gaps 1+2+6) | api-gaps |
| API Gaps → Challenge Conversations (Gap 4) | challenge-conversations |
| API Gaps → Route Cleanup (Gap 5) | route-cleanup |
V1 Plans (Archived)
All v1 plans (MVP plan, cost optimization, Playwright integration, etc.) have been archived to docs/docs_archive/plans-v1/.
Plan Governance
Plans follow versioning rules defined in Plan Governance:
- Never modify locked plans in place
- Create new versions with
parentreferences - Use status:
draft,active,locked, orarchived