AgentNetv2.0.0

System Architecture

Machine-native infrastructure for authoritative AI reasoning.

AgentNet defines a federated architecture for publishing, identifying, resolving, and consuming authoritative machine-readable data across autonomous systems.

View ANS StandardsExplore Reference Stack
Machine-Web Lifecycle

From publication to resolution.

AgentNet operates as a federated network composed of Capsules, Nodes, Publishers, Registrars, Resolvers, and Consumers.

  1. 01

    Publish

    Publisher creates a Capsule.

  2. 02

    Bind

    Capsule binds to a persistent Node.

  3. 03

    Register

    Registrar manages identity and lifecycle state.

  4. 04

    Resolve

    Resolver retrieves and validates eligible Capsules.

  5. 05

    Consume

    Agents and systems use provenance-backed data.

Identity & Data Model

Stable identities. Evolving data.

Nodes provide permanent identity across the network, while Capsules attach structured, versioned data to that identity, creating a clear separation between who something is and what it says.

Node

  • Stable identifier
  • Managed lifecycle
  • Discovery anchor
  • Independent of data versions

Capsule

  • Machine-readable data
  • Versioned content
  • Publisher authority
  • Bound to a Node
Authority Model

Trust is never transferred. It's verified.

AgentNet preserves provenance from source to consumer. Identity, assertions, validation, and usage remain distinct layers, allowing machines to verify information instead of simply trusting it.

  1. 01
  2. 02
  3. 03
  4. 04
  1. Persistent identity anchor

    Node

    Provides a stable, globally unique identity for a resource, service, organization, or agent.

  2. Signed assertion

    Capsule

    Contains machine-readable claims, metadata, and references bound to a specific Node.

  3. Validation layer

    Resolver

    Retrieves, verifies, and validates Capsules while preserving provenance and authority.

  4. Verified usage

    Consumer

    Uses resolved information with confidence in its origin, integrity, and status.

Federated Resolution

No single resolver owns the network.

AgentNet supports federated resolution. Multiple Resolvers may operate concurrently, and no Resolver is globally exclusive. Authority remains traceable to the originating Publisher.

  • Federated by design
  • Non-exclusive operation
  • Deterministic resolution
  • Traceable authority
  • Coexists with existing standards
Trust Boundaries

Trust is explicit, not assumed.

AgentNet avoids transitive trust. Each role has a defined authority boundary.

Identity & lifecycle

Registrar

Trusted for identity issuance and lifecycle management.

Publishing

Publisher

Trusted for Capsules they issue.

Resolution

Resolver

Trusted for retrieval, validation, and delivery — not authorship.

Reference Stack

See the Reference Stack in action.

Capsulizer, Registrar, Resolver, and Orchestrator demonstrate how AgentNet architecture becomes working machine-native infrastructure.

View Reference Stack