Conference workshop registration with room capacity, waitlist promotion, badges, and chair-scoped access
event-registration · 3600 s per turn · source
The ask
We organize a three-day operations summit with 60 paid workshops across three venues, and every workshop is capped at the capacity of the room it is in. I've attached the venue's room list, our workshop schedule, and the registrations so far; when a workshop is full new people go on its waitlist, and when someone cancels, the person who has been waiting longest gets the seat automatically. I need to export name badges for everyone holding a confirmed seat, and a dashboard with confirmed and waitlisted numbers and our revenue from confirmed seats. Each session chair should log in and see only the registrations for the workshops they chair, our finance lead needs a read-only login, and I want an admin login for me and a login for Helena Varga, one of our chairs.
Seed files the agent must import: rooms.csv</code>, <code>sessions.csv</code>, <code>registrations.csv. The agent must leave a RESULT.json with a reachable URL, an admin login, and the named restricted login.
Acceptance checklist
26 binary items. The first 14 are the enterprise baseline shared by every build task (delivery, invitations, roles, server-side authorization, scoped live dashboard, exact lists and exports, audit metadata, validation, persistence); the rest are application-specific. Core items, which together define "first usable": 1, 3, 5, 6, 8, 14, 18, 21, 23.
| Tag | Items |
|---|---|
| Exact | 9 |
| Rule | 4 |
| Permission | 3 |
| Dashboard | 2 |
| Delivery | 2 |
| Sharing | 2 |
| API | 1 |
| Audit | 1 |
| Automation | 1 |
| Persistence | 1 |
The full checklist with per-item "how to check" instructions and expected figures is in checklist.md. Testers see it; the agent never does.
Change requests
Each change is a new one-shot turn on the carried-forward workspace. Only the owner's text below is sent; the tester items are withheld. After each change the full checklist is rerun, so regressions count.
Change 1 · 3 new checklist items
Add a report with revenue by track and how full each workshop is, confirmed seats against the room's capacity. Session chairs should see it for their own workshops only.
Change 2 · 3 new checklist items
One person shouldn't hold confirmed seats in two workshops that run at the same time. If they try, put the second one on its waitlist or refuse it, and show me the double bookings we already have.
Change 3 · 3 new checklist items
At the door, session chairs will check people in. A confirmed registration can be marked checked in, nobody else can be, and chairs can only check people in for their own workshops.
No published score. Build runs need a human acceptance pass on a live URL, and no arm has completed one for the full set. Automated probes generate a tester sheet; they do not substitute for it. Results will be published as a separately labeled release when an arm completes.