Daily booking budget: cap bookable hours per host per day #91

Activity

1. shockalotti

   added

   enhancementNew feature or requestNew feature or request

   on Sep 22, 2026
2. pullfrog commented on Sep 22, 2026

   

   pullfrogbot

   on Sep 22, 2026 – with Pullfrog

   Contributor

   More actions

     ^{｜ Build this ➔ ｜ Make a plan ➔}
3. ovizii commented on Sep 23, 2026

   

   ovizii

   on Sep 23, 2026

   More actions

   Thanks for considering.

   • Is the cap per host across all event types, or per event type? neither, I think this should be decided per person.
   • Should external-calendar busy time count toward the cap, or only Calnode bookings? And do buffers count? Only calndoe bookings should be limited
   • With multiple hosts on an event type, whose day fills up? not sure what "hosts" means in this context. If it means the person whose calendar this lands on, then obviously that person's bookings should be limited.
4. shockalotti commented on Sep 23, 2026

   

   shockalotti

   on Sep 23, 2026

   ContributorAuthor

   More actions

   Thanks for answering all three, @ovizii - that unblocks the spec. Restating it back to confirm understanding:

   • Scope: per person, opt-in (each host sets their own cap; default unlimited). Not per event type, not workspace-wide.
   • What consumes budget: Calnode bookings only - external-calendar busy time and buffers don't count.
   • Multi-host: whoever's calendar takes the booking is whose budget fills.

   That's now fully buildable from our side: a per-host daily cap with day-level accounting in the slot engine (which currently evaluates each start time statelessly, so this is new machinery, not a setting tweak).

   One ask before it gets scheduled: this is so far one voice (a fair one - the side-business case is real). If a second person confirms the same shape, or contradicts any of the three answers above, that settles whether we build exactly this. Watchers, pile on.