An architect is selecting observability components for a multi-agent fraud-investigation system that must support reproducible debugging when investigators challenge an automated conclusion weeks later. Which capability set should be specified?
Select an answer to reveal the explanation.
Short Explanation
The correct answer is A. Reproducible fraud debugging weeks later needs correlated traces, structured reasoning logs, and replay capture—not a lonely CPU chart, tribal chat memory, or immediate deletion of every prompt and tool payload.
Full Explanation
Option A is correct. Architecture skills explicitly call for observability components including cross-service trace correlation, structured logging of agent reasoning paths, and agent replay capture for reproducible debugging—essential when conclusions may be challenged later in fraud workflows.
Option B is incorrect because host CPU metrics lack per-investigation causal detail.
Option C is incorrect because human recollection is incomplete and non-auditable for regulated investigations.
Option D is incorrect because discarding prompts and tool payloads may undermine required reconstructability and audit needs (retention should follow policy, not zero-by-default when replay is required).