====== 16.11 Script Model Summary ======

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

The Phase 0 Script and Execution Model defines how scripts support repeatable implementation work while preserving architectural [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] and implementation discipline.

**Table 16-1: Summary of Phase 0 script categories**

^ Script category ^ Phase 0 purpose ^
| Prerequisite checking | Confirms required tools, directories, configuration, dependencies, and handbook availability before generation or execution. |
| Type generation | Generates implementation types from governed IDL definitions. |
| Build preparation | Validates or prepares the repository for local execution, demonstration, or later deployment planning. |
| [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] execution | Starts a selected implementation participant. |
| Multi-node startup | Starts a controlled set of implementation participants for demonstration or interaction flow execution. |
| Multi-node shutdown | Stops implementation participants and records shutdown behavior. |
| Cleanup | Removes or isolates temporary artifacts according to repository workflow. |
| Log collection | Collects script or runtime logs where Phase 0 requires review or later evidence planning. |
| Workflow checking | Supports repository, naming, traceability, generated-file, or review checks. |

Scripts provide controlled support for implementation activity. They do not replace architecture, implementation mappings, developer rules, deployment planning, or evidence planning.

----

<WRAP centeralign>

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

</WRAP>