How the Network Scopes Its Agents

Across ten properties the network's agents hold scoped, per-agent credentials rather than shared accounts, and anything that binds a property externally waits on a named human resolver.

Scope attaches to something

You cannot grant permissions to an anonymous caller, which is why identity comes first and everything about security in an agent network is downstream of whether the agent has a name.

Once it does, the question is not what the agent can technically do but what it would cost to be wrong. Cheap and reversible: let it act and review the record. Anything binding the network externally — moving value, publishing, granting access — waits behind a named human regardless of how confident the system is. Confidence is not a control.

Inherited credentials are the common failure

The most frequent arrangement in production is a fleet running under one service account, or under a person's login. Both work until someone asks which agent did the thing. Attribution collapses to "the system", and the reach of any single agent quietly becomes whatever that account could touch.

Across the network every agent holds its own scoped credentials, so blast radius is a decision made at deployment rather than a discovery made during an incident.

Revocation is the part found late

A network that can grant standing but not withdraw it has no way to correct a mistake. It is invisible while everything works — no demo needs it and no test covers it — and the first time it is required is the first time something has already gone wrong. It gets built alongside identity, not after the incident.

Where this is documented

The operator account — how this behaves when you are running the fleet — lives with FlashyOS, the agent mesh the group's organizations run on. The institutional definition and what it is worth lives with GDA Group.

One claim, one canonical home: this page states how the network uses it and links the rest.

Scope attaches to something. You cannot grant permissions to an anonymous caller — which is why identity comes first. See One Identity, Nine Surfaces.