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

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
• non-LAN adopters can consume Universal Manifest without LAN-specific assumptions

Minimum journey coverage

• Fixture conformance (valid + expected-invalid)
• Standards artifact availability (universalmanifest.net paths)
• Resolver end-to-end (myum.net/{UMID}-style contract, headers, cache semantics)
• Non-LAN adopter proof (public profile projection)
• Optional LAN integration smoke (if LAN implementation context is available)

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)

Next

• Visual harness (quick checks): /proof/harness/
• Endpoint smoke (contract-level): /proof/smoke/
• Release gates and evidence rules: /governance/done-done/