Horizon
Everything dated on APAC Launch, laid out across the season — the dates people volunteered, the reviews on the calendar, the reminders you chose. A date here is a fact to plan around, not a countdown that judges you.
March
Mar 31
your clock
Your date on APAC Launch
The date you authored. Passed with 4 asks still open — that's a fact, not a failure; the ones that landed after are on the record too.
April
Apr 2
on condition
Data migration — committed
Committed by Priya T., on G. Tan's condition (only if Platform v2 lands).
Apr 15
chosen
FY27 Headcount — your reminder
A reminder you chose for a different initiative. One tap turns it off; it never repeats.
May
May
broke
Data migration — moved to May
Platform v2 slipped; the condition broke exactly as written, so the work carries to May. To move the date on the record, open a new round.
June
Jun 30
scheduled
Q2 review
The plan's scheduled revisit. Everything committed comes up here — held, changed, broke, or checked — on the calendar, not on demand.
Nothing on this horizon decays or pressures. A date that's passed sits quietly on the record; there's no red, no "overdue", no odds on what lands. It's the season as it is — for planning, never for judging.
OpenWho else sees a horizon? This is your initiative's horizon. Whether leaders get one is still open (spec DP list) — the recommendation, on the symmetry law, is that a leader sees only their own-record horizon, never a per-person read of anyone else's. Rendered here on that assumption.