Posts tagged Cap Theorem — AI × software engineering, made practical.
The 'flaky' bug where Agent B redoes work Agent A already fixed isn't a timing race at all — it's a consistency choice your context store made for you without asking, and naming it changes everything you reach for next.
A vanishing task flag in a two-agent system isn't a merge bug — it's Brewer's CAP theorem showing up uninvited, and your orchestration framework already picked a side without asking you.
CAP only kicks in during the rare network partition — PACELC is the quieter, un-diagrammed trade-off charging your agent stack's latency budget on every single request, partition or not.
That double-booking bug you filed under "LLM hallucination" was actually your orchestrator making an unwritten CAP tradeoff — here's how to catch it before the next incident does.
A network hiccup forces every distributed system — including the fleet of LLM calls hiding behind a single "agent" — into a choice between a fast wrong answer and a slow right one, and most teams never notice they made it.