Public: anyone can read this; the crew can change it.
Bets: the owner backs a few named wholes with a share of the week, and the crew finishes them #8713
From the owner's yes on bets, one addition I told them about: if nothing has been backed within a day, the planner's top proposed bets start at a modest share, each marked as not backed by the owner. The crew never sits idle waiting for a tap, and one tap stops any of them.
Parked by the crew: @mason's run ended without a pull: the pull closed
Reviewed pull #8771 at its head: ticked Builders pick only from backed bets, plus a small-fixes lane with a capped share (#8709). An issue in no bet doesn't start by itself.; A bet that hits its appetite stops: no automatic extension, and the lead writes what's left in one line, for the owner to re-back, cut or end. Tested.; A bet page shows each scope as figuring out or just executing, and a scope that hasn't moved reads as a raised hand, without a log.; Finishing a bet is a moment: a one-screen "this is done, try it" with a link, and one tap for "feels done" or "not yet, because...". The changelog groups releases by bet.; The same state gives the same picks (tested).. left open: The planner proposes bets from notes and open work, grouped by theme, each in one screen. The owner backs one with a tap and a share. At most 5 run at once. — Proposals come only from open issues grouped by label; reading notes is split to #8807..
Left open after pull #8771 landed: 1 unticked item remains (The planner proposes bets from notes and open work, grouped by theme, each in one screen. The owner backs one with a tap and a share. At most 5 run at once.). 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.
The open box (planner proposes bets grouped by theme, one screen, back with a tap, at most 5) is split into #8850 (proposals read unlabelled issues and the owner's notes, grouped by theme) and #8851 (one screen at phone width, backed with one tap at its share). The 5-at-once cap is already enforced by MAX_BACKED in src/crew/bets.ts.
The owner, 2026-11-02: "i definitely agree with the things feeling complete", "i should also be influenced to ship in coherent ways". A ranked list of issues makes the stream of small unrelated pulls, since each is picked alone. From Shape Up (https://basecamp.com/shapeup/1.2-chapter-03, https://basecamp.com/shapeup/2.2-chapter-08): appetite instead of estimate, fixed budget with variable scope, no extensions by default. Linear (https://www.lennysnewsletter.com/p/how-linear-builds-product): one accountable owner per project, the team is its own PM. Six weeks is too long here; the week is the big unit and a day the small one.
A bet is: a name, an appetite (share of the week), what done looks like in a few plain journeys, and scopes that each finish independently. It's a thin record over the existing issues, with one crew member as its accountable lead.
Done when: