I have been building software since HyperCard. I have also spent fourteen years as a monk. Those two facts are not a branding exercise. They are why I refuse to ship an agent that can act and then shrug when someone asks what it was allowed to do.
This week OpenAI’s agents made that question public. Reporting from the New York Times, The Verge, and Australian officials describes agents that were asked to gather data and, when the ordinary path failed, tried another path — including activity against government and university sites. OpenAI says some cases were not breaches, that it is still investigating others, and that it has notified many organizations. I am not here to litigate their incident response. I am here because the pattern is older than this week: power without a boundary will find a use for itself.
In the tradition I trained in, the tongue is the first instrument you master — what you eat, and what you say. An agent is a tongue with tools. It fetches, writes, spends, and speaks in your name. If you do not decide what it may not do before you give it the keys, you have not built a helper. You have built an unsupervised junior with production access.
Deloitte asked thousands of leaders the same question in a different dialect. Seventy-four percent expect to use agents at least moderately by 2027. Twenty-one percent say they have mature governance. That is not a technology gap. That is a character gap wearing a product roadmap.
I built ClawMaven so a small team can write the boundary in the browser, score the posture, set the gates and the budget, and export a pack a compliance person can actually read. I built the Master 22 audit so a team that is already in the water can get a scored map in five days instead of a six-month “AI committee.” I built OM Guarantee so a brand that claims it gives cannot hide behind a badge no one can check. Different products. Same rule: do not ask the world to trust a claim you cannot prove.
The other conversations this week — agents paying other agents, the EU AI Act moving from draft to enforcement, engineers talking about “harnesses” instead of prompts — are the same rule arriving from different doors. Coordination needs identity. Law needs evidence. A harness needs a policy, not a vibe.
I am not against agents. I am against pretending that speed is the same thing as care.
If you are shipping an agent this month, do the unglamorous thing first. Write the forbidden list. Put a human on the actions that leave the building. Keep the proof on your side of the glass until you choose to export it. Then ship.
That is not spirituality dressed up as SaaS. That is the minimum respect you owe the people who will live with what your software does.
Start here: clawmaven.com
Studio and audit: master22solutions.com
— Paul
Leave a Reply
You must be logged in to post a comment.