16.9 Script Logging and Error Handling [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.9 Script Logging and Error Handling ======

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

All Phase 0 scripts must follow the logging and error-handling conventions defined by the Developer Handbook.

Script logging should identify:

  - Script name
  - Script purpose
  - Invocation timestamp
  - User or execution context where appropriate
  - Working directory
  - Affected artifacts
  - Command or task being performed
  - Outcome
  - Warnings
  - Errors
  - Cleanup actions
  - [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] context where applicable

Script error handling must prevent silent failure. A script that cannot complete its required task must report the failure, return an appropriate exit status where applicable, and avoid leaving baseline artifacts in an ambiguous state.

Scripts that affect generation, repository state, runtime execution, or traceability must treat errors as implementation-governance concerns. They must not hide failed generation, partial startup, invalid configuration, missing prerequisites, or failed cleanup.

----

<WRAP centeralign>

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

</WRAP>