dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-011: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-6-011: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-011:start [2026/07/11 12:57] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== P1-REQ-13-6-011 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
 +
 +===== Statement =====
 +
 +The Conceptual Architecture SHALL distinguish between data-at-rest and data-in-motion concerns.
 +
 +===== Source =====
 +
 +Part 1, Section 13.6: Separation of Concerns Requirements.
 +
 +===== Rationale =====
 +
 +Data-at-rest concerns information that resides in storage, repositories, persistence, archives, or holding contexts. Data-in-motion concerns address information that moves, flows, transfers, publishes, subscribes, routes, or exchanges between participants or contexts.
 +
 +This requirement prevents storage and movement concerns from being treated as the same architectural concern, especially where sovereignty, residency, policy release, auditability, or evidence depends on the distinction.
 +
 +===== Applies To =====
 +
 +This requirement applies to data at rest and data in motion within the Conceptual Architecture.
 +
 +It applies specifically to:
 +
 +  * Stored information
 +  * Persisted information
 +  * Moving information
 +  * Exchanged information
 +  * Release and movement concerns
 +  * Residency and sovereignty concerns
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that the Conceptual Architecture distinguishes data-at-rest concerns from data-in-motion concerns.
 +
 +Verification activities include review checks confirming that:
 +
 +  * Data-at-rest references identify residence, storage, persistence, or holding concerns
 +  * Data-in-motion references identify movement, exchange, publication, routing, or transfer concerns
 +  * Storage location does not substitute for movement governance
 +  * Movement governance does not substitute for storage or residency governance
 +
 +===== 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-012:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-010:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-012:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>