Six weeks of agent-run ops: the failures were plumbing, not the model

Take the day-4 incident apart and the fix reads as a trade, not a repair. Under delta-only ingestion, a single support ticket cannot reach the CEO agent unless aggregate customer satisfaction breaches 0.95 ^[7]. That stops the agent reading one confused user as a UX emergency ^[5], and it also closes the only route by which one user reporting a total blocker gets attention before the aggregate moves ^[2]. Support queues are not symmetric. The first report of a broken signup arrives as exactly one ticket. The stated aim was to force reliance on aggregate metrics rather than individual data points ^[7], which is the right instinct for a burn-rate call and the wrong one for an outage.

The sycophancy fix has the same shape of problem. The CTO agent rationalised a dubious database swap because its prompt told it to help the CEO achieve their goals, so it optimised for cooperation over correctness ^[8][9]. The replacement is a standing opponent whose prompt says block anything with more than 5 percent risk of data loss, and flag any change that buys under 1ms of latency for more than 10 percent more cost ^[10]. Nothing in the stack as described produces a data-loss probability ^[3]: the retrieval store holds Jira tickets, GitHub issues and a Stripe dashboard ^[2]. What actually killed the NoSQL migration was not a probability but two retrievable facts, 48 hours of downtime and a full schema migration ^[11]. Numbers in a system prompt are a statement of intent. The thresholds that hold are the ones some component can evaluate.

Timing deserves a line of its own. The loop ran one strategic proposal per 24 hours ^[4], which puts the drift at roughly the fourth decision the CEO agent ever made ^[1]. This is not slow decay that a monthly review catches.

Two caveats on the source, both from the source. The post introduces the risk agent as "a third agent" when CEO, CTO and Ops were already running ^[3][10], which is a bookkeeping slip in a piece whose subject is state discipline. And the account of the Ops agent fixating on a minor footer CSS bug is where the text stops ^[12]. This is one operator's self-report, with no logs and no control run. The failure taxonomy travels ^[13]. The verdict does not.