====== 13.1 Purpose of Build and Run Scripts ======

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

[[fxdemo:05-part:13-build-and-run-scripts:start | Return to Build and Run Scripts ]]

Build and run scripts should make common Phase 0 tasks repeatable. A developer should not need to remember a long sequence of manual commands to create the [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] structure, check prerequisites, initialize the Python environment, generate [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]]/[[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] types, build containers, run [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]], stop Nodes, prepare Git, or collect validation [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]].

The scripts should support the following goals:

  - Reduce manual setup errors.
  - Make developer workflows consistent.
  - Capture expected command sequences.
  - Validate assumptions before making changes.
  - Produce useful diagnostic output.
  - Return meaningful exit codes.
  - Support review, testing, and acceptance Evidence.
  - Avoid hidden dependencies on one developer's machine.

The scripts should not hide architectural decisions. A script may automate a workflow, but the handbook, catalogues, Configuration files, and implementation decision records should still explain the Baseline assumptions that the script applies.

----

<WRAP centeralign>

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

</WRAP>