P1-REQ-13-6-011

Return to Part 1 Requirements

The Conceptual Architecture SHALL distinguish between data-at-rest and data-in-motion concerns.

Part 1, Section 13.6: Separation of Concerns Requirements.

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.

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 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

Related source section:

• 13.6 Separation of Concerns Requirements

Related requirement identifiers:

• P1-REQ-13-5-012
• P1-REQ-13-6-010
• P1-REQ-13-6-012

Draft