Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-012:start [2026/07/11 12:57] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-012:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== P1-REQ-13-6-012 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
 +
 +===== Statement =====
 +
 +Cross-concern relationships involving policy-governed release SHALL preserve the distinction between governance, authority, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]], [[dido:99_annexes:annex-b-terms-and-definitions:d:data|Data]], and [[dido:99_annexes:annex-b-terms-and-definitions:i:interpretation|Interpretation]].
 +
 +===== Source =====
 +
 +Part 1, Section 13.6: Separation of Concerns Requirements.
 +
 +===== Rationale =====
 +
 +Policy-governed release involves governance, authority, traceability, evidence, data, and interpretation. These concerns interact when information is evaluated, authorized, transformed, released, withheld, audited, or reconstructed. Each concern retains a distinct architectural purpose.
 +
 +This requirement prevents release governance from collapsing authority, data, interpretation, traceability, and evidence into a single release decision or implementation mechanism.
 +
 +===== Applies To =====
 +
 +This requirement applies to cross-concern relationships involving policy-governed release within the Conceptual Architecture.
 +
 +It applies specifically to:
 +
 +  * Governance
 +  * Authority
 +  * Traceability
 +  * Evidence
 +  * Data
 +  * Interpretation
 +  * Policy-governed release
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that cross-concern relationships involving policy-governed release preserve the distinction between governance, authority, Traceability, Evidence, Data, and Interpretation.
 +
 +Verification activities include review checks confirming that:
 +
 +  * Policy-governed release identifies the governance concern involved
 +  * Policy-governed release identifies the authority concern involved
 +  * Policy-governed release preserves Traceability and Evidence as distinct concerns
 +  * Policy-governed release preserves Data and Interpretation as distinct concerns
 +  * Release mechanisms do not redefine the concerns involved
 +
 +===== Traceability =====
 +
 +Related source section:
 +
 +  * [[fxdemo:01-part:13-conceptual-requirements:13-6-separation-of-concerns-requirements]]
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-005:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-011:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-012:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-013:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-001:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-007:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-008:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>