Tracing shows the route an action took.

Video caption

Tracing shows the route an action took.

Policy version and authorized scope are business facts.

Case ID, operation ID and effect receipt connect the layers.

My rule: Use links for explanation, separate checks for action.

#EricFieldNotes

Full written post / accessibility read

OpenTelemetry's current messaging conventions describe creation context and span links for asynchronous producer-consumer correlation. That is useful when an agent delegates and results arrive out of order.

A trace span may be marked successful because a message handler ran. The protected journal must still name who authorized the operation and which target effect the message was meant to produce.

Propagate enough correlation to reconstruct causality. When a late child reports completion, compare its identity and policy version with the decision record, then read the target independently.

Observability should tell the operator what happened. An authorization check and outcome readback decide what may be called complete. Do that because a successful message path can carry a stale or unauthorized decision.

#EricFieldNotes

Four-beat scene transcript

1. Tracing shows the route an action took.

OpenTelemetry's current messaging conventions describe creation context and span links for asynchronous producer-consumer correlation. That is useful when an agent delegates and results arrive out of order.

Visual: It does not decide whether the action was allowed or finished.

2. Keep a decision journal beside the trace.

A trace span may be marked successful because a message handler ran. The protected journal must still name who authorized the operation and which target effect the message was meant to produce.

Visual: Policy version and authorized scope are business facts.

3. Join on stable identities.

Propagate enough correlation to reconstruct causality. When a late child reports completion, compare its identity and policy version with the decision record, then read the target independently.

Visual: Case ID, operation ID and effect receipt connect the layers.

4. Do not promote telemetry to permission.

Observability should tell the operator what happened. An authorization check and outcome readback decide what may be called complete. Do that because a successful message path can carry a stale or unauthorized decision.

Visual: Use links for explanation, separate checks for action.

Research and claim limits

• OpenTelemetry messaging spans (S217)
• Temporal Child Workflows (S216)

The examples identified as illustrative or simulated are design probes, not reported incidents. Vendor specifications do not establish workload performance.