Who's who

The protocol name is ASMP. The idea is simpler:

A who’s who of what’s running, what’s in your world, and what you’re allowed to connect to.

One primitive, three rings

Ring	Scope	Example entries
Machine	This device	email on :8787, director-daemon on :7400
Life	Your world across devices	Homelab, Tailscale mesh, personal accounts
Business	What the org can connect to	Internal APIs, vendor systems, partner services

Same manifest shape. Wider scope. Policy tightens as you move outward.

        Business — vendor APIs, compliance tags
              │
        Life — homelab, cross-device, accounts
              │
        Machine — local daemons, MCP servers  ← v0.1

What each ring answers

Not “what agents can chat with” (A2A). Not “what tools can I call” (MCP).

Who exists, what can they do, how do I reach them, who owns them, am I allowed?

Layer	Machine	Life	Business
ASMP	What’s registered	What’s reachable on mesh	What’s approved to connect
Omni	Where logs/data live	Cross-system memory pointers	Org knowledge locations
Knox	Local access	Privacy boundaries	Compliance gates

See Eidos stack.

v0.1 is the machine ring

Proven on production hosts:

• 46 manifests in ~/.asmp/services/
• Registry on localhost:7700
• MCP discovery (service_find, service_list)

Rings 2–3 are documented direction — not shipped requirements.

Job to be done (not time savings)

Wrong pitch: “Save 15 minutes per plist.”

Right pitch:

“I built a service. Other agents can find and use it without custom wrappers.”

When a new session asks “what handles email?” and gets a real answer — the who’s who is working.

For adopters

Alex runs Ollama locally, three agent projects, can’t get Agent A to use Agent B’s code service without hand-wiring. Alex needs:

1. Write one manifest when building a service
2. Global discovery in every session
3. Query by capability, not port

That is the first external persona. Everything in v0.1 serves Alex on one machine.