group-schedulerlisted
Install: claude install-skill BaesTheorem/exobrain-harness
# Group Scheduler
MIST is the scheduler. Gather every constraint already known, propose the
2-3 best concrete times with the reasoning shown, and only then ask humans
to react. A poll is the fallback when reasoning runs out of data, never the
opening move.
Runtime data lives in `scheduler/` (see its README). Availability facts live
in People notes under `## Availability` (format: `[[People Note Schema]]` in
the vault).
## Data sources, in precedence order
When constraints conflict, higher wins. A person's own recent words beat
anything inferred.
1. **People note `## Availability`** -- stated constraints with provenance.
Alex-editable; always read fresh, never cache.
2. **Free/busy cache** (`scheduler/freebusy-cache.json`) -- for friends who
opted in with a calendar feed. If `generated_at` is older than 24h, run
`python3 scheduler/ics_freebusy.py` first (wrap in `mist-progress run`
when interactive). Per-person `error` fields mean stale data: say so.
3. **Discord digest** (`discord/discord-digest.json`) -- availability
statements from the last 7 days that may not be integrated yet.
4. **Claude Bus** (`/claude-bus`) -- for friends whose Claudes are on the
bus: ask in a `scheduling` thread. Bus protocol already permits coarse
availability ("free after 6 most weeknights") without human approval;
never ask a friend's Claude for calendar contents.
5. **Alex himself** -- Google Calendar MCP (camelCase params, see
`/calendar`) plus Things 3 deadlines.