Pareto 20, No. 6: Mark Laursen, for the ways an agent fails after you stop watching

He names the failure modes of long-running agents, from loops that never end to frameworks that count corrupted data as success. He also sells the fix, and says so. Read the diagnosis; weigh the prescription.

Seat 6 on The Pareto 20 is Mark Laursen, and it is the seat for a question that only shows up on your invoice: what does an agent do in hour nine, when nobody is looking.

Who he is

Laursen describes himself as a Portugal-based founder with 25 years in software and gaming, including co-founding the Nihilum World of Warcraft guild. Since March 2026 his blog has published one or two long pieces a month on running agents in production, drawing on what he reports as 18 months of first-hand operation. He is also, and this matters for how you read him, the founder and sole developer of Govyn, an agent governance proxy with an open-source version and a paid cloud version, and the author of Maestro, an orchestration spec.

What to read him for

The loop that never ends. Zombie Loops: The Long-Horizon Bug Nobody Codes For (August 12, 2026) names the failure a dashboard cannot see: an agent that passes its success condition and keeps running, and billing. His three safeguards are specific enough to act on before your next long run: checkpoint before context compaction, give the agent both a checkable success condition and a hard cap, and have a separate fresh-context agent grade whether the job is done.

Why "done" needs a definition. Done Means Done (July 1, 2026) argues that free-text status updates are how false-green results get through, and proposes four fixed tokens instead. If you have ever read "task completed successfully" above work that was not, this is the piece.

Frameworks he stopped using. Why I Stopped Using Multi-Agent Frameworks (June 3, 2026) reports abandoning AutoGen, CrewAI and LangGraph after 18 months. His numbers, which are his own and unaudited: CrewAI's hierarchical mode failed non-deterministically on 34% of identical runs against 4% for the same workflow in plain code, and one silent duplicate database write ended with the line, "The framework counted that as a successful run." His summary: "Multi-agent frameworks promise composability and deliver coordination overhead."

What it cost. What 18 Months of Production AI Agents Actually Taught Me (May 6, 2026) puts self-reported figures on the table, including a peak monthly model bill of $14,200, and argues the dominant failure is context-blindness rather than hallucination.

Start here

Zombie Loops. It is the most directly useful piece for anyone about to leave an agent running overnight.

What he sells, and what that means for you

This is the sharpest disclosure on the list after Alston Antony's. Laursen's posts diagnose governance failures and conclude that an infrastructure proxy is the only enforceable approach; Govyn is that proxy, and he sells it. His orchestration posts end by introducing Maestro, which is his. He does disclose this in article footers ("I have a direct commercial interest in the proxy-based approach described here"), which is more than most vendors manage. Consulting runs through his studio, Marathon Variety, and he co-founded an AI tools company in 2026. We also could not find anyone independent citing his work, so every reliability figure above rests on his own logs. Our read: the failure taxonomy is worth your time regardless of who sells the cure; the "only enforceable approach" conclusion is a vendor's conclusion.

Not for you if

You want an independent analyst. He is a practitioner who became a vendor, and the writing is better than that phrase suggests, but it is what he is.

---

Part of The Pareto 20, twenty creators who get a solo operator most of the way on AI decisions. How we chose them. Facts above were checked against the creator's own pages on September 12, 2026.