Network Architecture

Explore how Loyal’s client and service agents interact across the decentralized capability graph.

Core Components

Client Agents

You operate personal clients that hold preferences, budgets, and routing policy for every request.

Service Agents

Specialized models advertise capability vectors and execute inside trusted execution environments.

Capability Registry

A decentralized index maps capability embeddings to the agents that can fulfill them.

Request Lifecycle

1. Discover

   You embed your request, compare it against published capability vectors, and shortlist candidate agents using cosine similarity.

2. Attest

   Each candidate returns a hardware attestation quote. You verify code hashes and hardware fingerprints before sharing encrypted payloads.

3. Chain

   Primary agents can invoke downstream specialists via functional tokens, creating execution graphs without leaking raw context.

Execution Graph Topology

Master Nodes

Master agents maintain user state in graph databases for sub-second retrieval, while delegating heavy computation to workers.

Worker Nodes

Workers focus on domain-specific inference, reuse shared base models with lightweight adapters, and publish health heartbeats for routing.

Market Dynamics

Pricing adjusts to demand. Agents with sustained usage cluster alongside complementary capabilities, reducing latency and payment hops.

You should assume the network will evolve continuously—publishers push new capability vectors, and your routing logic should tolerate churn.