# Why-Graph

Agents that must prove why production broke as a graph path, then block the next agent from repeating it.

- Dates: 15–18 Oct 2026 · Graph Hacks 2026 (WeMakeDevs × FalkorDB)
- Team: team of 2 with Shoban Ravichandran
- My part: Agent runtime and the four agents, ingest, MCP server, PR Guard, UI, demo app, live deploy, demo video
- Verified: 453 ms safe minimum the guard enforced; 167 passing tests; 5 MCP tools for other agents; ~950 nodes in the demo graph
- Result: judging pending
- Case study: https://solaimuthu.vercel.app/work/why-graph

### The problem

AI coding agents ship around the clock, so they also break production around the clock. An LLM's root-cause story can't be checked, and nothing stops a second agent from repeating the first agent's mistake on another service.

### How it works

A deterministic Python orchestrator in FastAPI runs four agents: Triage and Memory in parallel, then Cause, then Memory again, then Comms. They share one FalkorDB graph as a blackboard: an investigation has findings, and findings have evidence.

Agents may only call named Cypher queries from a catalog (root alert, blast radius, suspect changes, config versus reality, similar incidents, who knows). There is no free-form query writing. Every finding is re-verified. Recording a finding re-runs the cited query and rejects any claim whose nodes and edges are not in the result. Confidence comes from graph signals, never from the model. Confirmed incidents become memory. A lesson and a detector are stored as Cypher, backtested against past changes, and exposed to outside coding agents as MCP tools and as a pull-request guard.

### What happened in the demo

An agent opened a pull request on our astro-shop demo app to "reduce checkout latency" by cutting the payment timeout from 800 ms to 200 ms, below payment's p99 of 446 ms. The guard honestly reported no known risk, because the graph had never seen that failure. It merged, and the staged incident took checkout errors to 62%.

The agents proved the cause as a graph path, and one click turned it into a lesson: a caller's timeout must be at least 1.5× the callee's p99. Then a fresh agent tried the same mistake on a different service and was blocked with a safe minimum of 453 ms.

### Decisions

The graph decides, not the model. A "graph-only" switch turns the LLM off and every verdict stays the same. That's the test that the graph isn't decoration. Honest guard output. Before the lesson existed, the guard said "no known risk" instead of guessing.

### My part

I built the agent runtime and the four agents, ingest, the MCP server, the PR guard and the SDE agents, plus the UI, the demo shop and its simulator, the live deploy and the demo video. Shoban Ravichandran built the graph and memory layer: seed data, the Cypher catalog, similarity and detectors.
