====== 1.4 How to Use This Handbook ======

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

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

This handbook should be used as the operational companion to the architecture documents. Parts 1 through 4 remain authoritative for conceptual framing, distributed logical architecture, the FX Demo Logical Profile, and Phase 0 implementation source material. This handbook provides the development conventions and execution practices needed to implement the Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] consistently.

Developers should use the handbook before creating or modifying implementation [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]]. [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] structure, file naming, generated Artifacts, script conventions, [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] behaviour, logging, [[dido:99_annexes:annex-b-terms-and-definitions:e:exception_handling|Exception Handling]], and documentation expectations should be checked against this handbook before changes are committed.

Reviewers should use the handbook as a checklist for implementation discipline. A change should not be accepted simply because it works locally. It should also be [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceable]], [[dido:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducible]], documented, reviewable, and consistent with the Phase 0 Baseline.

The handbook should also be treated as a living Baseline document. If the team makes a deliberate implementation decision that changes the expected Repository structure, tooling, scripts, generated Artifacts, Node pattern, or [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]], the handbook should be updated so that the written guidance and the actual implementation remain aligned.

The practical test for this handbook is whether a qualified team member can use it to check out the Repository, prepare the environment, generate required Artifacts, build the containers, run the Node network, observe [[dido:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]] status, stop the system, inspect logs, and understand whether the Phase 0 Baseline has met its Acceptance Criteria.

----

<WRAP centeralign>

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

</WRAP>