FIELD NOTE / X
A green trace is not a green outcome.
The short film, the complete written thought, and the evidence behind it.
The X conversation link will follow its public release.
A green trace is not a green outcome.
Video caption
A green trace is not a green outcome. The decision needs its own protected identity. Keep authority and outcome in separate records. #EricFieldNotes
Full written post / accessibility read
The supervisor delegates a pool move and the consumer span ends successfully. That proves instrumentation observed message processing. It does not prove the worker held the current policy or the service converged.
Propagate case ID, operation ID and source-policy version with the task. Link producer and consumer spans for causality, while a separate journal records authorization and target readback.
When a worker reports success after its parent times out, correlate the message to the original action and read the target. Without that identity, the result cannot safely close the original case.
Use messaging links to reconstruct what happened, then require current authorization and target evidence before declaring complete. Do that because a transport-success span is not a customer-outcome oracle.
#EricFieldNotes
Four-beat scene transcript
1. A green trace is not a green outcome.
The supervisor delegates a pool move and the consumer span ends successfully. That proves instrumentation observed message processing. It does not prove the worker held the current policy or the service converged.
Visual: A message can arrive while its business decision is wrong.
2. Carry more than a trace ID.
Propagate case ID, operation ID and source-policy version with the task. Link producer and consumer spans for causality, while a separate journal records authorization and target readback.
Visual: The decision needs its own protected identity.
3. Bind the late observation.
When a worker reports success after its parent times out, correlate the message to the original action and read the target. Without that identity, the result cannot safely close the original case.
Visual: A child result must name the case it changes.
4. Observability explains; it does not approve.
Use messaging links to reconstruct what happened, then require current authorization and target evidence before declaring complete. Do that because a transport-success span is not a customer-outcome oracle.
Visual: Keep authority and outcome in separate records.
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.