AI Agent Guardrails, Approval Workflows, and Reliable OrchestrationAI Agent Guardrails, Approval Workflows, and Reliable Orchestration
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Most AI builds break at the wiring, not the model: no retries, no log of what the model actually did, and no clear line for what the agent may do without a human.
I build that layer. My own products run on it -- an ordering platform where an AI agent handles real orders, and a coding agent that writes no file until someone approves the change.
The question worth answering first is what your agent should never decide on its own.
Post image
Kapil's avatar
For the coding agent, I'd bind approval to both the proposed diff and the file's current version. If another edit lands between review and write, does it stop and request a fresh review?
Muhammad Hasnat's avatar
Great question Kapil. Approval tied to the exact change is the core of how I build it, so nothing gets written that a human did not see first.
Ergini's avatar
refunds. anything that moves money waits for a human
Muhammad Hasnat's avatar
Agreed. Money is the clearest line there is. If it can't be undone, a human signs off.
Mojtaba's avatar
For me the line is anything irreversible or anything that costs money: refunds, deleting data, messaging customers in bulk. Below that line the agent can act, as long as every tool call is logged with its input and result, so you can replay what it actually did. The detail I'd...
Muhammad Hasnat's avatar
Well said Mojtaba. Logging every tool call with its input and result is what lets you trust the agent. You can always see exactly what it did.
Mojtaba's avatar
Exactly. The one extra thing I log is the decision itself, not just the call: why a tool was chosen or skipped, and whether a human was required. When something breaks, "what it did" plus "why it decided to" is what makes the run replayable instead of a guess. Are you storing...
Muhammad Hasnat's avatar
Agreed Mojtaba. Logging the reason behind each tool choice turns the log into something you can actually learn from.
OLANREWAJU's avatar
This is exactly right — the model is rarely the problem, the wiring is. Approve-before-any-write on the coding agent is the detail that matters. A file write looks small until it's the wrong file. My line building agentic systems is similar: anything irreversible, or anything a...
Muhammad Hasnat's avatar
Thanks Olanrewaju. Exactly, a file write looks harmless until it is the wrong file. Good to see you draw the same line.
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started