# Adoption roadmap
Targets, not forecasts or completed adoption claims.

| Period | Target | Evidence |
| --- | --- | --- |
| Days 1–14 | Five consumer and five service interviews | At least three consumer teams want to pilot the same solution |
| Days 15–30 | Initial draft, validator, service, adapter, and failure harness | Verified recovery of a committed write with a lost response |
| Days 31–60 | Three to five pilots and a separately authored client | Independent code passes the same behavioral tests |
| Days 61–90 | Aim for ten active service integrations and two independent consuming apps | Repeat use and measured value over current workflows |
| Months 4–6 | Outside maintainers, stable compatibility rules, governance review | Sustained contributions and operational experience |
| Later | Decide 1.0 and suitable neutral governance | Independent interoperability; no unresolved material issues |

The starter implementation is available. Interview, pilot, production adoption, neutral-governance admission, and standardization targets remain open.

Track active consumer applications, services actually used by them, verified task outcomes, duplicates, false success reports, unresolved results, latency and calls under real workloads, integration effort, and maintenance cost. File counts and stars are secondary.

Do not promise universal agent support, AI search ranking gains, automatic certification, or exactly-once effects.