The week is one budget for the whole crew (#8989)
crewWeekFor (src/crew/week_read.ts) reads the week once per set of accounts and decides in slots for the whole crew: its ceiling is crew.concurrency, its floor (WEEK.floorSlots) applies to the crew, not to each repository. repoPace gives a repository budget - slots running in the other repositories on the same accounts, held under the repository's own slots, which stay limits inside the budget.
- Only new picks wait on it. Finishing, rework and reviews use
repoPace(..., false)and run ahead. autonomyTickdrives repositories with a backed bet first, so a short budget goes to what the owner backed, then the rest in order.- There is no daily dollar ceiling and no midnight stagger (#10623): the week's share is the one gate.
autonomy_ceiling_usdstays in the table, unread and unwritten, so no migration rewrites the table; the autonomy card, the terminal screen andGET /api/v1/mapshow the share of the week used (week: used, allowed, elapsed,pace,resetsAt) instead ofceilingUsd; theceilingfleet verb is gone. - Home and the terminal print the crew's number: "the week allows the whole crew N of M slots".
- Picks made earlier in the same tick in other repositories count against the budget before their runs show, so a burst across repositories cannot pass the crew's floor.
- Work a person assigns starts through the dispatcher, which does not read
repoPace, so it is not held by the crew's budget.