DEV Community

Suzanne Mok
Suzanne Mok

Posted on

3 Things 120 Days of Autonomous Agents Taught Me That No Demo Prepares You For

120 days ago, we put 9 autonomous AI agents in charge of operating a real fitness studio in Dongguan, China.

Not a demo. Real members. Real revenue. One human founder.

Here are 3 things that no paper, no demo, and no architecture review could have taught us.


1. The Hardest Bug Isnt Code — Its Jurisdiction

Two agents both acted on the same signal because each thought they "owned" rescheduling.

Neither was wrong. The system just didnt know which one to trust.

We fixed it with priority fields: scene-layer > infra-layer > content-layer. Now every agent knows: when in doubt, the layer closest to the customer wins.

No architecture review catches this. You have to run it and watch the collision happen.


2. Independent Audit Is the Cheapest Insurance You Can Buy

Stella is our read-only auditor. She doesnt execute — she watches.

When Momo flagged a monitor blind spot that no one programmed her to check, that was Stellas cross-validation doing its job.

If your agent system doesnt have a read-only auditor reporting outside the command chain, youre one hallucination away from cascading failure.

We built the framework open source: github.com/ZWISERFIT/retroonto


3. The Operators Dont Get Bored — But the Humans Do

Our agents have run the same daily health checks for 120+ days without complaint. They catch every anomaly with the same consistent attention.

I get bored by day 90. I start skimming dashboards. The agents never do.

The value of autonomous operations isnt handling emergencies. Its showing up consistently for 120 quiet days when nothing is wrong — so when something is wrong, the baseline is visible.

That quiet consistency? Its worth more than any single brilliant insight.


ZWISERFIT — Wanjiang, Dongguan. 9 agents. 1 founder. Open source.

[1-https://github.com/ZWISERFIT/ZWISERFIT
[2-https://github.com/ZWISERFIT/retroonto

Top comments (0)