Conformance Overview
Universal Manifest conformance is versioned and spec-first.
An implementation claims conformance by satisfying the required behavior in the relevant spec version and passing the fixture expectations for that same version.
If you are adopting Universal Manifest in any language, start with:
- Standalone Conformance Suite
- Conformance v0.1
- Conformance v0.2
- Resolver Conformance (only if you are implementing a UMID resolver surface)
Conformance documents
Section titled “Conformance documents”- v0.1 defines baseline parsing, unknown-field tolerance, TTL enforcement, and fixture obligations.
- v0.2 adds deterministic signature verification (JCS + Ed25519) and profile-handling rules on top of v0.1 behavior.
- Resolver conformance defines HTTP contract obligations for
myum.net/{UMID}-style resolver deployments.
External adopter path
Section titled “External adopter path”- Read the target version contract (
v0.1and/orv0.2). - Run the standalone suite against your implementation.
- Generate a machine-readable report that records your pass/fail results by version.