Priority is not a number P1–P4 that follows you all day. It is a moment: how much uninterrupted time you actually have before the next meeting.
WAH treats time as part of the graph. Change the window — the next move changes. That is the whole point of the Context section on the homepage: the right task depends on the moment.
The same project, two windows
“I have 90 minutes. What can I finish?” → Review customer interview notes — 35 min · Fits your window · Unblocks the product brief · No dependency waiting on you.
“What should I work on before the 2 PM standup?” → Fix authentication — 35 min · Blocks onboarding and your call is approaching. Same effort, different pressure. The recommendation switches because the graph now includes the calendar.
Context ids we ship with
lib/wah.ts encodes six contexts: 45 min available, 20 min available, deep work, before a meeting, waiting on teammate, high energy. Each hints the filter: a real block vs. a short window vs. something you can finish before the call.
This is not a setting you tune once. It is a question you ask repeatedly: What can I finish in 45 minutes? What can I postpone until tomorrow? The demo in /app lets you click the same five questions and watch the card trade Places — interview notes one moment, roadmap → tomorrow the next.
Distribution angle
The most shareable screenshot of WAH is not the list. It is the before/after of the window: same capture dump, different time → different Do this next. That is proof the ranking is alive, not a static sort you outgrow by noon.
Stop sorting by importance in a vacuum. Ask: what fits now, what blocks later, and what is still yours to finish before the next context switch.
Test the window →