How APAC Launch is coming together across six teams — every mark is the residue of a real act: an answer given, a question routed, a check-in kept. The map notices; you decide. Your view — leadership sees team-level aggregates, never these names.
sent Aug 1 · day 12 of 42 · window closes Sep 12 · moved 2h 14m ago
11
Questions open
Waiting on
11 answers across 6 teams · oldest open 9 days
17
Committed
Held so far
17 commitments · 3 checked this week — all held
3
Conditions
Yes, if
Each one is one object — a single check-in reaches every place it binds
2
Changed
Answers changed
Staged for Resolve — nothing downstream sees them until you take them there
4
Branches
Asked their own team
4 leads answered by asking their own team · 1 private — lead, state, age visible
6
Land after Sep 12
Volunteered dates
6 answers arrive after your window — their dates, added up. No odds, ever.
today · day 12 of 42
Hover a trace — it flows at that act's real pace. Retrospective, on demand — never a live pulse.Hover a relay — the questions it coordinates appear.Click a branch — what's inside stays theirs.
AnswersCommittedCondition — yes, ifChanged
TimingDeferred — lands on a named dayOpen questionBroke — a check-in said so
CoordinationRelay — coordinates questions across teamsBranch — a lead asked their own team
Structure the map noticedBottleneck · Loop · UnownedTrace — a real routing act, nothing invented