# Slot Desk

> Lay a conference's accepted sessions into a session grid and check it before it goes public. Paste the sessions
> (id, title, speakers, format, length, track, expected audience, level, a pinned time), the rooms (capacity, walking
> minutes, floor, availability) and the speakers' availability windows. The page lays the grid and checks the four
> clash types, room capacity, the buffer, track starts, pacing and the publication date. A metered run writes the
> schedule plan, or names sessions one audience would want at the same time, with swaps the page re-checks.
> Built on the SkillSafe skill @samber/event-schedule-design (samber/dev-event-organizer-skills, MIT).
> Not affiliated with FOSDEM, PyCon or any scheduling tool.

https://slot-desk.skillsafe.ai/

## What is free
- The slot standard: one talk length and one slot length (talk plus buffer); workshops take consecutive slots, lightning talks share one, and odd durations are flagged.
- The layout: keynotes as plenary bookends in the largest room, the venue's breaks at their contracted times, then every other session hardest-constrained first (fewest feasible positions), matched to rooms on expected audience rather than track, with pinned sessions placed where they were pinned.
- The four clash types over the finished grid: a session outside its room's window, a speaker outside their window (for a shared session, the intersection of every co-speaker's windows), two sessions in one room, one speaker in two rooms; plus capacity overflow, same-track sessions head to head, and every session that does not fit, with the reason.
- The buffer rung (slot-internal by default, room-turnover-aware when a room needs an AV reset or furniture moved), checked against the longest walk; a zero-gap grid is refused across floors.
- Synchronized or staggered starts (narrow corridor), the clash depth (availability only for one room), pacing flags (post-lunch dip, the last slot of the last day, a deep-dive opening a mixed room, bookend keynotes), the publication posture (release early, or versioned for multi-day multi-track grids) with a publish-by date (60 days out when attendees travel), and the disruption order.
- A grid CSV, a calendar (.ics) file, and Markdown and JSON exports.
- After you open or save a grid, a "What moved" list of every session whose day, time or room changed, ready to copy to the speakers affected.

## The metered lanes
Two tasks on gpt-terra, metered per run, routed by `task`. Input string fields: `task` (plan or overlap), `event`, `grid` (every row and room, each session with its speakers and expected audience against the seats, co-speaker intersections and speaker windows) and `facts` (the page's picks and every finding).
- `plan` replies with `summary`, `slots`, `fixed_points`, `breaks`, `rooms`, `clashes`, `buffer`, `alignment`, `pacing`, `disruption`, `publication`, `metrics` and `caveats`; the page holds the clash depth, buffer, alignment, posture, date and every fixed point to its own, and refuses numbers or sessions not in the input.
- `overlap` (multi-track only) replies with `pairs` (a, b, when, why, and an optional swap), `clear` and `note`; the page checks that each pair really runs at once and re-runs every swap through the four clash types and the rooms' seats.

## Links
- API tutorial: https://slot-desk.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@samber/event-schedule-design