Public: anyone can read this; the crew can change it.
Flow: the week's budget as pipes I can see and turn, and the system does exactly that #8698
Landed in pull #8768 · 2 runs · run
4 earlier comments
Parked by the crew: the check stayed red through 2 automatic tries (pull #8712 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Sent back to you, Mason. #8712 parked after 2 tries, but 2 of its 3 failures weren't yours: test/stale_reds.test.ts had a fixed date, fixed on main in 5bff85db. The one that's yours: "design check: nothing added outside th…" in test/design-lint.test.ts. Rebase on main, fix that, and open it again; the branch mason/8698-flow-the-week-s-budget-as-pipes-i-can-se holds your work.
Reviewed pull #8768 at its head: ticked /flow shows the real pipes with this week's numbers, and each repository has a valve: open, a share of the week, or shut.; Turning a valve is one drag and applies on the next tick; the page shows what it will do before and what it did after.; A valve is a stored value and nothing changes it but a person. Same valves, same decisions (tested).; Where I look often is recorded and shown as a suggestion beside a valve, with one tap to accept. It never moves a valve by itself.. left open: A brand-new person understands it in a 30 second cold read, with screenshots on the pull. — No screenshots are on the pull..
Left open after pull #8768 landed: 1 unticked item remains (A brand-new person understands it in a 30 second cold read, with screenshots on the pull.). 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 #8812. The screenshots could not be taken: looks of the forge are taken signed out over an empty preview, so /flow shows nothing. #8812 lets a preview be looked at as its owner over seeded data, and its first pull carries /flow's desk and phone looks for the cold read.
The owner: "i need to be able to direct the flow... as easy as connecting pipes. like a game", and "make actions and trust that the system behavior is deterministic". Builds on #7668 (pillars) and Next up.
First slice, no game engine: one page drawing sources (my notes, the planner, hunters, reviews) flowing through valves (each repository and pillar) to shipped, with line width as real spend this week.
Done when: