13.6 Separation of Concerns Requirements

Go to Conceptual Requirements

This section identifies the normative requirements for separation of concerns established by Part 1. The canonical requirement statements are maintained in Annex C: Requirements, Part 1.

Table 13.6-1: Part 1 separation of concerns requirements.

Requirement ID	Statement
P1-REQ-13-6-001	The Conceptual Architecture SHALL distinguish Data, Structure, Semantics, Interpretation, Governance and Authority, Traceability, and Evidence as structured-information processing concerns.
P1-REQ-13-6-002	The Conceptual Architecture SHALL distinguish Data from Structure.
P1-REQ-13-6-003	The Conceptual Architecture SHALL distinguish Structure from Semantics.
P1-REQ-13-6-004	The Conceptual Architecture SHALL distinguish Semantics from Interpretation.
P1-REQ-13-6-005	The Conceptual Architecture SHALL distinguish Governance and Authority from the technical mechanisms that support governance.
P1-REQ-13-6-006	The Conceptual Architecture SHALL distinguish Traceability from Evidence.
P1-REQ-13-6-007	Cross-concern relationships SHALL preserve the distinction between the concerns involved.
P1-REQ-13-6-008	Cross-concern relationships SHALL be Traceable when they affect meaning, Interpretation, governance, authority, auditability, or Evidence.
P1-REQ-13-6-009	The Conceptual Architecture SHALL distinguish full transaction detail from transaction metadata and aggregate information products.
P1-REQ-13-6-010	The Conceptual Architecture SHALL distinguish data sovereignty from data residency.
P1-REQ-13-6-011	The Conceptual Architecture SHALL distinguish between data-at-rest and data-in-motion concerns.
P1-REQ-13-6-012	Cross-concern relationships involving policy-governed release SHALL preserve the distinction between governance, authority, Traceability, Evidence, Data, and Interpretation.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.