====== P1-REQ-13-3-002 ======

[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]

===== Statement =====

The Conceptual Architecture SHALL use [[dido:99_annexes:annex-b-terms-and-definitions:c:classification_path|Classification Paths]] to identify governed business and [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|Semantic]] scope.

===== Source =====

Part 1, Section 13.3: Classification Requirements.

===== Rationale =====

Classification Paths identify the governed scope represented by a classification. They provide a stable way to express business and semantic scope without relying on runtime, deployment, repository, or implementation identifiers.

Using Classification Paths supports consistent interpretation across documents, profiles, systems, and governed communities.

===== Applies To =====

This requirement applies to the use of Classification Paths within the Conceptual Architecture.

It applies specifically to:

  * Governed business scope
  * Semantic scope
  * Classification references
  * Profile inheritance
  * Cross-document traceability

===== Verification =====

Verification SHALL confirm that the Conceptual Architecture uses Classification Paths to identify governed business and semantic scope.

Verification activities include review checks confirming that:

  * Classification Paths identify governed business scope
  * Classification Paths identify semantic scope
  * Classification Paths do not substitute for runtime identifiers
  * Classification Paths support traceability across later profiles

===== Traceability =====

Related source section:

  * [[fxdemo:01-part:13-conceptual-requirements:13-3-classification-requirements]]

Related requirement identifiers:

  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-001:start]]
  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-003:start]]
  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-3-004:start]]

===== Status =====

Draft