Trust Levels for AI: Why Autonomy Should Depend on Proximity to the Founder

Short answer: AI autonomy should not be one setting for the whole company. It should depend on how close a person or channel is to the founder. In my own channels and with my closest circle, AI can act with high autonomy because I see the results and I can correct them fast. The further a channel is from me (the wider team, partners, customers, the public), the less the AI does alone and the more it drafts, asks and waits for human approval. Trust is earned in circles, from the center outward.

This is an opinion piece. It describes how I think about AI autonomy as a founder building an AI-native company, not a universal standard. But I believe more companies will end up somewhere close to it, because the alternatives fail in predictable ways.

Yesterday I wrote about why we built a team of AI avatars instead of one chatbot. That piece was about who the AI talks to. This one is about how much it may do alone.

The wrong question: "Should AI be autonomous?"

Most debates about AI in business are framed as a yes-or-no question. Should the AI be allowed to send emails? Should it answer customers without review? Should it change data in live systems?

Framed that way, the answer is always unsatisfying. "Yes" leads to an agent that someday sends the wrong message to the wrong person, at scale, under your name. "No" leads to an expensive drafting tool that saves less time than it costs to review.

The better question is: autonomous with whom, and where?

An AI assistant that reorganizes my personal notes overnight and an AI assistant that replies to a customer complaint are not doing the same kind of work, even if the technology is identical. The first one affects only me, and I will see the result tomorrow morning. The second one affects a person I may never meet, and the result may be out in the world before anyone in the company notices.

The variable that matters is not the task's difficulty. It is the distance between the action and the person who is accountable for it.

My rule: autonomy follows proximity

Here is the rule I use:

Why the founder? Because in a founder-led company, the founder is the final point of accountability. When an AI acts in my name, I answer for it. My proximity to the action decides how fast I can see a mistake and how cheaply I can fix it.

Three things change as you move outward from the center:

1. Visibility. Close to me, I see what the AI did, often the same day. Far from me, I may never see it.

2. Reversibility. A wrong action in my own workspace is usually easy to undo. A wrong message to a customer, a partner or the public cannot be unsent.

3. Shared context. People close to me know how I think and how my AI works. They can recognize when something looks off. Strangers cannot, and they have no reason to give the AI the benefit of the doubt.

When visibility, reversibility and shared context are high, the cost of AI mistakes is low and the value of speed is high. When they are low, the opposite is true. Trust levels are simply a way of writing that down.

The trust circles

I think about it as concentric circles. The exact boundaries will differ in every company. This is how I describe them.

Circle 1: The founder's own workspace

My notes, my calendar preparation, my research, my drafts, my internal documents. Here the AI can act with the most autonomy: organize, summarize, research, prepare, draft and even make routine changes, as long as the actions are logged and reversible.

The reason is simple. If it gets something wrong, I am the one who notices, and I am the one who pays the price. No one else is surprised.

Circle 2: The founder's closest circle

The few people who work with me every day and the AI executive seats that report directly to me. Here the AI can coordinate, prepare materials, collect information and follow up on agreed tasks. It can share drafts and summaries inside this circle. When it speaks for me in a new way, such as a new commitment, a new decision or a sensitive topic, it still asks first.

These people know my AI. They know its tone, its limits and how to flag a mistake. That shared context is what makes higher autonomy safe.

Circle 3: The wider company

Department heads, teams, technicians, office staff. Here the AI can answer questions within an approved scope, deliver routine information and prepare work. Anything that sounds like an instruction from the founder, a change in policy, a judgment about a person or anything about money goes through a human first.

The wider the audience, the more a message from "the founder's AI" is read as a message from the founder. That weight is exactly why it needs a human check.

Circle 4: Partners, vendors and the professional network

People outside the company who have a relationship with us. Here the AI drafts and the human sends. The AI can research, prepare a reply, summarize a thread and suggest next steps. It does not commit, negotiate or send under my name without approval.

Circle 5: Customers and the public

Homeowners, readers, the media, social platforms. Here the rules are the strictest. Public-facing AI, like our AI avatars, works only within a narrow, pre-approved scope: explain, guide, collect information, hand off to a person. Public content published in my name is drafted by AI under a publishing process I approved; this article is published under that standing process. Circle 5 remains the strictest: the AI does not invent new public statements or commitments on the fly.

What "more autonomy" actually means

Autonomy is not a single switch either. Inside each circle, I find it useful to separate five levels of action:

Close to the founder, more actions can move up the ladder to "act and report." Far from the founder, most actions stay at "suggest" or "prepare." Very few actions anywhere should be "act silently," and only when they are routine, reversible and logged.

The combination of circle and level gives you a simple grid. For any new AI capability, you can ask two questions: which circle does it touch, and which level do we allow there? That conversation takes minutes, and it prevents most of the bad surprises.

The things no circle unlocks

Some actions do not become autonomous no matter how close they are to the founder. In how I run the company, I treat these as locked in every circle:

• Moving money or approving payments.

• Signing or committing to anything legal or contractual.

• Decisions about people: hiring, evaluation, discipline.

• Changing live production systems without a test run, approval and a backup.

• Inventing facts or numbers. An AI that does not know says it does not know.

These limits are not about trust in the technology. They are about accountability. Even if an AI could do these things well, a human must own them.

How trust moves between levels

Trust levels should not be frozen. They should move, in both directions, based on evidence.

Trust is earned by track record. An AI capability starts at a lower level. If it performs well for a while (its drafts need few corrections, its summaries are accurate, it routes edge cases correctly), it can be promoted one step. I treat promotion as a human decision, ideally written down so the new level is clear to everyone who works with the system.

Trust is lost faster than it is earned. One serious mistake in an outer circle can send a capability back down. That is not punishment; it is calibration. The same is true for people.

Trust is specific, not general. An AI that is excellent at scheduling does not automatically earn autonomy in writing to partners. Each capability earns its own level in its own circle.

Trust is visible. Everyone close to the system should know what the AI is allowed to do. Hidden autonomy is the most dangerous kind, because no one is watching for its mistakes.

Why I think this beats the alternatives

There are three common alternatives. Each fails in its own way.

"Full autonomy everywhere." It is fast until the first public mistake. Then the company swings to the other extreme and loses the benefits it had. It also puts the founder's name on messages the founder never saw.

"Human review for everything." It feels safe, but it turns AI into a queue of drafts waiting for a tired human. The founder becomes the bottleneck, and the AI's main advantage, speed, disappears. People start approving without reading, which is worse than no review at all.

"Autonomy by task type." Many companies set rules like "AI may send emails" or "AI may not." This ignores the most important factor: who receives the email. A note to my own team and a note to a customer are not the same task.

Proximity-based trust keeps speed where mistakes are cheap and caution where mistakes are expensive. It also mirrors how good founders already delegate to people. You give your closest, most trusted colleagues more freedom, and you put more process around communication with people who do not know you. AI should follow the same logic.

The objection: "Isn't this founder-centric?"

Yes, on purpose. In a founder-led company, the founder is where accountability ends. Making AI autonomy depend on proximity to the founder is a way of keeping accountability honest.

But the founder does not have to be the only center. As a company grows, the same model can be applied around other accountable leaders: a department head can have their own circles for their own function. What should not change is the principle: autonomy grows where the accountable person can see and correct the result.

There is also a cultural benefit. When the team knows that the AI acting near the founder is the same AI that is carefully supervised in outer circles, they trust it more. Clear rules make the system predictable, and predictability is what makes people willing to work alongside AI instead of around it.

How to apply trust levels in your company

1. Draw your circles. Start from the accountable person (founder or CEO) and list who and what sits in each circle: workspace, closest circle, company, partners, public.

2. List your AI capabilities. Every place AI reads, writes, sends or changes something.

3. Assign a level to each capability in each circle. Observe, suggest, prepare, act and report, or act silently.

4. Write the "no circle unlocks" list. Money, legal, people decisions, production changes without a test, invented facts.

5. Make it visible. Publish the grid internally so everyone knows what the AI may do.

6. Review and promote. Look at the track record regularly and move capabilities up or down one step at a time.

7. Log everything. Autonomy without a log is not autonomy; it is a blind spot.

FAQ

How much autonomy should an AI assistant have in a company? It should depend on who is affected. My rule is that the closer a person or channel is to the founder or accountable leader, the more the AI can do alone. Further out, with partners, customers and the public, the AI drafts and a human approves.

What are AI trust levels? AI trust levels are a framework for deciding what AI may do in each context. They combine "circles" (how close a person or channel is to the accountable leader) with action levels: observe, suggest, prepare, act and report, or act silently.

Should AI ever send messages to customers without human review? Only within a narrow, pre-approved scope, such as answering routine questions or collecting information, and only when it identifies itself as AI and can hand off to a person. Anything new, sensitive or published in the founder's name should be approved by a human.

How does an AI earn more autonomy? Through a track record. A capability starts at a lower level, and a human promotes it one step at a time when its work needs few corrections. Serious mistakes move it back down. Trust is specific to each capability and circle.

What should AI never do on its own, regardless of trust level? Move money, sign or commit to legal agreements, make decisions about people, change live systems without testing and approval, or invent facts and numbers. Those stay with accountable humans.

Want more essays like this? Subscribe to The Operator's Edge.