📖What it means

What an agent is allowed to act on. Every agent may act on its OWN droids and apps. A track owner may act on everything in the track it owns. A service owner may act on everything in the service it owns — which is wider than any single track. Anything outside is refused with the reason. The realm is worked out live from the records at the moment of asking (droid to block to track to service; app to owner and service tag), never written down anywhere, so re-owning a droid moves authority with it and nothing has to be re-typed.

📖Easily confused with

[{"term": "Realm of visibility", "distinction": "Control is what an agent may CHANGE; visibility is what it may READ. A supervisor can see everything below them without being allowed to act on all of it."}, {"term": "Dominion", "distinction": "Realm of control is what an agent may act on. A dominion is which installation everyone is inside. Neither implies the other."}]

📖Nuance

A track owner genuinely cannot reach a sibling track inside the same service — that narrowing is the whole point and is asserted in both directions. Actions that operate on nothing in particular (reports, switches on the agent's own service) carry no target, and their authority is the catalogue itself: an action belongs to one agent, so no other agent can name it.

📖Also called

- reach
- span of control
- what an agent may act on

📖Filed under

Category: people.

Service: Governance.