Adoption Roadmap
This page describes a practical, adopter-facing sequence for implementing Universal Manifest in any system.
It focuses on what teams need to implement and prove, independent of any single repository or internal workflow.
Adoption outcomes
Section titled “Adoption outcomes”By the end of this roadmap, an adopter should be able to:
- consume v0.1 manifests safely
- validate behavior against conformance fixtures
- plan or implement v0.2 signature verification
- operate against stable publishing and resolver contracts
Phase 1 — Implement the v0.1 baseline
Section titled “Phase 1 — Implement the v0.1 baseline”Read:
- Getting Started → Concepts
- Getting Started → Quick Start
- Specification → v0.1
Minimum outcome:
- parse required fields
- enforce TTL (
issuedAt/expiresAt) - ignore unknown fields safely
- support shards and pointers without tight coupling
Phase 2 — Prove v0.1 conformance
Section titled “Phase 2 — Prove v0.1 conformance”Read:
- Conformance → v0.1
- Getting Started → Stub Manifests
Minimum outcome:
- accept required valid fixtures
- reject required invalid fixtures
- produce repeatable PASS/FAIL evidence in your CI or release workflow
Phase 3 — Plan integrity interoperability (v0.2 draft)
Section titled “Phase 3 — Plan integrity interoperability (v0.2 draft)”Read:
- Specification → v0.2 (draft)
- Conformance → v0.2 (draft)
Minimum outcome:
- align on canonicalization/signature behavior (JCS + Ed25519)
- define verifier failure handling
- validate against signed and invalid-signature fixtures
Phase 4 — Operationalize publishing and resolution
Section titled “Phase 4 — Operationalize publishing and resolution”Read:
- Publishing → Domain Split
- Publishing → Publishing and Versioning
- Conformance → Resolver
Minimum outcome:
- consume stable versioned artifact URLs
- conform to resolver contract expectations (status codes, caching, headers)
- verify endpoint behavior in the target environment
Phase 5 — Prove cross-surface adoption
Section titled “Phase 5 — Prove cross-surface adoption”Read:
- Integrations → LAN Integration (non-normative)
- Integrations → Social/Profile Integration (non-normative)
- Verification & Proof → Journeys → Tests (proof)
Minimum outcome:
- prove at least one end-to-end implementation journey
- show that integration guidance stays non-normative and spec-aligned
Release-readiness checkpoints
Section titled “Release-readiness checkpoints”Use Governance → Done-Done as the release-readiness framework.
Public readiness claims should always be backed by auditable evidence, not narrative status.