Business documents rarely keep their most useful information in convenient database records or JSON objects. Invoices hold line items in tables, financial reports organize figures by period, inspection forms group findings by category, and emailed statements often arrive as attachments or message files.
Before our applications can validate, compare, search, or store that information, they have to somehow recover the relationships between rows, columns, headers, and values.
AI stands for artificial intelligence, yet I prefer the term Dr. Venkat Subramaniam used in one of his talks: Accelerated Inference. To my mind, it is far more accurate, so I have embraced it.
And “accelerated” is precisely the point. With AI, generating code has become cheap; it is no longer the bottleneck of software development. What has become expensive, and what this article is really about, is everything around it: aligning outcomes with intent, owning what we ship, and exercising the judgment that no amount of acceleration can replace.
A few months back, I wrote about Loop Engineering: The Layer After Prompt, Context, and Harness Engineering, arguing that once your prompts are tuned, your context is assembled, and your harness is wired up, the thing that actually determines whether an agent works is the loop it runs in: how it decides to keep going, stop, retry, or hand off. A few readers asked a fair follow-up after that piece: loops over what, exactly? What happens when one job stops being one loop's worth of work?
That question turned out to have an answer that was already forming across the AI engineering world by the time I went looking for it. Mid-July 2026 saw a fast, noisy round of debate on X about exactly this, kicked off by a question from OpenClaw creator Peter Steinberger about whether the conversation had already moved past loops into graphs. Within a couple of days it had a name: graph engineering. I want to walk through what it actually means, where it overlaps with loop engineering, and where I think the skeptics in that debate had a fair point.
Comments
Post a Comment