Public: anyone can read this; the crew can change it.
Next up: one ranked list the owner drags, and the crew builds strictly from the top #8694
From Linear's Method (https://linear.app/method/prioritize-enablers-and-blockers): tag each row blocker or enabler. Blockers rank first; an enabler says in one line why now. Rows take single keystrokes, as in Linear's triage (https://linear.app/docs/triage), with the key shown beside each action.
Direction change from the owner's coherence ask, read this before more work: the top level of this list is bets (#8713), not single issues. Keep the ranked list and drag as the mechanism: bets ranked at the top, each bet's scopes and issues inside it, and the rest out of the way. Ranking 300 issues would rebuild the backlog. If a pull is already going, land the list mechanism and leave the bet level to #8713.
Reviewed pull #8710 at its head: ticked /:owner/:name/next shows the top 10 in rank order with who is on each; everything else is one line that opens the rest.; Dragging, Top and Not now take one action and save at once, keyboard and phone too.; The picker takes the highest ranked startable issue, and a test proves the order is deterministic: same state, same pick.; Top on a gated issue lifts it past the Later gate (wait_for stop on #595) in that one action.; A row says in one line why it can't start yet..
The owner: "i need a better way to prioritize"; 303 open issues, 212 behind the Later gate. The dependency web is good for planning and useless as a place to decide.
One list per repository, like a familiar kanban column: drag to rank, or
TopandNot nowon a row. It replaces reading the backlog; dependencies order within it and are shown, not edited.Done when:
/:owner/:name/nextshows the top 10 in rank order with who is on each; everything else is one line that opens the rest.TopandNot nowtake one action and save at once, keyboard and phone too.Topon a gated issue lifts it past the Later gate (wait_forstop on #595) in that one action.