P1-REQ-13-6-009

Return to Part 1 Requirements

Statement

The Conceptual Architecture SHALL distinguish full transaction detail from transaction metadata and aggregate information products.

Source

Part 1, Section 13.6: Separation of Concerns Requirements.

Rationale

Full transaction details, transaction metadata, and aggregate information products represent different information forms with varying sensitivities, governance, release, interpretation, and evidentiary implications. Treating them as equivalent creates unmanaged release and interpretation risk.

This requirement supports governed information handling by preserving the distinction among detailed, metadata, and aggregate forms.

Applies To

This requirement applies to information-form distinctions within the Conceptual Architecture.

It applies specifically to:

Full transaction detailTransaction metadataAggregate information productsRelease scopeInformation sensitivity

Verification

Verification SHALL confirm that the Conceptual Architecture distinguishes full transaction detail from transaction metadata and aggregate information products.

Verification activities include review checks confirming that:

Full transaction details remain distinct from transaction metadataFull transaction details remain distinct from aggregate information productsMetadata does not imply a full-detail releaseAggregate products do not imply a full-detail release

Traceability

Related source section:

Related requirement identifiers:

Status

Draft

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