# Social Slate

> How many official social occasions to run, and a floor every one of them clears. List the official social occasions
> on the table with their slots against the published grid, owners, venues and the access commitments already
> published, and get the slate depth decided, the inclusion floor checked per slot rather than per activity, the closing
> occasion protected as programme and an owner named for every occasion beyond the first - then the published social
> programme page and an access statement per occasion. Built on the SkillSafe skill @samber/event-official-social-program,
> from samber/dev-event-organizer-skills (MIT), by Samuel Berthe. What is already decided, and by whom: each occasion's
> format and the alcohol posture belong to event-hospitality (if it has not decided them, the page routes there and
> stops); the access commitments come from event-accessibility-inclusion and are never invented; schedule non-overlap
> goes to event-schedule-design; satellites to event-side-event-coordination; the code-of-conduct scope to
> event-code-of-conduct. It never moves a slot, and labels its own numbers self-set.

https://social-slate.skillsafe.ai/

## What is free
- The hospitality gate: if the format or the alcohol posture is not decided, "decide the format with hospitality first" and a route to event-hospitality.
- The slate-depth menu (a single social occasion, two occasions on separate slots, a themed multi-activity track) re-ranked from the interview, every move named and every deleted rung struck.
- Occasions sharing hours with each other or with the main programme.
- The inclusion floor per slot: in every hour the slate offers anything, one option clears each published commitment - never an invented one.
- The closing occasion's protection, an owner per occasion beyond the first, and the venue-hold and access-statement dates.
- The hand-offs to schedule design, side-event coordination, accessibility and inclusion, and the code of conduct.
- A verdict: decide the format with hospitality first, fix first, ready to publish.
- Exports: the slate (.csv), the floor per slot (.csv), the slate calendar (.ics), the page skeleton (.md), everything (.json).

## The metered lanes
Two tasks on gpt-terra, metered per run, routed by `task`. Input string fields: `task` (slate or announce), `event`, `occasions`, `commitments`, `notes` (may be empty) and `facts`.
- `slate` replies with `summary`, `verdict`, `depth`, `overlaps`, `floor`, `closing`, `owners`, `dates`, `handoffs` and `caveats`; the page holds every row to its own.
- `announce` replies with the published social programme page: `title`, `intro`, `occasions` (each with an access statement), `what_to_expect`, `code_of_conduct_note` and a `note`.

## Links
- API tutorial: https://social-slate.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@samber/event-official-social-program
- Related: https://access-pledge.skillsafe.ai/ and https://conduct-desk.skillsafe.ai/