1.2 Scope of Phase 0 [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.
====== 1.2 Scope of Phase 0 ======

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

[[fxdemo:05-part:01-purpose-and-scope:start | Return to Purpose and Scope ]]

Phase 0 establishes the first executable implementation [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] for the Financial Systems [[dido:99_annexes:annex-b-terms-and-definitions:a:archetype|Archetype]]. Its scope is intentionally limited. The objective is to create a working, observable, and repeatable [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] network that demonstrates the basic implementation discipline required for later phases.

Phase 0 includes [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] setup, prerequisite checking, development [[dido:99_annexes:annex-b-terms-and-definitions:e:execution_environment|Environment]] preparation, [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]]/[[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] type generation, generated [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] management, basic Node implementation patterns, [[dido:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]] status reporting, simple command handling, containerised execution, logging, [[dido:99_annexes:annex-b-terms-and-definitions:e:exception_handling|Exception Handling]], and Baseline [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]].

Phase 0 also includes the initial Hello World-style Node network. These Nodes are not intended to perform full financial processing. Their purpose is to demonstrate that defined [[dido:99_annexes:annex-b-terms-and-definitions:n:node_role|Node Roles]] can be implemented as runtime participants, started, stopped, observed, and coordinated through shared Control Plane topics.

Phase 0 does not include full production readiness, complete ACTUS processing, complete financial-domain semantics, full IEF [[dido:99_annexes:annex-b-terms-and-definitions:p:policy|Policy]] enforcement, production-grade [[dido:99_annexes:annex-b-terms-and-definitions:s:security|Security]], enterprise [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment|Deployment]], [[dido:99_annexes:annex-b-terms-and-definitions:p:performance|Performance]] optimisation, or a full operational dashboard. These remain future concerns unless explicitly introduced by a later phase or approved change to the Baseline.

Phase 0 also does not implement the later Phase 2 Policy / Governance Plane or Release Plane extensions. The Phase 0 Repository, Node pattern, topic naming conventions, IDL/type-generation [[dido:99_annexes:annex-b-terms-and-definitions:w:workflow|Workflow]], logging rules, Exception Handling rules, container conventions, and review practices should nevertheless avoid choices that would prevent later addition of distributed Policy enforcement, replicated Policy decision capability, Policy administration, Policy information sources, local Policy caches, metadata or aggregate view generation, release gateways, recipient-specific release products, release [[dido:99_annexes:annex-b-terms-and-definitions:o:obligation|Obligations]], and release [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]].

----

<WRAP centeralign>

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

</WRAP>