RP1 Spatial Fabric
This page captures integration guidance for 3D/spatial computing platforms and RP1-style spatial fabric use cases.
Current status
Section titled “Current status”RP1 lane materialization is complete for the current scope.
Public implementation evidence:
Boundary: normative vs non-normative
Section titled “Boundary: normative vs non-normative”- Normative contract: Specification and Conformance
- Non-normative guidance: this page
Integration intent
Section titled “Integration intent”Use Universal Manifest as the portable envelope for identity and consent while RP1 or equivalent systems provide spatial graph semantics.
Suggested pointer names
Section titled “Suggested pointer names”rp1.fabricrp1.anchorSetrp1.placeGraphrp1.sessionContext
Suggested consent keys
Section titled “Suggested consent keys”spatial.locationSharespatial.anchorSharespatial.crossWorldLinkingspatial.sessionReplay
Minimum behaviors
Section titled “Minimum behaviors”- Enforce TTL and freshness before accepting spatial linkages
- Block cross-world linking when consent is denied
- Degrade gracefully when RP1-specific shards are unknown
- Keep RP1 extensions out of core required fields