Someone at a real clinic was rebuilding the week's schedule by hand, every single week. Same names, same grid, same hours re-checked by eye. Once you've watched somebody do that a few times, it's hard to leave alone.

Scheduling looks simple until you write down the rules: every provider owes a certain number of hours, blocks can't collide, availability shifts week to week, and a human still has to be able to overrule the computer without a fight. On top of that, this is patient-adjacent work, so I wanted it to run with no server and no network at all; nobody's clinic schedule should depend on someone else's uptime.

The person keeps the pen; that was the rule I built everything around. Autofill packs the week as a first draft, and the Attention panel sits beside the board flagging whoever is short hours or unassigned, so you can see at a glance what the draft got wrong and fix it yourself. The machine does the tedious pass; you do the judgment. The whole thing runs in the browser with no backend.

It's live at beaconscheduler.quiettools.dev, runs with zero network, and drafts a real clinic's week. In the demo it schedules a fictional practice, Beacon Pediatric, so you can push it around freely.