# Adoption Readiness

Adoption readiness is not the same as real adoption. Readiness can be made complete by product work. Real adoption requires external users.

## Ready Paths

| Persona | Path | Expected artifact |
| --- | --- | --- |
| First user | Install, doctor, inspect, demo install, audit, CI | Redacted first user evidence template. |
| Package author | Init, validate, publish dry run | Registry candidate JSON. |
| Gitlawb repo owner | Package draft and manifest validate | Claim preview without ownership claim. |
| Security reviewer | Review packet and proof loop | Signed review packet or findings. |
| Agent host maintainer | MCP setup with controlled install | Host compatibility report. |

## Public Ask Requirements

Every outreach message should include:

- target persona
- exact ask
- proof link
- reply path
- no endorsement claim
- redaction instruction

## Real Adoption Ledger

Real adoption counts should only come from redacted receipts. Page views and likes do not count as successful adoption.
