Hacker
Raghav Gupta
@ragxx
- Top 50
HYPOCENTER
Graph HacksOct 2026
When production breaks, three deploys, a config change and a feature flag have often all landed in the last hour, and the on-call engineer has minutes to pick which one to roll back. Most incident tools show that services are failing. The ones that guess why usually blame the latest deploy. On my planted faults that guess is right only 50% of the time, so teams roll back the wrong thing while the real cause keeps burning. Hypocenter is an on-call agent for SRE and platform teams that finds what actually started the failure. It works by one rule: no path, no blame. A change can be a suspect only if the FalkorDB graph connects it to the failing service, and it leads only if the alerts climb that path in order. "Nothing changed" and "a shared host" are valid answers too. Four agents take each incident in turn: Triage, Investigator, Skeptic and Responder. They hand off through the graph, never directly, so every step of the reasoning is a node you can query. Every verdict passes 8 named checks, each shown with the Cypher that decided it. If the graph can't connect the failure, Hypocenter says it can't prove it instead of guessing. The agent only proposes. Before a person approves, the fix is proven on a copy of the graph. After approval Hypocenter checks the alerts really cleared, and it reopens the incident if they didn't. It also works as a company brain: it answers "why was this change made?" from the team's chat, remembers what "it" meant in a follow-up question, and gives a ship / review / hold call before a deploy. Results: 81% right service first on all 360 failures in the public RCAEval benchmark, run against the benchmark's own baseline code. 71% on 90 failures held out until the method was frozen. NSigma scores 76% there, and I report that loss. 94.5–96.8% on planted faults full of decoys, vs 50% for "blame the latest deploy".
Saans
Environmental HacksOct 2026
https://builder.aws.com/post/3KYcX3G8EWzBWCMOjE12SlH9TzQ_p/we-built-saans-so-no-farmer-in-punjab-has-to-burn-stubble-again-and-shipped-it-on-aws