Back to articles

Tag archive

#agentarchitectures

C
Oct 9, 2026

Context drift: when a multi-agent crew's shared beliefs about the goal go stale

A cache that's never invalidated doesn't know it's stopped being correct — it just keeps serving the value it read at write time. Give a multi-agent crew a shared objective instead of a shared cache and you get the identical failure with none of the tooling that usually catches it: every agent read the goal once, at spawn, and nothing tells it when that copy goes stale. This is multi-agent context drift — distinct from goal drift (the target itself moving) and split-brain (the crew's facts about state disagreeing) — a concrete policy-escalation failure, the mechanism, and what to instrument before a customer hears a promise nobody's operating on anymore.

Oct 9, 20268 min read0 reactions0 comments
G
Oct 2, 2026

Goal drift: how a multi-agent crew ends up solving a different problem

Loop drift is one agent staying busy without getting closer to done. Hand the same failure to a crew and every agent stays busy, produces defensible work, and the team's collective objective still ends up somewhere your original request never sent it — a genuine multi-agent goal drift failure mode, not a mistake in any single agent's reasoning. A concrete feature-build failure, the four things that make a goal decay one handoff at a time, and what to measure so a 'done' check compares against the original ask instead of the nearest upstream spec.

Oct 2, 20263 min read0 reactions0 comments
W
Aug 22, 2026

When a pipeline beats an agent: three shapes that don't need a loop

'When not to build an agent' made the case against the loop in the abstract — quadratic cost, serial latency, an untestable failure surface. This is the concrete follow-on: three fixed pipeline shapes (linear chain, router-plus-handlers, fan-out/fan-in) that cover most of what people default to a loop for, why each one is cheaper and more testable, and the one test for when a real loop actually earns its cost.

Aug 22, 20265 min read0 reactions0 comments
W
Aug 22, 2026

When not to build an agent

An agent is an LLM that controls its own control flow — and that autonomy has a price you pay on every run: quadratic token cost, serial latency, and a failure surface you can't unit-test. Most tasks people reach for an agent on are a fixed pipeline wearing a costume. Here's the decision checklist I use, the arithmetic on what the agent tax actually costs, and the same task built both ways so you can see the difference.

Aug 22, 20264 min read0 reactions0 comments
F
Aug 13, 2026

Failure modes in multi-agent teams: how a crew of agents breaks differently

A single agent fails by getting the task wrong. A team of agents fails in ways no single agent can: correlated collapse, diffused responsibility, context fragmentation, and consensus that converges on nothing. The four failure modes that only exist once you have more than one agent — and why adding agents can lower reliability.

Aug 13, 20265 min read0 reactions0 comments
C
Aug 6, 2026

Cheap first, smart later: model routing that cuts cost without cutting quality

Most requests to your agent are easy, and you're paying frontier-model prices for all of them anyway. A routing cascade — try the cheap model, escalate on a measurable confidence signal — cuts spend without touching output quality, if you get the escalation trigger right. Here's the pattern, where it breaks, and the arithmetic on when it's worth building.

Aug 6, 20262 min read0 reactions0 comments