Spec manifest

The numbered specs under spec/ in the repository are the canonical, implementation-shaped source of truth for the system's design. The Architecture section of this site is the narrative summary; when the two disagree, the spec wins.

Spec	Purpose
00_overview.md	Vision, goals, non-goals, glossary, system diagram
01_data_model.md	Entities, ERD, indexes, invariants
02_api_design.md	REST surface, errors, pagination, idempotency, ETags
03_mcp_integration.md	FastMCP design, tool catalog, MCP resources
04_auth_and_identity.md	Sessions, bot tokens, middleware, CSRF, settings
05_wiki_and_notes.md	Wiki rendering, wikilinks, backlinks, sticky notes
06_frontend.md	Next.js routes, components, state, board UX
07_observability.md	Audit, activity, webhooks, metrics, health
08_repo_structure.md	Repo layout, dependency rules, naming, tooling
09_testing_strategy.md	Test pyramid, fixtures, CI gates, E2E journeys
10_sprint_plan.md	Phase 1–6 implementation streams, agent delegation, progress tracker
11_sprint_plan_ux_iteration.md	UX iteration sprint: board-first navigation, dashboard overhaul

Reading order

For a human or AI contributor coming in cold:

1. 00_overview.md — the vision and the system diagram.
2. 01_data_model.md — the entities everything else hangs off.
3. 08_repo_structure.md — where code lives and the dependency rules.
4. The remaining numbered specs (02–07, 09) in order.
5. The sprint plans (10, 11) — the build history, kept as a record of how the phases were planned and delegated.

The ADRs complement the specs: a spec describes what the design is; an ADR records why a contested decision went the way it did.