Foreword [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.
====== Foreword ======

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

The Financial Systems [[dido:99_annexes:annex-b-terms-and-definitions:a:archetype|Archetype]] has developed from a conceptual architecture into a practical implementation pathway. Parts 1 through 4 establish the architectural foundation, the reusable distributed logical architecture, the FX Demo Logical Profile, and the Phase 0 implementation source material. This part, the Phase 0 Developer Handbook, moves the work one step closer to execution by defining the conventions, [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] structure, tooling, scripts, generated [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]], [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] patterns, and review expectations needed to create a disciplined demonstration [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]].

Phase 0 is intentionally modest in functional scope but significant in architectural terms. Its purpose is not to deliver a production financial system, a complete ACTUS implementation, or a fully governed IEF release environment. Its purpose is to demonstrate that the architectural ideas can be realized as a working, observable, repeatable Node network. The initial implementation demonstrates that Nodes can be defined, built, started, stopped, observed, and coordinated via a shared [[dido:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]] while preserving [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] to the architecture.

This handbook is therefore both practical and architectural. It is practical because it gives developers and reviewers concrete guidance on Repository layout, file naming, generated code, scripts, containers, logging, [[dido:99_annexes:annex-b-terms-and-definitions:e:exception_handling|Exception Handling]], and [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]]. It is architectural because those practical conventions are not arbitrary. They are intended to protect the separation between architecture and implementation, maintain the discipline of the SIP-RA and [[dido:99_annexes:annex-b-terms-and-definitions:f:fdis-ra|FDIS-RA]], and ensure that Phase 0 remains a governed demonstration rather than an uncontrolled prototype.

The handbook should be read as a working guide for the team. It provides enough structure to support consistent implementation, but it does not attempt to replace the architecture documents that precede it. Where detailed architectural meaning is required, the relevant source documents remain authoritative. Where implementation discipline is required, this handbook provides the operational rules of the road.

The goal is simple: create a Phase 0 Baseline that the team can build, run, inspect, explain, and improve. If the Baseline is [[dido:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducible]], traceable, reviewable, and understandable, then it will have served its purpose. It will provide the project with a stable foundation for subsequent development and the September 2026 demonstration.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>