Project Artifacts

Project artifacts live under .oat/projects/<scope>/<project>/.

Core artifacts

state.md: lifecycle state and checkpoint metadata
discovery.md: problem framing, constraints, solution space exploration (for exploratory requests), and discovery outcomes
spec.md: requirements + acceptance criteria
design.md: architecture and implementation approach (full in spec-driven mode; optional lightweight version in quick mode covering architecture, components, and testing strategy)
plan.md: phase/task breakdown and review tracking
implementation.md: execution log, verification, final summary
summary.md: institutional memory artifact — generated from project artifacts at closeout, used as PR description source and archive cover page

Mode-sensitive notes:

state.md includes workflow mode metadata (spec-driven, quick, import) for routing.
spec.md and design.md are required in spec-driven mode, optional in quick/import mode. Quick mode offers a lightweight design.md (architecture, components, testing strategy) at a post-discovery decision point.
plan.md remains canonical execution artifact across all modes.

summary.md: generated by oat-project-summary — re-runnable, tracks its own state via frontmatter for incremental updates after revisions
reviews/*.md: phase/final review files
pr/*.md: generated PR descriptions
references/imported-plan.md: preserved source plan for import mode

Artifacts are the project system of record; automation and routing should derive from these files, not memory.