1.1 Purpose of the Handbook

Return to Purpose and Scope

The purpose of this handbook is to define the practical conventions and development rules for creating, running, inspecting, and reviewing the Phase 0 implementation Baseline. It translates the architectural guidance established in Parts 1 through 4 into implementation-facing practices for Repository organisation, development tooling, generated Artifacts, DDS/IDL type generation, Node implementation, Control Plane behaviour, build and run scripts, containerisation, logging, Exception Handling, Git workflow, and Acceptance Criteria.

The handbook exists to prevent Phase 0 from becoming an informal prototype. Phase 0 is a demonstration Baseline, but it should still be disciplined, Reproducible, traceable, and reviewable. Every source file, generated Artifact, script, Configuration file, container, Node, and topic should have an identifiable purpose within the implementation Baseline and should remain Traceable to the architecture or to an explicitly documented implementation need.

The handbook is also intended to support shared team practice. Developers, architects, reviewers, and demonstration participants should be able to use the same conventions when creating Artifacts, reviewing changes, running the system, collecting Evidence, and explaining how the Phase 0 Baseline supports the larger Financial Systems Archetype.