📖What it means

A detailed technical artifact describing how something in the project should be built: architecture, workflow, UI, data model, API, policy mapping. Stored as a row in the design records -> designs table. Every design has title, description, type, department, status (draft/review/approved/retired), version, and content markdown. Designs are the 'how' layer between policies (rules) and code (what exists).

📖Easily confused with

[{"term": "Requirement", "distinction": "A design is the HOW; a requirement is the WHAT."}, {"term": "Cookbook entry", "distinction": "A design describes a built thing; a cookbook entry prescribes an action to take."}]

📖Also called

- design record
- architecture doc

📖Filed under

Category: records.

Service: Governance.