UM in the RP1 Spatial Fabric

You walk into a spatial fabric. Your browser has been holding your manifest since you signed in this morning, so there is nothing to scan and no form to fill. The fabric asks for proof over RMAP, your browser presents the manifest once, and the session stays open until the manifest expires.

The fabric checks the signature, confirms it has not expired, sees that a trusted provider vouched you are a real person, and lets you in.

Three services light up around you, and each one gets only its slice. The map service sees where you are. A retail kiosk by the door sees your display name and position, nothing more. A bar wants to know you are over 18, so it gets a yes to that one question and never sees your birthday. One envelope, three different views.

The browser brokered every handoff, no service saw a field outside its contract, and each decision left a signed line on the receipt.

Touches identity, entity type, RMAP service credentials, consent, zero-knowledge age proof, and spatial addressing, each step logged to the receipt.

A technician puts on AR glasses to start a shift on a big plant floor. Their manifest already carries the things the job depends on: signed safety certifications, an equipment-access credential for the gear and zones they are cleared for, the plant's own policy, and a list of which sensors stay on and which stay off. Eye tracking and the camera are off, and the plant policy keeps them off.

At the door the fabric checks all of that, then switches on the two services the plant requires: safety alerts and emergency evacuation.

At a hydraulic press, the monitoring service gets just enough to confirm the technician is cleared, and full telemetry appears in the glasses. That service writes only to its own corner of the scene tree and cannot reach into the safety service's branch.

A training guide walks them through a pump swap. Before it runs, the fabric checks the module the same way an app store checks a signed app: right fingerprint, real publisher, not revoked.

Then a forklift rolls into the next aisle. The safety service needs to warn the navigation service to reroute foot traffic. That message only goes through because the plant pre-approved exactly that channel for exactly that kind of alert. A warning lights up in the glasses, and because safety is mandatory here, the technician cannot wave it away.

When the shift ends, the manifest expires, every service drops its access, and the whole run is sealed into a signed end-of-shift record.

Touches identity, equipment-access credentials, consent, the content-trust check, scene-tree write permissions, and service-to-service messaging.

A new fabric is coming together, and a vendor offers a predictive-maintenance module. The browser will not run it on trust. First it checks three things: the file matches the fingerprint the publisher signed, the publisher is who they claim to be and has not been revoked, and their signature on the code is real.

All three pass. The module runs, but only with the access its publisher actually declared, writing to its own branch of the scene and nowhere else.

A second module shows up from a publisher the fabric revoked after the manifest was issued. The browser blocks it cold. The block and the reason go into the audit log, and the code never reaches the runtime.

Touches the content-trust check, the package and service catalog, and scene-tree write permissions, with a signed receipt either way.