Loop Engineer vs Graph Engineeras defined on X

@mingrath

Two job titles, six weeks apart. What people on X actually mean — from posts dated 7 Jun to 26 Jul 2026.

Loop Engineer vs Graph Engineer animated diagramTop-down architecture diagram; dashed connectors animate in the direction of flow and glowing dots ride the main paths.the ceilingshared memoryLOOP ENGINEERappeared June 2026The claimDesign loops, don't promptOne agent, one cycleplan → act → verifyFour typesturn · goal · time · eventMarks its own homeworkSame agent grades it: 10/10Forgets at the edgeMemory dies with the windowGRAPH ENGINEERappeared July 2026The claimNine-word post, 500k viewsExplicit topologyNodes, edges, branchesSpecialised rolesManager · workers · judgeIndependent reviewA fresh agent grades it: 5.5State outlives the runTyped edges with provenanceservicesecuritydatacloud infrarequest in flight

The lineage people keep posting

  • • Prompt engineering — 2022
  • • Context engineering — 2025
  • • Harness engineering — Feb 2026
  • • Loop engineering — Jun 2026
  • • Graph engineering — Jul 2026

When a loop becomes a graph

  • • One agent can't hold the whole task
  • • Work must fan out in parallel, isolated
  • • You need a reviewer that didn't do the work
  • • State must survive the context window

Read the hype critically

  • • One PDF, credited to Anthropic, Ng, Karpathy and IBM
  • • Nearly every post ends 'article below'
  • • Multi-agent burns roughly 15x the tokens
  • • 'Graph engineer' is also a Neo4j data role

Researched from X posts. The patterns are real; the attributions in the viral threads are not.