Journeys → Tests (proof)
Universal Manifest requires runnable proof for interoperability claims.
The journey model is implementation-neutral:
- define canonical adopter journeys
- map each journey to executable tests
- treat the resulting results as primary evidence for release-readiness
Why journeys
Section titled “Why journeys”Journeys prove externally observable behavior:
- consumers can parse and enforce TTL
- unknown fields don’t break compatibility
- versioned artifacts resolve over HTTPS
- UMIDs can be resolved by a conforming resolver contract
- cross-runtime adopters can consume Universal Manifest without implementation-specific assumptions
Minimum journey coverage
Section titled “Minimum journey coverage”- Fixture conformance (valid + expected-invalid)
- Standards artifact availability (
universalmanifest.netpaths) - Resolver end-to-end (
myum.net/{UMID}-style contract, headers, cache semantics) - Cross-implementation adopter proof (public profile projection)
- Optional reference implementation smoke (if reference implementation context is available)
What counts as evidence
Section titled “What counts as evidence”For any adoption or release claim, evidence should include:
- PASS/FAIL per journey
- artifact outputs for each run (logs, reports, screenshots where relevant)