Skip to content
Universal Manifest

RP1 Spatial Fabric

This page captures integration guidance for 3D/spatial computing platforms and RP1/MSF-style spatial fabric use cases.

RP1 Spatial Fabric Integration

Current status

Section titled “Current status”

RP1/MSF source refresh and lane deepening are complete for the current scope.

Public implementation evidence:

Primary-source grounding used in this refresh:

Boundary: normative vs non-normative

Section titled “Boundary: normative vs non-normative”
  • Normative contract: Specification and Conformance
  • Non-normative guidance: this page

What the sources confirm

Section titled “What the sources confirm”
  • A spatial fabric is multi-scope. A root scope can mount child scopes through attachment points.
  • Resource references bridge both child-scope traversal and external 3D assets.
  • Portable identity state is not the same thing as live runtime state.
  • gltf and glb assets should stay external to the manifest.
  • Freshness and revocation checks must fail closed at the integration edge.

What belongs in Universal Manifest

Section titled “What belongs in Universal Manifest”

Universal Manifest is the portable envelope for:

  • subject binding
  • consent and freshness policy
  • pointers to root/current fabric, place graph, anchor services, and attachment indexes
  • compact attachment-policy and asset-profile summaries
  • optional revocable session-context references
  • optional attachment/session freshness evidence

The RP1/MSF runtime remains responsible for:

  • live scope traversal
  • current loaded node trees
  • search and tool state
  • model/resource caches
  • live authorization on attachment follow or asset fetch

Suggested pointer names

Section titled “Suggested pointer names”
  • rp1.fabric
  • rp1.anchorSet
  • rp1.placeGraph
  • rp1.attachmentIndex
  • rp1.assetProfile
  • rp1.sessionContext
Section titled “Suggested consent keys”
  • spatial.locationShare
  • spatial.anchorShare
  • spatial.crossWorldLinking
  • spatial.sessionReplay

Suggested facet families

Section titled “Suggested facet families”
  • spatialAnchors
  • placeMembership
  • spatialFabricAttachmentPolicy
  • spatialAssetProfile

Example flow

Section titled “Example flow”

A subject arrives with a manifest that points to an Earth/root fabric, a place graph, and an attachment index for parcel-linked child scopes.

  • The manifest carries a small portable anchor set.
  • A compact attachment-policy facet says which parcel can open which child scope.
  • That attachment policy can also point to rp1.attachmentIndex as the freshness source; if that evidence is stale, traversal stops.
  • Cross-world visibility is blocked when spatial.crossWorldLinking is denied.
  • Session-context replay is blocked when the pointer is expired or revoked.
  • Asset-profile data says the consumer should fetch external gltf/glb payloads rather than expecting models inside the manifest.

Minimum behaviors

Section titled “Minimum behaviors”
  • Freshness-check attachment links before following them
  • Block child-scope traversal when attachment freshness is stale or uncertain
  • Block cross-world linking when consent is denied
  • Keep RP1/MSF extensions out of core required fields
  • Treat session-context references as optional, revocable, and non-reusable after expiry
  • Degrade gracefully when RP1/MSF-specific facets are unknown

Next

Section titled “Next”