====== 6.5 Prerequisite Validation ======

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

[[fxdemo:05-part:06-prerequisites-and-tooling:start | Return to Prerequisites and Tooling ]]

The ''checkPrerequisites.sh'' script should validate the required tools before the developer generates [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]], builds containers, runs [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]], or collects acceptance [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]].

The script should check:

  - Required commands are available on the path.
  - Required versions meet the [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] expectations.
  - Required environment variables exist and point to valid locations.
  - Required [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] tooling can run.
  - Required container tooling can run.
  - Required Python support exists, if Python utilities form part of the Baseline.
  - Required runtime language tools exist, if Phase 0 Nodes or generated bindings need them.
  - Required [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] directories and [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] templates exist.

The script should produce clear, actionable output. When a check passes, the script should report the result briefly. When a check fails, the script should explain what failed, why it matters, and what the developer should inspect or install next.

The script should return a non-zero exit code when a required prerequisite fails. It may return warnings for missing optional tools, but those warnings should not block Baseline execution unless the developer requested a workflow that depends on the optional tool.

----

<WRAP centeralign>

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

</WRAP>