Use this page as the entry point for project documentation. Documents are grouped by purpose so active guidance is easy to distinguish from research and historical records.
adr/— binding architecture decisions and their history.architecture/module-map.md— current module ownership, contracts, dependencies, and validation.architecture/work-packet-template.md— scope template for contributor and agent work.architecture/interface-change-checklist.md— safety checklist for cross-boundary or externally observable contracts.architecture/domain-collaboration-plan.md— implemented collaboration-boundary plan.architecture/collaboration-pilot-assessment.md— evidence and limitations from the initial boundary pilots.architecture/frontend-assessment.md— 2026-08-30 review of the frontend stack, size, the block editor of the time (replaced by the live editor on 2026-10-09), and the three oversized components with their split seams.
roadmap/product-roadmap.md— overall product direction and workstreams.roadmap/vault-lifecycle.md— detailed vault lifecycle and multi-vault workstream.
design/design-system.html— frontend visual tokens, component patterns, layouts, and interaction states.
maintenance/dependency-update-plan.md— completed dependency-update plan and retained upgrade context.maintenance/release-runbook.md— cutting a release withjust release-prepareandjust release-publish.
research/embeddings/— embedding-model, licensing, evaluation, and FastEmbed feasibility records.
Research records inform decisions but are not binding architecture policy.
Accepted decisions belong in adr/.
reviews/— point-in-time pull-request and implementation reviews.superpowers/— task-specific design, handoff, and implementation records retained for context.