4.4 Phase-Specific Nature of the Profile [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.

====== 4.4 Phase-Specific Nature of the Profile ======

[[fxdemo:04-part:04-phase-0-implementation-profile-overview:start | Go To Phase 0 Implementation Profile Overview ]]

This part defines a phase-specific implementation profile.

A phase-specific implementation profile identifies the implementation decisions that apply to a defined development phase. It controls implementation work for that phase without claiming to define the permanent implementation architecture for all later phases.

The Phase 0 profile establishes the implementation baseline for the first demonstrable FX Demo implementation. Later phases may define additional implementation profiles that add functionality, change technology selections, refine generated artifacts, introduce additional runtime packaging, strengthen governance, expand evidence expectations, or support additional deployment environments.

A later implementation profile may extend, refine, supersede, or replace this Phase 0 profile. The later profile still preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] to the applicable Part 1 concepts, Part 2 logical elements, Part 3 FX logical profile elements, and prior implementation artifacts where continuity matters.

----

<WRAP centeralign>

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

</WRAP>