Request evidence correlation in AI Syndicate
AI Syndicate treats request correlation as evidence with structure, not just logs with timestamps. The system correlates gateway activity, control-plane checkpoints, and operator-facing evidence views around a shared requestID so teams can investigate what happened without reconstructing traces by hand.
This still does not replace execution enforcement. Request correlation shows what happened. Enforcement decides what is allowed to happen before side effects occur.
Why request evidence correlation matters
Gateway events
The execution gateway emits accepted, completed, failed, and stream-finalized events with a stable request ID and variant metadata.
Checkpoint correlation
Control-plane checkpoints carry the same request ID so operators can tie governance state to the execution path without manual reconstruction.
Evidence views
Hosted customers get a request-centric evidence page. Enterprise operators get a Request Trace view in the admin console.
Where operators see it
Customer-facing request lookup with evidence timeline, routing detail, policy gate evaluations, and cost context.
Surface: hosted request evidence view
Administrative request trace view for self-hosted operators with ledger-backed request lookup and trace reconstruction.
Surface: /console/#trace
Operator-grade access for incident response, automation, and low-level verification workflows.
Surface: syndicate telemetry events / checkpointPending / gatewayEventsByRequestID
What the request ID unlocks
A shared request identifier lets teams pivot from a user-facing report to the gateway event stream, then into control-plane checkpoints, and finally into policy, parameter binding, and cost evidence. That is the practical difference between “we have logs” and “we can actually investigate this request.”
In the hosted deployment, that view is available directly in the customer console. In the enterprise deployment, the same model is available in the admin console and through local operator tooling.
Next step
For the implementation contract, operator evidence views, and normative request-event requirements, read the companion documentation page.
Read the request evidence correlation guide