====== 15.8 Logging Convention Requirements ======

[[fxdemo:04-part:15-phase-0-developer-handbook-requirements:start | Go To Phase 0 Developer Handbook Requirements ]]

The Developer Handbook must define logging conventions for Phase 0 implementation artifacts.

Logging conventions must identify:

  - Required log fields
  - [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] or participant identity fields
  - [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] context where applicable
  - Correlation identifiers
  - Timestamps
  - Lifecycle-state events
  - Processing outcomes
  - Warnings
  - Degraded operation
  - Failures
  - Recovery attempts
  - Command handling
  - Publication and subscription failures
  - Validation or processing failures
  - Relationship to audit and provenance records where applicable

Logging supports Health and Observability when it describes operational condition. Logging supports Audit and Provenance when it preserves information needed for review, replay, reconstruction, or [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] planning. Logging supports Control Plane behavior when it records commands, acknowledgments, retries, recovery, or operational coordination.

----

<WRAP centeralign>

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

</WRAP>