# Guest Protocol

> The few guests who need special handling, qualified by obligation and received with discretion. Name the guests you
> think need special handling and what each arrives with, and get speakers, sponsor staff and press routed out first,
> the rest qualified by obligation rather than status, the roster with its holder, viewers and deletion date, the
> program, visibility and escort postures set against what each guest actually said - then the greeter brief, the
> liaison intake for any protective detail, and who decides on the day. Built on the SkillSafe skill
> @samber/event-vip-management, from samber/dev-event-organizer-skills (MIT), by Samuel Berthe. Four siblings own most
> of what people call a VIP, and the most common correct outcome is that nobody is left in scope. It never infers
> anyone's importance, identity, gender, nationality or visibility from a name or a title, leaves security decisions to
> the guest's own detail, and labels its own numbers self-set.

https://guest-protocol.skillsafe.ai/

## What is free
- The route-out: speakers to event-speaker-experience, sponsor personnel to event-sponsor-fulfillment, press to event-press-relations - and "nobody in scope - stop" when nobody remains.
- The qualification test on whoever is left: external protocol, security, discretion or dependency exposure (only when the relationship recurs) - a title alone qualifies nobody.
- The identification breadth, program, visibility and escort menus re-ranked from the interview, every deleted rung struck (a closed print run and seating plan delete both marker rungs).
- The roster with its fields, named holder, viewers and deletion date - a missing holder or date is a fix.
- A visibility posture per guest from only what each said; "not said" stays not said, and the page asks rather than decides while there is time.
- The liaison intake for a guest with their own protective detail, protocol officer or advance team; the two day-of decisions with a name against each; the hand-offs.
- A verdict: nobody in scope - stop, fix first, ask the guests first, ready to brief the greeters.
- Exports: the roster (.csv, deletion date in its first line), the routing table (.csv), the greeter brief skeleton (.md), everything (.json).

## The metered lanes
Two tasks on gpt-terra, metered per run, routed by `task`. Input string fields: `task` (posture or brief), `event`, `guests`, `notes` (may be empty) and `facts`.
- `posture` replies with `summary`, `verdict`, `routed`, `qualified`, `not_qualified`, `roster`, `program`, `visibility`, `escort`, `decisions`, `handoffs` and `caveats`; the page holds every name, type, pick and posture to its own.
- `brief` replies with the `greeter_brief` (title, who arrives, how to greet, what not to say, photos, escalation), the `liaison_intake` for any guest's own detail, `day_of` and a `note`.

## Links
- API tutorial: https://guest-protocol.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@samber/event-vip-management