How to explore it
The graph is laid out as nine lane clusters floating in one volume — Lane A (can-do) verdicts burn green, the 220 dream verdicts sit in violet, and everything waiting on you, a person, money, or a send is in the warm colours. A verdict's size is how much other work leans on it: references pointing at it, plus the verdicts it runs before. The biggest node in the room is the one the most work waits on.
| Control | Quest (in VR) | Desktop / phone |
|---|---|---|
| Move | Left thumbstick — fly where you look | Drag to orbit, scroll to zoom, arrow pad on phones |
| Turn / climb | Right thumbstick — snap-turn sideways, climb & sink vertically | Drag |
| Select | Point a controller laser at a node, pull the trigger | Click / tap a node |
| Fly to selection | Press A (right controller) | “Fly to it” in the detail card |
| Info panel | Panel rides at the lower right of your view; B hides / shows it | Detail card, top right |
| Exit | Menu button on the left controller | — |
What the edges honestly are
- References (67, amber) — one verdict's text explicitly points at another. These are the only true dependencies in the graph.
- Precedes (576, teal) — ordering edges from the thread-map rebuild: this verdict runs before that one.
- Similar to (2,270, faint) — topic similarity from the Mycelium index. It explains why nodes sit near each other. It is not a dependency and never constrains order.
Behind these 1,152 verdict nodes sit 26,869 chunk nodes — 28,021 nodes and 79,370 edges in graph.db. This page draws the verdict-to-verdict subgraph (2,913 edges), exported Nov 21, 2026, with the Nov 22 triage lanes. Standing rule: no edge without observed evidence — the graph never invents a dependency.