# Remote Stage

> Run the technical and audience-facing delivery of a fully-remote technical event - then write the production plan or
> the tech brief each speaker receives. Enter whether attendees are inside the event or watching a feed, what was
> promised, the people free for production, last edition's failures, and every session with its UTC slot and speaker.
> Built on the SkillSafe skill @samber/virtual-event-production (samber/dev-event-organizer-skills, MIT).

https://remote-stage.skillsafe.ai/

## What is free
- The grid: sessions at once, the shortest gap, a continuous programme, and each speaker's local start with middle-of-the-night slots flagged.
- Platform: one-way feed plus the existing chat space by default; single feed when nobody can watch chat; a managed virtual venue when sessions run at once, a booth or directory was sold, or procurement forces it; the same sessions on a second live platform deleted.
- Speaker readiness per session: setup note, group check, individual check plus local backup (unrepeatable, unknown connection, live demo), pre-recorded (speaker's night, no live slot, a demo that failed before); a check on a different tool deleted.
- Moderation by name per concurrent session, a technical watcher and a host on the feed when promoted, the speaker moderating their own chat deleted, and staffing against the people free for production.
- The failure drill (fallback line, rehearsed handoff, warm fallback, full drill) with a contingency doc nobody read aloud deleted; six delivery gates, all self-set; run-sheet CSV, Markdown and JSON exports.

## The metered lanes
Two tasks on gpt-terra, metered per run, routed by `task`. Input string fields: `task` (plan or brief), `event`, `sessions` and `facts`.
- `plan` replies with `summary`, `posture`, `platform`, `speakers`, `staffing`, `drill`, `rehearsal`, `budget`, `checks`, `signals` and `caveats`; the page holds the platform, every session's rung and local time, moderators and watchers by name, the drill and the gates to its own.
- `brief` replies with `briefs` (session, speaker, local, rung, message) and `note`; the page holds each brief to the UTC and local start in its first line, the same-link rule, the rung's instructions, the demo fallback and the drop plan.

## Links
- API tutorial: https://remote-stage.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@samber/virtual-event-production