Skip to main content
The dispatch
Issue #14 2026-05-24 Sundays only

The day we shipped Phase 2 to a 7-figure store.

Brevard flipped Phase 2 on a Wednesday at 14:00 UTC. The first live decision_log row landed at 14:02. The CFO Slack message landed at 14:11. Here's what we learned.

At 14:00 UTC on a Wednesday, a wellness brand doing seven figures a year flipped from dry-run to live. Two minutes later, the first real decision_log row landed. Nine minutes after that, the CFO sent a Slack message. This is the story of those eleven minutes, because they're more instructive than any demo.

The flip itself was anticlimactic — which was the point. Two weeks of dry-run meant the team had already read every kind of row the agent would write. The live rows looked exactly like the dry-run rows, just with real writes behind them.

The CFO message

At 14:11 the CFO wrote, simply: 'I can see everything.' Not 'is this safe?' — that question had been answered by the audit plane during dry-run. The live moment turned an abstract trust into a concrete one: every action a row, every row reversible, the kill switch one click away.

The flip to live is supposed to be boring. If it's exciting, you skipped the two weeks that make it boring.

The lesson we keep relearning: dry-run earns understanding, live earns trust, and you can't skip the first to get the second.

// three links we sent

  • Shopify's latest Admin API changelogshopify.dev
  • A paper on calibration under distribution shiftarXiv
  • A competitor's surprisingly honest pricing pagearound the web

// one ship

decision_log gains parent_id for cycle ancestry

You can now trace any row back to the cycle that produced it.

See the changelog

// the dispatch

Get this Sunday's issue.

Subscribe and the next dispatch lands at 09:00 local this Sunday. Operator essay, three ecosystem links, ship of the week. That's it.

Sundays only · One-click unsubscribe · No tracking pixels