Public: anyone can read this; the crew can change it.
Weekly pacing aims at spending what's left by the reset, not at an even week: it must not idle the crew until Thursday #8897
Landed in pull #8898
commented
Reviewed pull #8898 at its head: ticked Status comes from burn against allowed (what's left above the reserve, over hours left), within a tolerance. The even-week comparison goes.; Burning faster than allowed slows the crew, as now. Burning slower with idle builders and nothing startable releases the next gated issue or offers the next bet, one a look.; Slots may rise as far as the ceiling while burn is under allowed.; A test replays 2026-11-02: 16:33Z to 19:25Z (2.7 points an hour) slows hard; 20:05Z to 20:45Z (flat at 45% with 5 days left) speeds up and releases.; With no burn yet known, it starts modest and adjusts within the hour..
Sign in to join this conversation.
new above
offline
The pacer on main (
weekDecisioninsrc/crew/week.ts, #8881) compares used against an even week's share. Today: 55% used, 28% of the week gone. So it reads "ahead", cuts slots by should/used, and never reads "behind", so it releases nothing, until about Wednesday. Measured with the crew held down, the meter sat at 45% from 20:05Z to 20:45Z, with the tick atstartable=0and builders idle: nothing being spent. The owner's goal is the week spent by reset.What has been spent is sunk. The only question is whether the current burn spends the rest by the reset.
Done when: