Reference
Document types
The quick lookup. For the narrative version read The chain; for the full shipped specification read the document model projection.
One line per type. The narrative walk of the same material is The chain; the shipped per-type specification your agent authors against is published verbatim at the document model.
| Type | Name | Is |
|---|---|---|
| PRD | Product Requirements Document | The root statement of product intent: the problem, who has it, what changes when it is solved, what is out of scope. One per project. |
| REQ | Requirement | One testable capability the product must have, with category, priority and rationale. References its PRD. |
| US | User story | One story under a requirement: as-a / I-want / so-that, carrying its acceptance criteria. References its REQ. |
| AC | Acceptance criterion | An observable, testable statement of done in given / when / then form, carried inline in its user story. The currency of the whole framework. |
| TAD | Technical Architecture Document | The architecture root: a shell for cross-cutting sections, with TACs and ADRs as children. One per project. |
| TAC | Technical architecture component | A lasting component of the system: purpose, responsibilities, interfaces, dependencies. References the TAD. |
| ADR | Architecture decision record | One consequential decision: context, decision, consequences, and the alternatives with reasons. References the TAD. |
| BS | Build Sequence | The planning root: how work is ordered and under what strategy. One per project. |
| FBS | Functional Build Specification | One work item: a coherent slice of delivery scoped to a set of AC ids, with build order, dependencies, sizing and execution status. |
| TS | Test Suite | What test cases exist for one or more acceptance criteria on a single user story, at a named test level. Hangs off the user story. |
| TC | Test Case | One test: the AC it verifies, the pointer to the executable test, and its status. Carried inline in its test suite. |
| CN | Code Node | The spec-to-code bridge: a source path, optionally symbol-suffixed, implementing one or more acceptance criteria. No parent; its identity is its path. |
| MANIFEST | Manifest | rcf/manifest.json: declares the three root documents (PRD, TAD, BS) from which every other document is discovered. |
Two structural rules worth carrying into any reading of the tree: every reference points upward from child to parent, and parents never list their children (the downward view is computed). Field-level detail, required fields, enums, id patterns and the file layout, ships with the @stravica-ai/rcf-schemas package, one page per type in its docs/ directory.