Eidos stack

ASMP is a coordination primitive in the Eidos agent infrastructure map — the layer that answers who exists and what can I connect to?

The missing node

The Eidos operating map shows Telos, the Trilogy (Research, Governor, Docket), Praxis, and tools like Lever, Felix, Foreman, Knox, Omni, and Pavo.

ASMP is the node the map is missing: host-level service declaration and discovery.

How layers relate

Telos (why — identity, direction)
    │
Trilogy: Research · Governor · Docket
    │
Praxis (learn from execution)
    │
┌───┴───────────────────────────────────┐
│  ASMP          Omni          Knox      │
│  WHO exists    WHERE data    ALLOWED?  │
│  WHAT they do  lives                   │
│  HOW to connect                        │
└───┬───────────────────────────────────┘
    │
Marketplace / Private Stores (installable tools)
    │
launchd / systemd (execution)

Layer	Question
ASMP	What services run? What capabilities do they expose?
Omni	Where is the evidence? What’s indexed, blocked, or manual-only?
Knox	Is this agent allowed to access it?
Felix	Build new agents and plugin bundles
Foreman	Delegate work to worker agents
Marketplace	Distribute public plugins

Three rings, one map

Ring	ASMP	Omni	Knox
Machine	Local daemons, MCP servers	Log paths, data stores	Local access policy
Life	Homelab, personal APIs	Cross-system memory pointers	Privacy boundaries
Business	Org services, vendor APIs	Org knowledge locations	Compliance gates

One line

ASMP is how agents declare what’s running. Omni is how they find the evidence. Knox is whether they’re allowed.

Together they make the operating map machine-readable.