dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-012:start

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-5-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-5-012:start [2026/07/11 12:57] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== P1-REQ-13-5-012 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
 +
 +===== Statement =====
 +
 +The [[dido:99_annexes:annex-b-terms-and-definitions:p:policy_and_release_plane|Policy and Release Plane]] SHALL support data sovereignty and data residency as conceptual release and movement concerns.
 +
 +===== Source =====
 +
 +Part 1, Section 13.5: Runtime Plane Requirements.
 +
 +===== Rationale =====
 +
 +Data sovereignty and data residency affect how information moves, where information resides, which authority governs release, and which obligations apply. Treating these concerns conceptually allows later logical and implementation profiles to support governed release and movement without redefining the conceptual architecture.
 +
 +This requirement separates sovereignty and residency concerns from specific networks, storage systems, jurisdictions, or deployment environments.
 +
 +===== Applies To =====
 +
 +This requirement applies to Policy and Release Plane definitions and references within the Conceptual Architecture.
 +
 +It applies specifically to:
 +
 +  * Data sovereignty
 +  * Data residency
 +  * Release concerns
 +  * Movement concerns
 +  * Governed information handling
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that the Policy and Release Plane supports data sovereignty and data residency as conceptual release and movement concerns.
 +
 +Verification activities include review checks confirming that:
 +
 +  * Data sovereignty appears as a conceptual release and movement concern
 +  * Data residency appears as a conceptual release and movement concern
 +  * Sovereignty and residency concerns remain distinct from deployment environments
 +  * Later profiles map sovereignty and residency concerns without redefining them
 +
 +===== Traceability =====
 +
 +Related source section:
 +
 +  * [[fxdemo:01-part:13-conceptual-requirements:13-5-runtime-plane-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-013:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-015:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>