← Back to concept explainers

Concept Fable

Authority boundaries

Conclusion first:Authority boundaries are the explicit limits on the decisions, actions, spending, data access and external commitments an Agent is allowed to make. They further constrain 'can call tools' into 'under what conditions it can call them, how much scope it can affect, whether approval is required, and whether it can make external commitments'. Without authority boundaries, an enterprise Agent turns rapid response into compliance, financial and brand risk; for Andy Ren Xu to deliver a managed service, boundaries must be part of the operational design.

Authority Boundary · Agent Operating Model

Read the story first. There is no rush to give a definition here; let the question grow on its own first.

Fable

No matter how fast the messenger runs, he cannot promise a bridge on the city lord's behalf

North Gate City had a team of messengers dedicated to relaying messages from City Hall to the various neighborhoods. In the past the errands were simple: announce road repairs, confirm rosters, chase forms. The messengers ran fast and the residents knew them well, so many small matters were handled the same day.

After the city expanded, the couriers began handling more complex requests. Merchants asked whether they could occupy a road for three days, schools asked whether they could temporarily change routes, and workshops asked whether they could use a repair fund in advance. Everyone hoped the courier would answer on the spot, because waiting at the city hall for approval was too slow.

The department head first gave the messengers a broad authorization: handle reasonable requests on your own. The first few days worked well, and the lines got shorter. But soon, one messenger agreed to let a merchant occupy the road, while another messenger agreed to let a convoy pass on the same day; someone approved a small advance payment without knowing that the same street had already been advanced three times.

The incident happened on a rainy night. To appease the dock merchants' association, a messenger verbally promised that City Hall would build a temporary bridge within ten days. The association signed freight contracts based on that promise. The commissioner only learned the next day that the budget, craftsmen, and permits didn't exist.

The director did not blame the messenger for being diligent. He laid out all the errands and found the problem was blurred boundaries: which words were merely relayed, which could be confirmed, which could change schedules, and which involved spending money, contracts, public safety and external commitments.

The new rules were written on a boundary map. Couriers could confirm information, arrange low-risk times, and issue standard forms; when exceeding an amount, affecting public roads, changing contracts, accessing sensitive archives, or committing municipal resources externally, approval from the office was required.

The boundary map also specified how records should be kept. Every reply had to state its basis, limit, and validity period. If a courier encountered a new situation, he did not need to guess what the director thought; instead, he escalated the request according to the boundary and told the other party when a formal reply could be expected.

A few months later, the people still felt the courier got things done quickly, but the city was no longer dragged into trouble by verbal promises. The commissioner said authorization is not about stuffing the lord's seal into someone else's bag, but clearly stating what can be done, how far it can go, and when it must stop.

Reveal

This story is about: authority boundaries

Authority boundaries are the explicit limits on the decisions, actions, spending, data access and external commitments an Agent is allowed to make. They further constrain 'can call tools' into 'under what conditions it can call them, how much scope it can affect, whether approval is required, and whether it can make external commitments'. Without authority boundaries, an enterprise Agent turns rapid response into compliance, financial and brand risk; for Andy Ren Xu to deliver a managed service, boundaries must be part of the operational design.

What matters is that it is not just a term, but a structural problem that repeatedly appears in real AI / Agent systems. Understanding it lets you judge when to add a model, when to change a process, and when to add governance.

Metaphor mapping

  • Messenger: an Agent that can execute tasks and communicate externally
  • Reasonable requests handled on their own: ambiguous authorization
  • Lane occupation and fleet conflict: local judgment causes system conflict
  • Ten-day bridge repair promise: Agent overreach creates external obligations
  • Boundary diagram: Authority Boundary
  • Amounts, roads, contracts, sensitive archives: common dimensions of permission boundaries
  • Basis, limits, and validity period: auditable authorization conditions
  • Escalate by boundary: boundaries do not stop work, they define when to hand it to a human

Andy Ren Xu's judgment

The practical value of this concept is that it helps you break "AI features that look smart" into deliverable, verifiable, and governable units of work.

permission boundaryapproval gateautonomy leveldelegated authority

Related distinctions

This concept is easily confused with adjacent concepts; it is recommended to continue to the comparison page.

京ICP备2026014272号