technical-requirement
The technical-requirement label classifies a document as prescriptive: it states something that must hold, must be done, or must be conformed to. Downstream systems, reviewers, and processes can rely on it as a binding source of truth within the organisation's scope.
When to apply
- Requirement specifications (functional, performance, safety, security).
- Interface contracts between systems or teams.
- Governance rules the organisation chooses to enforce.
- Standards adopted from external bodies and normatively applied internally.
When not to apply
- An explanatory companion ("how we satisfy requirement X") — use documentation instead.
- A draft that has not yet been through review — use Tags (
draft,in-review) to express workflow state; the Label describes the document's intent, not its approval status.
Why the distinction matters for Index queries
Many organisational workflows filter on "all active technical requirements referenced by this workspace". Keeping the nature of the content (this Label) orthogonal from its state (Tags) lets those queries stay stable across state transitions.