The product workflow, three rules

prd-intake · provenance and hard rules
Provenance — every statement carries one tag
TagMeaning
[PRD]Stated in the PRD — quote or section ref attached
[PRD-CLARIFIED]Was a gap; answered by a person — name + date in the gap register
[INFERRED]Derived from PRD content — the reasoning is shown inline
[CONVENTION]Not in the PRD; a documented DS/repo convention applies — proposed as a default, needs confirmation
[GAP → Q#]Not in the PRD, no convention covers it — a numbered question
Three hard rules
  1. Pattern knowledge generates questions, not content. Knowing list pages need a default sort never means inventing one — it means raising a [GAP]. No invented fields, statuses, roles, flows, or copy. Ever.
  2. PRD terminology is verbatim throughout the brief and all questions.
  3. Two-way fidelity. Anti-hallucination is “nothing added”; the brief also proves “nothing lost”: every requirement-bearing sentence in the PRD lands somewhere — extracted, listed under Out of scope, or explicitly set aside with a reason.