20.10 Phase 0 Does Not Define Later Phase Implementation Profiles [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== 20.10 Phase 0 Does Not Define Later Phase Implementation Profiles ======

[[fxdemo:04-part:start | Go To Top ]]

[[fxdemo:04-part:20-phase-0-implementation-rules-and-constraints:start | Return to Phase 0 Implementation Rules and Constraints ]]

Phase 0 does not define later phase implementation profiles.

The Phase 0 Implementation Profile defines the selected Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]]. It does not define the final implementation architecture for all development phases, and it does not implement the later Phase 2 [[dido:99_annexes:annex-b-terms-and-definitions:p:policy_and_release_plane|Policy And Release Plane]] extension.

Later implementation profiles may extend, refine, supersede, or replace the Phase 0 Baseline. A later Phase 2 profile may add distributed policy enforcement, replicated policy decision capability, policy administration, policy information sources, local policy caches, metadata or aggregate view builders, release gateways, recipient-specific release products, release [[dido:99_annexes:annex-b-terms-and-definitions:o:obligation|Obligations]], release [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]], additional policy topics or equivalent exchanges, and stronger sovereignty-aware or residency-aware release controls.

Phase 0 implementation choices must preserve [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] and should not preclude those later extensions. However, later phase capabilities must not be treated as Phase 0 requirements unless this implementation profile is explicitly revised and re-baselined.

<WRAP centeralign>

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

</WRAP>