Agent Graph Engineering series: services, contracts, subgraphs, human-in-the-loop
huygl99 · reddit · 2026-11-02
A developer's ongoing Agent Graph Engineering write-up (parts 2-7) walks through production agent architecture decisions one at a time: separating product and agent services before prompts silently rot; declaring shapes once and generating clients so the compiler catches renames; constraining what each step may return; at-most-once execution for irreversible actions plus fencing customer words as data instead of scanning them; splitting one graph into specialists with a supervisor routing ("an agent cannot go off script" is the whole point for refund-issuing systems); and human-in-the-loop failure modes like approvals that silently never send. Upcoming parts cover streaming progress, tracing costs, and swapping models or prompts safely.
More from coding & agent
- GitHub Actions has a lesser-known ubuntu-slim runner: 1 CPU, 5GB RAM, cheaper CI — DanielLockyer · 2026-11-02
- Before automating a workflow with AI, ask if anyone understands it end to end — djgoel123 · 2026-11-02
- One stale date silently broke a WhatsApp reply agent: 19 messages unanswered — petrusenko_max · 2026-11-02
- The 10X engineer is now just a SKILLS.md: 6 workflow rules for AI coding agents — mdancho84 · 2026-11-02
- Auditing my MCP credential broker: the worst hole was the config file — Relevant_Mousse_9117 · 2026-11-02
- AWS's open-source Strands Harness claims 45% cheaper than Claude Code, reigniting harness debate — blaizedsouza · 2026-11-02