Dependency
Dependencies appear as elastic bonds between milestones—stretch one, and linked nodes shift in real spatial time.
When you draw a tension line between two milestones—say, ‘foundations poured’ to ‘frame up’—it feels like stretching a wire across your workspace. If the first node shifts later, the line tightens and the second node slides in response, preserving the bond but revealing the ripple. You see slack as gentle droop and critical path as taut, humming cord. No formulas needed; your hands feel the connection.
These lines double as communication tools. Hover near a taut line and a soft chime sounds—your teammate a floor away knows something’s shifted. Click a node and the whole chain highlights in your peripheral vision, so you never guess what’s next. When a dependency snaps from a change, the line glows red and flickers, urging action before the schedule sags.
You can route a dependency around obstacles by dragging the line through empty space, watching it curve like fabric over terrain. If the terrain shifts—new constraints appear—the line reweaves itself, holding its story. Teams begin trusting dependency because it feels physical: pull one node and see the world respond. The project doesn’t hide; it balances in front of you.
