6.6 Logging and Exception-Handling Baseline [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.

====== 6.6 Logging and Exception-Handling Baseline ======

[[fxdemo:04-part:06-phase-0-implementation-preconditions:start | Go To Phase 0 Implementation Preconditions ]]

The Phase 0 logging and exception-handling baseline must exist before implementation Nodes process FX information.

The logging baseline identifies the required logging conventions, log categories, Node identity fields, timestamps, correlation identifiers, lifecycle-state reporting, processing outcome reporting, and the relationship to Health and Observability, Audit and Provenance, and Control Plane concerns.

The exception-handling baseline identifies the processing boundaries where implementation Nodes capture exceptions, the information each exception record must preserve, and the conditions under which an exception affects health reporting, audit/provenance recording, Control Plane action, retry, recovery, or release eligibility.

Operational exceptions support Health and Observability when they describe Node condition, degradation, failure, warning, or recovery. Exceptions affecting logical processing, lineage, replay, reconstruction, release, or [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|evidence]] support Audit and Provenance. Exceptions requiring retry, pause, resume, restart, or recovery coordination support Control Plane interaction.

----

<WRAP centeralign>

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

</WRAP>