business-requirements/

Purpose

The business/product layer: what the product must do and why. The features, the gaps, and the scope — not the technology (that's architecture/), not the schema (that's database/ and modules/), not AI governance (that's ai/).

What belongs here

• Feature requirements (what each module must do) and how they are sourced.
• The gaps registry (nursery pain points found in research, expressed as buildable scope).
• Market research and explicit scope (in / out).

What does NOT belong here

• Tech stack / technology choices → architecture/.
• Schema / tables → database/ and modules/.
• AI authority/OFF-behavior/governance → ai/ (applied via the runbook's Part B).

Source of truth

Live status/counts → DOCS_INDEX.md.