ii·Incident InvestigatorOPERATIONS / RESEARCH LAB
Synthetic environment v0.1

EVIDENCE BEFORE ACTION

Understand the incident.
Show your working.

Follow an investigation from an alert to observations, retrieved runbooks, and a supported diagnosis.

02 / INVESTIGATEREADY

SYNTHETIC INCIDENT

Choose an incident

Read-only tools · cited runbooks

A diagnosis should leave a trail.

Run this incident to see which tools were called, what they found, and which runbook sections informed the response.

Observe→Retrieve→Explain

WHAT IS ACTUALLY HAPPENING?

One loop. Three building blocks.

01

The investigator

In LLM mode, the model chooses its next tool based on previous observations. A fixed budget keeps the investigation bounded. Demo mode uses a transparent reference policy instead.

02

The tools

Six allowlisted functions read scenario evidence and search runbooks. There is no shell, mutation tool, arbitrary URL fetch, or live Kubernetes connector.

03

The knowledge

BM25 retrieves relevant runbook sections. The response cites retrieved chunks and observed evidence. Missing evidence must lead to uncertainty, not an invented diagnosis.