11-13
Graph Engineering: Building a CI Triage Agent Graph
A how-to for replacing a single agent loop with a graph of specialists: nodes each own one verb and a scoped context, edges are deterministic routing code, a shared state file carries history across runs, and a gate decides done or not done. The worked example is a GitHub Actions failure triage system, with copy-ready agent definitions for a classifier and a bug fixer, edge rules that keep hard constraints out of prompts, a STATE.md layout, and a test-gate prompt. Autonomy is staged from manual /goal to scheduled /loop to cloud Routines. The author concedes most teams should not build one yet, and names comprehension debt as the cost of a graph that ships code nobody reads.