Differences

This shows you the differences between two versions of the page.

--- fxdemo:04-part:14-phase-0-repository-and-build-artifact-model:14-7-script-directory-model:start [2026/08/04 07:08] – ↷ Links adapted because of a move operation nick_dido
+++ fxdemo:04-part:14-phase-0-repository-and-build-artifact-model:14-7-script-directory-model:start [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 7: / Line 7: @@
 Scripts may support prerequisite checking, repository preparation, IDL generation, build preparation, node execution, multi-node startup, multi-node shutdown, cleanup, or other controlled implementation tasks. Each script must identify its purpose, expected inputs, expected outputs, affected artifacts, logging behavior, error-handling behavior, and relationship to the Phase 0 implementation baseline.
-Scripts support implementation activity. They do not redefine logical [[dido:99_annexes:annex-b-terms-and-definitions:n:financial_node|Nodes]], logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoints]], interaction patterns, [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]], or governance relationships.
+Scripts support implementation activity. They do not redefine logical [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Nodes]], logical [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Communication Endpoints]], interaction patterns, [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]], or governance relationships.
 Scripts that affect generated artifacts, repository state, runtime execution, or [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] must follow the Phase 0 Developer Handbook and repository workflow.