dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-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-5-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-5-011:start [2026/07/11 12:57] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== P1-REQ-13-5-011 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
 +
 +===== Statement =====
 +
 +The [[dido:99_annexes:annex-b-terms-and-definitions:p:policy_and_release_plane|Policy and Release Plane]] SHALL support conceptual separation between full transaction detail, transaction metadata, aggregate summaries, derived indicators, redacted views, masked views, exception views, and full-detail release views.
 +
 +===== Source =====
 +
 +Part 1, Section 13.5: Runtime Plane Requirements.
 +
 +===== Rationale =====
 +
 +The Policy and Release Plane needs to distinguish different forms of information and release products. Full transaction detail, transaction metadata, aggregate summaries, derived indicators, redacted views, masked views, exception views, and full-detail release views carry different governance, sensitivity, and release implications.
 +
 +This requirement supports governed release decisions without treating one information form as equivalent to another.
 +
 +===== Applies To =====
 +
 +This requirement applies to Policy and Release Plane definitions and references within the Conceptual Architecture.
 +
 +It applies specifically to:
 +
 +  * Full transaction detail
 +  * Transaction metadata
 +  * Aggregate summaries
 +  * Derived indicators
 +  * Redacted views
 +  * Masked views
 +  * Exception views
 +  * Full-detail release views
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that the Policy and Release Plane supports conceptual separation among the identified information and release forms.
 +
 +Verification activities include review checks confirming that:
 +
 +  * The identified information and release forms remain distinct
 +  * Metadata release remains distinct from the full transaction detail release
 +  * Aggregate release remains distinct from the full transaction detail release
 +  * Redacted, masked, exception, and full-detail views retain distinct meanings
 +
 +===== Traceability =====
 +
 +Related source section:
 +
 +  * [[fxdemo:01-part:13-conceptual-requirements:13-5-runtime-plane-requirements]]
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-5-005:start]]
 +  * [[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-5-015:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>