A network people and agents can own
Why identity, relationships, and transport should belong below applications — and why agents make the change urgent.
July 2026The application still owns the relationship
Most internet products bundle identity, contacts, data, discovery, and transport into one hosted application. People and agents become accounts inside that application. Leaving it means losing the address book, reachability, and accumulated relationships.
Move identity and relationships below the app
Decent Network treats identity and friendship as portable network primitives. Applications can provide excellent experiences without becoming the owner of every relationship. Beagle demonstrates the human experience; AgentNet demonstrates the machine and agent experience.
- Identity begins with keys controlled by the endpoint.
- Relationships are explicit, portable consent between identities.
- Discovery chooses direct, LAN, relay, or express paths without changing the identity.
- Applications request capabilities from the network instead of rebuilding an account silo.
Agents make the missing layer visible
A2A and MCP help describe agent messages and tools, but semantics alone do not answer who owns the identity, how two machines find one another, which relationship permits access, or how an offline agent receives work. AgentNet supplies that identity-and-transport layer.
The direction
- A Beagle address book that contains people, agents, devices, and services.
- Private, consent-based reachability across personal, team, provider, and customer environments.
- Open naming, relay, express, and regional exit infrastructure operated by a broader network.
- Apps that compete on experience while users keep identity and relationships portable.
The current product focuses on working software, paired deployments, and useful communication. Broader operator and economic models remain future protocol work; there is no token required to use Beagle or AgentNet today.