A public-health case-reporting agent has been redeployed several times, and an auditor needs to reconstruct exactly which agent version handled a specific case report submitted six months ago. Where should the auditor look first?
Select an answer to reveal the explanation.
Short Explanation
Reconstructing which agent version handled a case six months back is like asking which edition of a manual an employee was using on a specific day — you need the edition history, not just the delivery receipts. Agent Registry keeps that edition history, tying versions to the windows when each was live. Traffic logs and scan reports can tell you what happened, but neither one tells you which build was doing it.
Full Explanation
Agent Registry maintains a version history for each deployed agent, recording which build was active during a given time window, which is precisely the record an auditor needs to tie a six-month-old case report back to the specific agent version that produced it. Deployment logs record the act of deploying, but unless they are cross-referenced against a maintained version history they don't reliably answer "what was live at time X," especially across several redeployments where logs may be rotated or incomplete. Agent Gateway's traffic logs capture the content and pattern of tool calls, which is useful for seeing what the agent did, but a log entry showing a tool call doesn't by itself identify which agent build issued it unless that version metadata was captured alongside. Sensitive Data Protection's scan reports address a completely different concern — flagging sensitive content in stored data — and have no relationship to agent versioning at all. A scope caveat: version history answers which build was active, but reconstructing the full behavior of that version for the audit may still require correlating it with the corresponding traffic or execution logs from that period. As an operational check, an auditor can query Agent Registry for the version window covering the report's timestamp and cross-check that version's configuration against what the traffic log shows for that call.