One tree = the whole microsite. Each screen links to its wireframe below. Turns 1–7 stay as history; superseded options are marked.
If this map is right, say "go hi-fi" — I'll build page by page in this order: Splash → Atlas → Harness → FleetOps → WorkLedger, one shared shell, dark futuristic, cinematic.
Try next: "go hi-fi — build the real pages" · "swarm view 5a + this table as one page" · "add account/token lane from tokenomics"
⚙ dark chip = refactoring team (Tomas · Robert · Petr · Franta). Plain chip = any Grouponer (Dusan, Ales…).
Try next: "make 6a the Atlas landing and go hi-fi" · "merge 6b into 3a's login flow" · "news post detail page"
Try next: "go hi-fi — build the real site" · "more swarm visual directions" · "wireframe Atlas-in-WorkLedger question round-trip"
Try next: "go hi-fi on Harness with the animated CLI" · "same deep-dive for FleetOps / WorkLedger" · "merge 4a hero with 1h cockpit"
Try next: "go hi-fi on Atlas with these screens" · "same deep-dive for Harness / FleetOps / WorkLedger" · "different SLA rules"
Try next: "go hi-fi on 2a" · "add a headline above the orbit" · "swap phases below the stats"
B&W and sketchy on purpose — the dark, futuristic, cinematic treatment comes in hi-fi. All numbers are placeholders until we pull real ones from refactor:main.
Try next: "more options for FleetOps" · "wireframe the cinematic intro sequence"