AHSAN RIAZ

GUIDE

AI agent governance

An agent that can read files, browse, and act in real systems needs the same care as a new hire with access. Governance is the difference between leverage and an incident.

Last updated October 2026.

Most agent projects fail in one of two ways: the agent is given too much access and does something it should not, or it is given so little that it is not useful. Good governance is finding the line on purpose, per task, before it runs in production.

Scoped access

An agent should reach the folders, accounts, and systems it needs and nothing else. Start narrow and widen only when a task demands it.

Approval boundaries

Anything that sends, spends, or deletes goes through a person. Everything else can run, as long as it is reversible.

Audit trail

Keep a record of what the agent did, with what input, and what it changed. Without it you cannot debug or trust the system.

Sandboxing

Run experimental or high-risk work in an isolated environment so a mistake stays contained.

Cost controls

Agentic tasks use more capacity than chat. Cap usage, choose cheaper models for simple steps, and route hard work to stronger ones.

Testing

Test against real cases before launch, including the awkward ones. Keep a small evaluation set so quality does not drift silently.

THE PRINCIPLE

AI where it helps, rules where they make sense, a person where it matters

Not every step should be agentic. Predictable steps belong in deterministic rules because they always produce the same result. Judgment and unstructured input are where a model earns its place. Anything high-impact keeps a person in the loop. The mixing is the design work, and it is where most of the value sits.

CHECKLIST

Before an agent touches real work

Want an agent you can trust with real work?

Show me the task and what it touches. I will design the access, the approvals, and the audit trail.