Public: anyone can read this; the crew can change it.
Weekly pacing reads the subscription's real meter: it never slowed the crew while the week fell 8 points in 3 hours #8873
Landed in pull #8881 · 2 runs · run
2 earlier comments · 1 event
Reviewed pull #8881 at its head: ticked Unknown capacity is not treated as fine: home says the pace is unknown, and the crew holds at a stated modest level.; Burn over the last few hours decides too, so a fast afternoon slows the crew within minutes, across every path that starts runs (assigned, reviews, feedback, checks), not only picked builds.; A test replays today's numbers and slows down. /talk keeps its reserve.. left open: Pacing runs on the measured percent the provider reports (headroom), not an inferred dollar cap, so it can't silently switch off. The elapsed share and the percent drive the decision. — The percent is still derived from the inferred dollar cap; no provider percent is ingested.; Home's sentence is on the page for the owner, with the percent left and the projected run-out time. — The percent is shown, but the run-out time appears only when burning, and I did not see the owner view on the preview.; When the pacer is working, crew.concurrency goes back to its ceiling; say so on the pull. — It is an operator setting that this pull did not change; it is still to be reset after merge..
Left open after pull #8881 landed: 3 unticked items remain (Pacing runs on the measured percent the provider reports (headroom), not an inferred dollar cap, so it can't silently switch off. The elapsed share and the percent drive the decision.; Home's sentence is on the page for the owner, with the percent left and the projected run-out time.; When the pacer is working, crew.concurrency goes back to its ceiling; say so 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 into #8960 (pacing on the measured percent, concurrency back to its ceiling) and #8961 (home's sentence with percent left and run-out time).
2026-11-02: the
usagetool's week headroom went from 54% at 16:33Z to 46% at 19:25Z, about 2.7 points an hour, against about 0.36 needed to last until the reset on 11-08 at 02:00Z. At that rate the week runs out in about 17 hours, and/talkgoes with it.src/crew/week.tsshipped in 0.7.339 and did nothing: tickslots=5, no sentence on home. I believereadWeekinsrc/crew/week_read.tsskips the account because itsw.capis null (standing.tsinfers a dollar cap), andweekForthen returns null. Prove that. I setcrew.concurrencyto 4 by hand meanwhile.The owner wants the week spent by the reset, not by Tuesday.
Done when: