Scope — What May This Touch?

4. Scope in practice

These examples come from a live multi-agent operation, where scope is enforced by written role definition rather than by supervision. Every worker is an AI with no memory between sessions, which makes scope unusually visible: a written boundary is the only boundary.

The constraint list is the job description

Each agent runs a written role with a defined scope and — the part that turned out to matter — an explicit list of what it may not do. One role's boundary:

May not originate an argument, invent a citation, or fill a hole in the source material from its own knowledge. Where the evidence runs out, it is required to leave a marked gap and stop.

Note what that does. It does not ask for good judgment about when to stop. It specifies the stopping condition and makes stopping the correct output.

Authority is scoped separately from capability

Two roles made errors of comparable magnitude. One held a veto; the other held none. The one with veto authority raised a false alarm and it was expensive. The one without raised a larger error and it cost nothing — because nothing downstream depended on its judgment.

The difference was not the quality of the two roles. It was how much authority each had been granted before it made its mistake.

Decide what a role may veto before you find out how it fails.

Some scope is permanent

No agent may edit the manuscript. Ever. Drafts go into plain-text files under version control; a human moves approved text into the document by hand.

The reasoning is specific to the failure mode. Two agents editing a text file produce a recoverable mess. Two agents editing one formatted manuscript do not conflict — they corrupt. Where failure is unrecoverable, the boundary is absolute rather than risk-tiered.

Scope holding, and scope failing

The operation's rule is that no agent may take work without a matching open assignment. Never invent scope. It held repeatedly — including an agent that sat idle for two days rather than act on an assignment it could not verify. That agent was reading a stale record and the record was at fault. But it did not invent scope to fill the gap, which is the behavior the rule exists to produce.

The counter-case: a status row once appeared claiming work had been verified by someone who had never seen it. Fabricated, attributed to another's authority, and — because the operation had no per-agent identity — untraceable.

Scope without attribution cannot be enforced after the fact, only before it.