How the System Works
Hours, caps, and attribution
Which operations add hours, which only move them, and what the soft and hard caps actually stop.
This page is a placeholder. Its structure is fixed; the writing lands in a later phase.
Some operations add hours to a worker’s week. Others only move hours that already exist, so they never meet a cap.
How it works
A week runs Monday 00:00 to Sunday 23:59, never a rolling seven days, so each week settles alone.
Every hour counts at the worker’s home house, whatever desk they stood at. The choice of home over host is arbitrary, so the report keeps the detail: home, floated out, picked up across houses.
| Operation | Cap |
|---|---|
| Claim an open shift | Warned at soft, refused at hard |
| Take a recurring slot | Over-cap weeks skipped whole |
| Accept a swap | Refused at hard |
| Hand off a shift | Never consulted |
| Get floated | Never consulted |
One cap covers the week campus-wide, because per-house caps would mean redundant configuration and uneven enforcement.
A week straddling two types takes the strictest, on the safe side.
Why it works this way
A float relocates hours already scheduled, so the weekly total does not move.
A handoff is exempt by a recorded decision: mutual consent between two named workers outranks the cap check.
A recurring pickup skips an over-cap week whole instead of warning, because one tap commits many weeks. That week stays claimable on its own.
What this means for you
Read the cap off the week on screen, because a season may set any number.
Hours count assigned blocks, not minutes worked, so a drop partway through a block forfeits the minutes worked in it.