16.10 Script Approval and Baseline Status [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== 16.10 Script Approval and Baseline Status ======

[[fxdemo:04-part:16-phase-0-script-and-execution-model:start | Go To Phase 0 Script and Execution Model ]]

A script becomes part of the Phase 0 implementation baseline only after review and approval under the repository workflow.

Approved baseline scripts must follow the Developer Handbook. They must include the required script header, purpose statement, usage guidance, input expectations, output expectations, logging expectations, error-handling expectations, and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] references.

Non-baseline scripts, exploratory scripts, local developer scripts, or scratch automation must remain outside the approved implementation baseline unless the repository workflow explicitly marks them and prevents confusion with approved scripts.

This distinction protects the Phase 0 implementation baseline from uncontrolled automation.

----

<WRAP centeralign>

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

</WRAP>