Stub Manifests

This site includes “near-real” stub manifests to make Universal Manifest concrete for adopters.

These stubs intentionally include extra fields that are not yet standardized in the v0.1 context/schema (v0.1 allows unknown fields). Treat them as shape + intent fixtures, not final ontology.

Where to see them

• Interactive loader (site): /harness/index.html
• Raw JSON-LD (site build output): /harness/fixtures/…

Stub fixtures (v0.1)

Each link below opens the raw JSON-LD fixture (useful for copy/paste, diffing, and quick inspection).

• Venue edge (venue identity + policy + edge endpoints): /harness/fixtures/v0.1/stubs/venue-edge-manifest.jsonld
• Display device (device registration + trust metadata): /harness/fixtures/v0.1/stubs/display-device-manifest.jsonld
• Creator public capsule (safe public projection for screens): /harness/fixtures/v0.1/stubs/creator-public-capsule-manifest.jsonld
• Social profile (future “profile projection” surface): /harness/fixtures/v0.1/stubs/social-profile-manifest.jsonld
• LAN platform display (LAN-specific envelope for signage runtime): /harness/fixtures/v0.1/stubs/lan-platform-display-manifest.jsonld

What to look for (how these help adopters)

Even if you ignore every optional field, you can still gain value from:

• subject (stable identity reference)
• TTL (issuedAt / expiresAt)
• shards as a composition mechanism
• pointers as “canonical lives elsewhere” references

These stubs are designed to make it easier to implement:

• projections for different surfaces (public display vs web profile)
• local-first consumption (cache while in use, log by @id)
• forward compatibility (unknown field tolerance)

Signed fixture (v0.2 draft)

• Minimal signed manifest (JCS + Ed25519 profile): /harness/fixtures/v0.2/minimal-signed-manifest.jsonld
  • See: /spec/v02/ and /conformance/v02/

Next

• v0.1 contract: /spec/v01/
• v0.1 obligations + fixtures: /conformance/v01/