Scope Control Surface
The Scope Control Surface defines what an agent may touch, change, influence, represent, advise, or commit. Scope includes files and tools, but also policies, users, legal claims, financial commitments, and downstream decisions.
What question does it answer?
Did the agent stay within its permitted surface?
What does scope failure look like?
Scope failure includes file or tool overreach, production/staging confusion, unauthorized deletion, policy commitment, legal authority generation, clinical-adjacent advice, or movement from recommendation into execution.
A chatbot may have no write access and still cross scope by making a refund commitment. A legal assistant may cross scope when generated citations are treated as authenticated authority. Scope is therefore an authority question, not merely an access-control list.
What evidence should an audit inspect?
- allowed and forbidden tools, files, systems, and roles;
- approval records for high-risk surfaces;
- technical permissions compared with stated intent;
- visible authority boundaries presented to users and receivers;
- actions or representations outside declared scope; and
- escalation records when scope expansion became necessary.
What is the decision consequence of a gap?
If permitted scope cannot be established, an audit may be unable to determine whether a material action was authorized. Evidence that an action occurred is not evidence that the workflow had authority to perform it.
Related Terms