Why-Graph

AI agents ship the change. FalkorDB remembers why it broke. The next PR is checked before it merges.

Overview
Press Next to follow one change from a Band agent to a blocked PR.
Band · AI engineering team room why-graph-demo · 5 Claude Code agents wg-coordinatorassigns, merges wg-engineerwrites the fix wg-reviewerchecks with MCP wg-analystasks the brain wg-chaosmakes the mistake GitHub · astro-shop config/services.yaml PR → review → merge to main payment timeout 800 → 200 astro_sim watches main, diffs the config deploys · telemetry · alerts runtime simulated from latency_ms Why-Graph API FastAPI · grounded agents · MCP server On every incident, in this order Triageroot alert, blast radius Memoryseen this shape before? Causeguilty commit, as a path Commsstatus update, pages owners Every claim cites a Cypher query and the exact nodes; it is re-run to verify. Claude writes the words. The graph decides. FalkorDB one graph per tenant Episodicincidents, findings Semanticlessons, vectors Proceduraldetectors = Cypher services · people · PRs commits · config · runbooks Console · why-graph.vercel.app Incident (live agents, evidence path, Run live) · PR Guard · Memory · Brain · Adopt it React + @falkordb/canvas, streamed over SSE opens PR on merge deploys telemetry alerts Cypher live stream · confirm the fix MCP · check_change_risk · incident_report · why_is · who_knows 1 Agent ships a bad timeoutPR #1, merged 2 Checkout fails, alerts fireINC-1031 opens 3 Agents prove the causecommit → config → payment p99 4 Human confirms, graph learnslesson L-1 + detector D-1 5 Next PR is blockedsafe value ≥ 453 ms