Skip to main content

Technical Design Documents (TDD)

Per-feature design documents that go between the PRD (the what and why) and the implementation. Owned by the founder; agentic team consumes and produces TDD content under founder review.

What lives here​

A TDD is the right vehicle when:

  • The feature is meaningfully complex enough that the design is non-obvious from the PRD chapter alone.
  • An ADR-level decision is implied (a TDD that requires deviation from the PRD or an existing ADR triggers a new ADR — see docs/ADR/README.md).
  • Multiple bounded contexts coordinate (e.g. a flow that touches identity + accounts + audit).

Naming and structure​

  • Filename: NN-kebab-case-title.md for top-level TDDs, or place under docs/TDD/<domain>/NN-…md when scoped to one bounded context.
  • Header fields (frontmatter or ## Owner / ## Status headings) are required and validated by scripts/check-doc-frontmatter.ts.
  • Status values: Draft | In Review | Accepted | Implemented.
  • Template: docs/standards/tdd-template.md.

Status​

This directory is empty during the Phase-0 substrate bootstrap. The first TDDs land alongside the first apps/* (Phase 1a — the monorepo skeleton + identity bounded context).

See also​