Required Entity Set

Appendix A

Required Entity Set

The Entity and Multiplicity columns are normative: §14.8 requires every Entity below, at the multiplicity stated, and §16.2 checks that each is bound in the Path Map. The Clause column is a non-normative index to the clauses that impose each Entity. The binding of each Entity to a concrete location and serialization format is declared by the Project's Path Map (§14.8).

EntityMultiplicityClause
Vision Documentone§3
Governing Principlesone§14.1
Entry Pointone§14.3
Registryone§14.7
Component Specificationone per Component§6.1
Top-level System Specificationone§6.17
Interface declarationsone per interface; those internal to a Component Specification are bound with it, those spanning Components are separately bound§6.10
Decision Recordsone per binding decision§11
Records of Exploratory Work Unitsone per Exploratory Work Unit; none where no Exploratory Work Unit is run§5.7, §6.13
Work Recordone§4.5
Plan Documentsone per Work Unit§4.6, §5.9
Phase artifactsat least one per Phase§8.1
Design and planning documentsone per effort spanning more than one Work Unit; none where no such effort exists§6.19
Verification Planone§7.9
Verification Artifacts (Gate records, drift reports, quality record chain, Verification Reference State records, etc.)one per verification event; element-local Verification Procedures live on the governed artifact§7, §8.4, §14.6
Baseline Ledgerone§9.1
Risk Registerone§12.1
Status Ledgerone§9.3
Deviation Matrixone§9.4
Key Design Parameter registerone§6.18
Criticality Recordone§7.10
Executor scope declarationsone per Executor§13.1
Reusable task definitionsone per recurring kind of work§5.10
Realization and its local documentationone Realization; internal layout declared in the Path Map§14.8