# Date Windows

> Pick the date a technical event runs on, then write the venue request and - once money handling exists - the
> announcement. Enter who the audience is, the candidate start dates, the competing events you know of and the
> calendars you have checked. Built on the SkillSafe skill @samber/event-date-selection
> (samber/dev-event-organizer-skills, MIT).

https://date-windows.skillsafe.ai/

## What is free
- The day type from whose time attendees spend: weekdays for professionals on employer time (the DevOpsDays organizing guide), Friday evening to Sunday for students and hobbyists (the MLH hackathon organizer guide); a mixed audience picks a pole, splits the programme or - weakest - uses a boundary day, never an average.
- Every candidate window checked for the wrong weekdays, a must-land-by date, same-date clashes, same Monday-to-Sunday week events, and same-city events worth sitting beside for travelling audiences (piggybacking); every competing event called dodge, piggyback, watch or clear; ecosystem anchors flagged.
- Six calendar categories marked checked (with the source) or outstanding - this page never supplies a holiday date; the multi-geography pass promoted for audiences from several countries; deeper checks deleted under a forced window.
- Evening slots and a recurring series stuck on one weekday and hour flagged for who they exclude.
- The surviving windows ranked for the venue (three to five, Get Options), the announcement rung (venue-locked, money-ready, program-teased), and the money gate that holds every announcement.
- Windows CSV, Markdown and JSON exports.

## The metered lanes
Two tasks on gpt-terra, metered per run, routed by `task`. Input string fields: `task` (decision or outreach), `event`, `windows` and `facts`.
- `decision` replies with `summary`, `daytype`, `windows`, `conflicts`, `calendars`, `slot`, `announcement`, `signals` and `caveats`; the page holds the day type, every window's status and rank, every call, every calendar status and the announcement rung to its own.
- `outreach` replies with `venue_subject`, `venue_body`, `announcement`, `hold_reason` and `note`; the page requires every surviving window in rank order, no rejected window, and no announcement unless the money gate has passed and the venue is signed.

## Links
- API tutorial: https://date-windows.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@samber/event-date-selection