Three rings

ASMP v0.1 focuses on the machine ring: services running on a single host. The full vision has three rings of the same primitive.

Same question, wider scope

Who exists, what can they do, how do I connect, and am I allowed?

Ring	Scope	Example entries
Machine	This device	`email-daemon` on `:8787`, `director-daemon` on `:7400`
Life	Your world	Homelab nodes, personal APIs, accounts, devices across your life
Business	Your org	Internal services, vendor APIs, partner systems, compliance boundaries

The manifest shape stays the same. Rings are scope, not different protocols.

Machine ring (v0.1 — now)

What is running on this computer right now?

name: director-daemon
capabilities:
  provides: [process.supervise, email.classify, comms.search]
endpoints:
  - protocol: http
    port: 7400

Proven on production hosts with 40+ manifests and a localhost registry.

Life ring (next)

What is part of your operational world, even when you are not on one machine?

Tailscale mesh nodes
Homelab services
Personal data sources (calendar, email accounts)
Cross-device agent infrastructure

ASMP entries might declare visibility: tailnet or visibility: remote with reachability metadata. Omni (the memory pointer layer) reads ASMP to know what exists before routing retrieval.

Business ring (later)

What can this organization connect to?

Internal agent-built services
Approved vendor APIs
Partner integrations
Policy-tagged data sensitivity (high, regulated)

Knox-style approval boundaries attach to manifests. Agents discover what they may connect to, not just what exists.

How the rings compose

         Business ring
    ┌─────────────────────┐
    │  vendor APIs,       │
    │  partner systems    │
    └──────────┬──────────┘
               │
         Life ring
    ┌──────────▼──────────┐
    │  homelab, accounts, │
    │  cross-device       │
    └──────────┬──────────┘
               │
         Machine ring
    ┌──────────▼──────────┐
    │  local daemons,     │
    │  MCP servers        │
    └─────────────────────┘

Bootstrap discipline: Ring 1 must work ambiently before rings 2–3 expand. The litmus test:

A new agent session in any repo asks “what can help me with email?” and gets a real answer on turn one.

When that works, expand scope.