# Documentation Map

All project documentation should live under `docs/`.

## Folder Guide

- `docs/phase-1/`: phase-specific planning and delivery documents.
- `docs/phase-1/features/`: feature-level specs and requirements for phase 1 work.
- `docs/phase-1/tasks/`: task trackers, execution logs, and delivery records for phase 1.
- `docs/phase-2/`: Developer onboarding, running the multi-agent stack, and operational guides.
- `docs/phase-2/current-sprint.md`: live sprint context the agent should read first, including the active sprint, your tickets, blockers, and immediate priorities.
- `docs/phase-2/llds/`: Phase 2 technical specifications, Low-Level Designs (LLDs), and protocol definitions.
- `docs/reports/`: dated reports and reporting outputs.
- `docs/reports/jira/`: Jira-specific dated reports.
- `docs/strategy/`: strategy, research, workshop, and experiential-design artifacts.
- `docs/dump/`: raw dumps, temporary source captures, and material that has not yet been curated.

## Placement Rules

- Create new documentation inside the closest existing subtree before adding a new folder.
- Use **kebab-case** for file and folder names (e.g., `multi-agent-architecture.md`).
- Avoid redundant names based on the parent folder (e.g., in `phase-2/`, use `setup-guide.md` instead of `phase-2-setup-guide.md`).
- Keep live working context out of `docs/reports/`; current sprint state belongs in `docs/phase-2/current-sprint.md`.
- Use dated filenames for recurring reports and logs in `docs/reports/`.
- Keep scratch material in `docs/dump/` until it is promoted into a curated folder.