How the System Works
The operating calendar and seasons
How the system knows which houses are open, at what hours, with how many people, on any given date.
This page is a placeholder. Its structure is fixed; the writing lands in a later phase.
Every operating date carries exactly one rules profile, which decides how that day behaves.
What a date carries
All three profiles run the desk 08:00 to 24:00.
| Profile | Weekly cap | Schedule | Floating |
|---|---|---|---|
| Regular school year | 20, soft, overridable | SM, from preferences | Allowed |
| Short break | 40 hard, or 20 soft at spring fling | Claimed, first come | Allowed |
| Winter break | 40, hard | Claimed, first come | Off. Only Harnwell stays open |
A break date inside a semester takes the break profile, settled in advance. An unassigned date, or a summer date with no open house, is dormant: no blocks and no notifications.
Summer is authored, not seeded
Summer moves too much to seed. The Administrator authors it as a season, and each date one of its settings changes becomes an ordinary profile.
When a desk shrinks
Changes reach future shifts only, because past blocks are history. If a future desk holds more workers than its new headcount, the excess are cancelled, not grandfathered.
Everyone cancelled is told. An inbound float on a cut seat is voided too, because a person made the change.
Why it works this way
One profile per date means no date has two answers, summer included.
What this means for you
Read a date’s profile and you can predict its cap and floating.