Public: anyone can read this; the crew can change it.
The Later gate is in plain sight: what it holds, who set it and when, and one action to lift any of it #8700
5 earlier comments
From Linear's triage (https://linear.app/docs/triage): add snooze until a date or until new activity, and duplicate merge that keeps the surviving issue's links. For the planner's pass over the gate, keep is justified as blocker or enabler; the rest are proposed to close. Later must not stay a pen that never empties.
From Shape Up (https://basecamp.com/shapeup/2.1-chapter-07): unchosen pitches are dropped, not tracked; important ideas come back. So the default for the gate's 208 is close with one approval unless it joins a proposed bet (#8713), and any closed one stays findable and can be revived with one tap. This overrides my earlier note on keeping blockers and enablers.
Reviewed pull #8711 at its head: ticked Home and Next up (#8694) say in one line how many issues the gate holds, with who set it and when; it opens the list.; Every held issue says so at its top with Lift, and lifting is one action. The Later label reflects the gate: changing either one changes both.; Anything that holds work back for a person says so to that person in the product. A test covers that a new gate shows up on home.. left open: A one-time planner pass over what the gate holds proposes keep, merge or close per issue, grouped by theme in under one screen, with closes applied only on one approval. It stays cheap: titles and bodies only, one run. — Only close is proposed. Merge is not built, keep is just an unticked box, and bodies are not read..
Left open after pull #8711 landed: 1 unticked item remains (A one-time planner pass over what the gate holds proposes keep, merge or close per issue, grouped by theme in under one screen, with closes applied only on one approval. It stays cheap: titles and bodies only, one run.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Split by the planner into #8813. Pull #8711 proposes only close. #8813 adds keep and merge, reads bodies, and holds to the owner's Shape Up default: close unless the issue joins a bet.
Found 22:46Z: issues I unlinked from the gate by hand at 20:46Z and 21:56Z (#7579, #7535, #7534, #7337, #7338, #7335) sat unpicked for 2 hours, with startable=0 in the tick and builders idle, and nothing said why. They carry a live triage note: "no pillar named, so it waits behind the Later gate; name a pillar to move it". So lifting one means naming a pillar too, or the picker passes it by in silence.
Add to this issue: Lift puts the issue in reach of the picker in that one action, with a pillar chosen for it. The tick says why any ready issue is not startable. A test lifts an issue with no pillar and sees it picked.
The owner: "i shouldve been able to know about the later issues. thats something i just told a claude code at one point and it forgot so those things have just sat". #595 holds over 200 issues, and the only sign is a dependency edge and a label. Removing the label does nothing, as I found on 2026-11-02, which is its own trap.
Done when: