# Expo Floor

> An expo floor where every booth gets traffic and every sponsor gets what their tier promised. Enter the floor you
> were given, the booths by sponsor tier and what each tier already promised, the venue's access hours, power and
> rigging rules, and get the layout that carries attendees past every booth, the tier-to-physical-spec catalog, power
> and network per booth, the setup and teardown schedule as offsets from one anchor, staffing and conduct rules and a
> traffic mechanic for the booths the layout cannot reach - then the exhibitor manual and the pre-doors walk-through.
> Built on the SkillSafe skill @samber/event-booth-experience, from samber/dev-event-organizer-skills (MIT), by
> Samuel Berthe. Route, don't decide: the signed floor plan, the aggregate capacity, the tier ladder and the conduct
> policy never move here. It never invents a dimension, a power figure, a price, a time, a booth, a sponsor or an
> approval, routes every fire lane, egress, occupancy and rigging sign-off to the venue and the authorities, and labels
> its own numbers self-set.

https://expo-floor.skillsafe.ai/

## What is free
- What may not move, written down first: the signed floor plan, the aggregate capacity, the tier ladder, the conduct policy - each with the sibling it routes to.
- The venue facts settled before any design: access hours, the shipping window and fees, overnight storage, rigging, the power supplier, the drop cost, the request deadline and the print date; a missing one holds the verdict at "settle venue facts first".
- The layout and traffic pattern menu re-ranked (a corridor deletes the loop, the grid and the hub; a hall promotes the racetrack), every deleted rung struck, and the booths the layout cannot reach named.
- The booth-spec depth menu and the eight-row tier-to-spec catalog (footprint, furniture, position class, power, network, vertical limit, signage rule, staffing) with every promise the spec cannot meet flagged.
- Power and network per booth: the drops counted, costed and checked against the request deadline.
- The setup and teardown window menu (no secure storage deletes the overnight build) and the master schedule as offsets from doors open, with clock times and checks against the access hours.
- Staffing and conduct provisioning, a traffic mechanic aimed at the unreached booths, the review before print and the walk before doors.
- A verdict: settle venue facts first, fix first, ready for review before print, ready to print.
- Exports: the spec catalog (.csv), the schedule (.csv and .ics), the walk-through (.md), everything (.json).

## The metered lanes
Two tasks on gpt-terra, metered per run, routed by `task`. Input string fields: `task` (floor or manual), `event`, `tiers`, `venue`, `notes` (may be empty) and `facts`.
- `floor` replies with `summary`, `verdict`, `fixed`, `layout`, `catalog`, `power`, `schedule`, `staffing`, `mechanic`, `review` and `caveats`; the page holds every pick, footprint, drop count, date and schedule row to its own.
- `manual` replies with the exhibitor manual - `title`, `welcome`, `your_booth`, `arrival`, `schedule`, `power_and_network`, `staffing_and_conduct`, `the_mechanic`, `contact`, `teardown` - plus `walk_through` for the morning and a `note`.

## Links
- API tutorial: https://expo-floor.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@samber/event-booth-experience
- Why a sponsor segment buys: https://sponsor-why.skillsafe.ai/
- Pricing the tiers: https://sponsor-ladder.skillsafe.ai/