Domain Split

Universal Manifest uses two public domains with distinct responsibilities.

This split is intentional: it keeps the standard professional and neutral, while allowing runtime lookup behavior to evolve independently.

1) Standards domain: universalmanifest.net

Purpose:

• landing page and curated docs entry
• public documentation and adoption guidance
• machine-readable discovery and agent entry points
• public tool surfaces (sandbox, harness, workbench, resolver UI)
• governance (“done done”, decisions, versioning)
• versioned, immutable spec artifacts (contexts and schemas)

Expected URL shape:

• https://universalmanifest.net/ (landing)
• https://universalmanifest.net/docs/ (curated docs entry)
• https://universalmanifest.net/for-agents/
• https://universalmanifest.net/.well-known/universal-manifest.json
• https://universalmanifest.net/llms.txt
• https://universalmanifest.net/ns/universal-manifest/v0.1/schema.jsonld
• https://universalmanifest.net/ns/universal-manifest/v0.1/schema.json

Operational model:

• static hosting/CDN
• correct Content-Type headers for JSON-LD and JSON Schema
• CORS enabled for tooling
• immutable caching on versioned paths

2) Resolver domain: myum.net

Purpose:

• runtime UMID resolution and manifest retrieval
• deterministic contract for HTTP behaviors (headers, caching, errors)
• runtime discovery metadata for machine consumers

Expected URL shape:

• https://myum.net/{UMID}
• https://myum.net/.well-known/myum-resolver.json
• https://myum.net/openapi.json

Resolver behavior (recommended baseline):

• resolve UMID deterministically
• return either:
  • 200 with manifest JSON/JSON-LD, or
  • 307 redirect to a canonical manifest URL
• return deterministic errors:
  • 404 unknown UMID
  • 410 revoked UMID (if revocation policy is supported)

3) Why this split exists

• spec governance is not a runtime service
• resolver operational posture (privacy, caching, revocation) should not leak into spec hosting
• the adoption story is cleaner (Linux Foundation style: standards site vs runtime resolver)
• agents and humans can discover the system in layers without confusing documentation ownership with runtime behavior

4) Compatibility policy (legacy namespaces)

Early artifacts may reference a localartist.network namespace.

Publishing policy:

• universalmanifest.net is canonical for standards URLs
• any previously published legacy URLs must remain resolvable as compatibility aliases

Next

• Publishing guarantees: Publishing → Versioning
• Runtime contract: Conformance → Resolver
• Agent entry path: For Agents → External Agent Onboarding