Hacker
Vaishali Thakur
@vaishali3837
Projects
Faultline: an on-call agent that can't blame a deploy until FalkorDB proves it
Graph HacksOct 2026
It's 2 a.m. and checkout is failing. Three changes shipped in the last hour. The on-call engineer has to pick one to roll back, and if they pick the wrong one, the outage gets worse. AI agents don't help much here today, because they answer with confidence instead of proof. We built 140 incident worlds designed to fool them, and a strong LLM working alone blamed an innocent change 37 times. Faultline is an on-call agent for SRE and platform teams with one rule: no path, no claim. It may not blame a change until FalkorDB shows two things. First, there is a causal path from that change to the symptom (algo.SPpaths). Second, that path has enough capacity to carry the damage we actually measured (algo.maxFlow). If either check fails, the agent says "I don't know" and hands the incident to a human. We think that honesty is the most important feature. When the proof holds, it does what a good on-call engineer would do: - finds the smallest containment with a max-flow min-cut, and tries it first on a GRAPH.COPY of the graph - works out who should fix it (HarmonicCentrality) and pages them - takes one human-approved action: a real GitHub pull request, or a data repair it proposes from its own measurements - checks that the action really landed through a second channel: GitHub plus telemetry, or a warehouse rebuild with its invariant suite - writes the decision back to the graph, so the next incident starts warm What we measured: - 0 confident wrong blames across 1,540 generated incident worlds, and 0 across 40 windows on the real OpenTelemetry Demo - with Claude driving the investigation: 40 of 40 right causes and 0 wrong blames The same graph also blocks risky pull requests before they merge. It answers "who owns this, who knows it, and who decided it" with node ids you can open and check.
CoffeeAndCode@prashantthakur77,@puneet1625,@lakshaydeol