The identical sample exhibits up every time brokers transfer from toy workflows to programs with actual state. As scope will increase, weak ensures create predictable signs: overconfident actions on stale information, brittle reasoning when which means drifts, and compounding errors as soon as the agent can write again.
The repair is to deal with brokers as what they’re: programs that learn, purpose, and write in opposition to reside operational information. That pushes you into establishing ensures that almost all enterprise stacks present solely implicitly. 4 matter greater than the remaining: freshness, semantics, secure write paths and lineage.
Freshness: Cease reasoning about yesterday
Many organizations have discovered to reside with staleness: batch pipelines, duplicate lag, caches, delayed CDC (change information seize), materialized views. People compensate with judgment. Brokers compensate with confidence.
A typical manufacturing failure mode is appropriate reasoning on the flawed time slice. The agent reads stock that’s minutes behind and triggers a reorder that collides with replenishment already in flight. Or the agent sees an incident marked “resolved” in a single system whereas one other system nonetheless exhibits the rollback pending, and it proceeds with a change that ought to have waited. Name these errors what they’re: freshness bugs.