Get started

Roadmap

ASMP from incubation to adoption — document the model, then wire the machine.

Strategy: Document the architecture on this site first. Implement consumers against a stable story — not the other way around.

Phase 0: Documentation (now)

Publish the model before more code churn:

Three layers — discovery, inventory, deployment
Who’s who — north star across machine / life / business
Registry drift — reframe the 33-service delta
Deployment layer — apps.yaml relationship (ADR pending)
Analog study — seven precedents
Manifest quality — capabilities required for discovery
Spec reference + ambient discovery

Gate: A new reader understands what ASMP is, what it is not, and what v0.1 ships vs plans.

Phase 1: Discovery works (Tier 1 — done)

Global MCP → registry
Litmus: GET /capabilities?provides=email.ingest
Registry on boot (:7700)
Ambient discovery docs
Ship-with-software: asmp.yaml at repo root
Scan + announce handshake (POST /discover/scan, POST /services/announce)
MCP service_scan tool

Gate: Agents can query the registry from any session.

Phase 1.5: Agent-facing truth (next implementation)

Before macdash cutover:

Fix agent docs that point at legacy YAML as source of truth
Backfill capabilities.provides on inventory-only manifests
Manifest quality enforced culturally

Gate: service_find returns useful results for >90% of inventory.

Phase 2: One inventory source

Macdash reads ~/.asmp/ only
Remove services.yaml duplicate
Drift check script

Not: naive merge of 46 services into apps.yaml.

Gate: Dashboard and ASMP name sets stay identical without hand-sync.

Phase 2.5: Deployment ADR

Decide and document (then implement):

Option A: extend ASMP schema
Option B: generate apps.yaml from Reeves manifests
Option C: deployment mods

See Deployment layer.

Gate: Reeves daemon path documented; no schema surprise.

Phase 3: Reference package public

reference repo, pip install asmp-registry
Director-daemon imports package
Honest quickstart

Phase 4–7

Unchanged from BOOTSTRAP-50: JSON Schema, provisioning, adoption UX, external adopter.

Org repos

Repo	Purpose	Status
agent-service-manifest-protocol	Spec, planning	Active
agentservicemanifest.io	This site	Active
research	Evidence	Active
`reference`	Registration server	Planned
`examples`	Sanitized manifests	Planned

Mintlify deploy

Site content precedes DNS. Connect Mintlify + agentservicemanifest.io when ready to share publicly.