📖What it means

Statements of what the project must have and must do. Requirements are auto-derived from the live state of the project — never written by hand and never stored in a standalone the requirements records three live sources are: (1) the registry shared machinery tables (structural), (2) prompt *.md files (behavioral), (3) tools.json files (capability). Plus a technical-requirements markdown file for infrastructure and quality. The SST's Requirements category points to the project's own Requirements app as the authoritative view.

📖Easily confused with

[{"term": "Design", "distinction": "A requirement says WHAT must be true; a design says HOW it is built."}, {"term": "Success criterion", "distinction": "A requirement is standing and derived from the live estate; a success criterion is written for one initiative and graded at its close."}]

📖Also called

- requirement

📖Filed under

Category: records.

Service: Governance.