15.9 Exception-Handling Requirements

Go To Phase 0 Developer Handbook Requirements

The Developer Handbook must define exception-handling patterns for Phase 0 implementation artifacts.

Exception-handling requirements must identify:

Processing boundaries where implementation Nodes capture exceptionsRequired exception contextNode or participant identityCorrelation identifiersAffected logical interaction where availableAffected DDS Topic or generated type where availableTimestampException type or error categoryProcessing outcomeRetry or recovery expectationHealth-reporting effectAudit/provenance effectControl-plane effect where applicableOperational exceptions must support Health and Observability when they describe node condition, degradation, failure, warning, or recovery. Exceptions that affect logical processing, lineage, replay, reconstruction, release, or Evidence must support Audit and Provenance. Exceptions that require retry, pause, resume, restart, or recovery coordination must support Control Plane interaction.

Exception handling must not hide processing failures. An implementation artifact must either handle the exception according to the approved pattern or report the failure through the appropriate logging, status, audit/provenance, or control mechanism.

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