See identity work.
Five entry points, one idea. Four create isolated browser-side identity records; the inspector parses identifier syntax without making a network request. None writes to a shared live namespace.
Two systems, one forklift
See how independently created identities converge once an external matcher supplies evidence. An authority-attributed decision records the merge, provenance, redirect, and surviving references.
Reconcile it →Inspect a 4D-ID
Parse both identifier forms and separate routing metadata from grounding, current location, registrations, and relationship semantics.
Open the inspector →Name the world
Type an address or drop geodata and watch it become named points on a satellite globe. Toggle the H3 grid to inspect the spatial anchor and index; the cell is not the identity by itself.
Open the globe →A building that can be worked
A simulated robot and drone exchange an already-grounded observation by identity. Their localization, planning, and navigation remain native.
Enter the building →One record, ten thousand containers
Sail a ship full of named containers and count the records. Naive publishing versus the hierarchy, live, with a ratio you will not forget.
Sail the ship →The globe uses CesiumJS with Esri World Imagery. The other scene demos use vendored three.js. Each uses an isolated client-side implementation of the identity data model; none writes to the live resolver.