Nodes, edges, contracts
Spatial organization helps reveal dependencies and relationships that a flat list can hide.
Why this view belongs here
Spatial navigation is another representation of the same knowledge space.
The original LifeStack reference separates observation from action: the Navigator is diagnostic and read-only, while execution belongs outside the observation plane. On this public site, 3D is likewise a way to inspect relationships—not a new authority surface.
See the whole while drilling down
The 3D model complements the tree, graph, lineage, evidence, chronology, and search views.
Navigation is not execution
Exploring a node changes the viewer's perspective; it does not silently grant standing or produce consequence.
Recovered source lineage
The 3D interaction was recovered from the earlier LifeStack code history.
The preserved source history contains the React + Three.js dodecahedron interaction core: face-locked clickable labels, drag rotation, wheel zoom, auto-rotation, visibility fading, and raycast hitboxes. The current site uses the live historical environment as the public surface while preserving that code lineage for later controlled migration.
Migration posture
The preserved Navigator is still served from its historical Manus host in this candidate. Independent hosting is under recovery/testing. The external assistant remains part of that historical cross-origin surface and is deferred to source recovery/migration.