Investigator
In one line: It correlates signals across sources and hands a human a case file, not a guess.
What it is
An Investigator answers “why did this happen?”. It pulls signals from several places, lines them up, and hands a person a case file: what it looked at, what it found, how sure it is and what it could not check. The person decides what to do.
How one run goes
- Take a case: an alert, a complaint, a number that looks odd.
- Gather evidence from several sources.
- Correlate it: line events up in time and by likely cause.
- Write the case file with findings, their sources, a likely cause, a confidence and the gaps.
- Hand it to a person. It does not act on its own conclusion.
An example
Failed checkouts spike. The Investigator reads the error log, the list of recent deploys and a payment provider’s status page, notices the spike started three minutes after a deploy, and files a case with the three links and what it could not see.
Where the human comes in
A human reviews the case file and makes the call; the agent never acts on its own conclusion.
Use it when
Triage eats time because the evidence is spread over several tools. It is not the right shape when one dashboard already answers the question.
Watch out for
A confident wrong answer is worse than none. Make it cite a source for every claim and say plainly what it could not check.
Back to all patterns or the Idea Gallery. A pattern is a shape to borrow when it fits, not a category: the gallery cards do not carry one.