P1-REQ-13-6-011

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 informationPersisted informationMoving informationExchanged informationRelease and movement concernsResidency 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 concernsData-in-motion references identify movement, exchange, publication, routing, or transfer concernsStorage location does not substitute for movement governanceMovement governance does not substitute for storage or residency governance

Traceability

Related source section:

Related requirement identifiers:

Status

Draft

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