P1-REQ-13-6-009

Return to Part 1 Requirements

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

Part 1, Section 13.6: Separation of Concerns Requirements.

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.

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

It applies specifically to:

• Full transaction detail
• Transaction metadata
• Aggregate information products
• Release scope
• Information sensitivity

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 metadata
• Full transaction details remain distinct from aggregate information products
• Metadata does not imply a full-detail release
• Aggregate products do not imply a full-detail release

Related source section:

• 13.6 Separation of Concerns Requirements

Related requirement identifiers:

• P1-REQ-13-5-011
• P1-REQ-13-5-015
• P1-REQ-13-6-001
• P1-REQ-13-6-012

Draft