# `docs/research/` — historical reviews, audits & explorations

These documents are **point-in-time records**, not current reference material.
They capture investigations, audits, and design explorations from a specific
moment in the project's history (each carries its own date / status banner).
They are kept for context — "why did we decide X?", "what did we rule out?" —
but they are **not maintained** and may describe code, commands, or plans that
have since changed.

**For current information, do not rely on these files. Instead read:**

- [`docs/plan.md`](../plan.md) — current status + the executed iteration history
- [`docs/solution-design.md`](../solution-design.md) — current architecture
- [`docs/requirements-and-specs.md`](../requirements-and-specs.md) — current requirements
- [`CLAUDE.md`](../../CLAUDE.md) — current conventions + structure
- the guides in [`docs/guides/`](../guides/) — current user-facing how-tos

**Exception:** [`vision.md`](vision.md) is *not* historical — it is the living
statement of the project's vision and direction, cited as authoritative from
the root README and `CLAUDE.md`. Keep it current.

Everything else here (audits, integration notes, the manual test plan, the
SPA / semantic-graph explorations, etc.) should be read as "this was true / was
the thinking on its date," cross-checked against the current docs and code
before acting on it.
