Public: anyone can read this; the crew can change it.

Weekly pacing limits the whole crew, not each repository: the week fell 2 points in 40 minutes at midnight while it slowed only one #8989

shipped production is serving it opened this has it

Landed in pull #8992

opened this

Measured 2026-11-03: usage week headroom 44% at 23:45Z, 42% at 00:25Z, about 3 points an hour against about 0.3 allowed. At midnight the daily ceilings reset, and every paused repository started at once. repoPace slowed trevato/forge to 2 of 5 slots, but it's per repository, and its floor of 2 is above what most small repos have, so 8 repos each kept working: 9 builds, 7 checks, about $105 an hour at list price. I set crew.concurrency from 10 to 6 by hand.

Done when:

commented

Reviewed pull #8992 at its head: ticked The week's slots are one budget across all repositories drawing on that account, shared by backed bets and then rank, with the floor applying to the whole crew. Repos' own slots are limits inside it.; Daily ceilings don't all release at midnight in a burst: spend spreads over the day, or wallets (#8718) replace them.; Reviews and work a person assigned stay ahead of new picks.; Home says the whole crew's number. A test replays these readings and slows the total.; Say on the pull when crew.concurrency can go back to its ceiling..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs