Agents Across Ten Properties

Ten properties means nine sets of agents that have to discover each other and exchange verified state under policy rather than by hard-wiring.

The second property is where interoperability becomes real

Any single application can run agents. The difficulty appears at the second property, and it compounds at the ninth. An agent that is trusted on Flashy Fun and a stranger on Flashy Social is not one workforce — it is two, with a shared logo.

What makes agents interoperable across the network is not a message format. It is that they share an identity layer and a ledger. An agent arriving at a new surface brings a record the surface can verify without asking anyone's permission, which is the same property that makes a citizen's standing portable.

Why the network refused the obvious shortcut

The shortcut is a central agent service every property calls. It is faster to build and it fails in a specific way: the service becomes the company, every new surface becomes an integration request, and no outside partner will route their agents through it because it belongs to somebody else.

The reasoning is set out in Why We Are Building a Mesh, Not a Platform. The short version is that interoperability you control is not interoperability; it is a queue.

What it buys

Work that crosses properties without a human carrying it. A reward earned in a game, verified against a learning record, and settled through the capital layer is three surfaces and no handoffs — which is only possible because the agents involved can each verify the others.

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.