PRDs: Product

One PRD per feature increment. Each defines the problem, goals, and scope for that increment and links to the URD requirements it satisfies. Engineering tickets carry the how.

PRD	Date	Status	Title	Modules touched
—	—	—	No PRDs yet	CORE-05

No PRDs yet — add one with cp from another module's prds/ or follow §5 of the convention.

Authoring rules

• One PRD per file. Filename: YYYY-MM-DD-<kebab-slug>.md.
• Status values: Draft · In Review · Approved · Implemented · Superseded by <date-slug>.
• Status is updated in-place; never delete a PRD — supersede it.
• A PRD that refers to non-existent identifiers (services, tables, endpoints) must say so explicitly in its Requirements / Solution section.