doc-ref

Reference documents (BRD-REF and ADR-REF) are supplementary artifacts that provide project overviews, glossaries, technology stack summaries, and infrastructure details without participating in formal traceability chains. They clarify and augment primary BRD and ADR documents.

Create BRD-REF or ADR-REF documents following the REF naming convention, use mandatory templates and sections, maintain revision history, and place them under docs/{TYPE}. These documents stay outside formal traceability while providing essential reference material.

Use reference documents for strategic vision, technology stack overviews, infrastructure references, and quick-lookup glossaries that support but don't drive requirements traceability. They keep supplementary content organized without cluttering the formal documentation chain.

Reference documents must follow the REF naming convention (BRD-REF or ADR-REF), include mandatory templates and sections, maintain document control with revision history, and be stored in docs/{TYPE} directories to ensure consistent organization.

No. Reference documents are supplementary only and do not participate in traceability chains. Use them to clarify and contextualize primary BRD and ADR documents, not as replacements for formal requirement artifacts.