13.1 Purpose of Build and Run Scripts

Go To Top

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 Repository structure, check prerequisites, initialize the Python environment, generate DDS/IDL types, build containers, run Nodes, stop Nodes, prepare Git, or collect validation Evidence.

The scripts should support the following goals:

1. Reduce manual setup errors.
2. Make developer workflows consistent.
3. Capture expected command sequences.
4. Validate assumptions before making changes.
5. Produce useful diagnostic output.
6. Return meaningful exit codes.
7. Support review, testing, and acceptance Evidence.
8. 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.