Live· Host Planning Instrument · local plan stateSC-OOS-001
Occasion Operating System
The night, sequenced
What happens, in what order, and who is holding it?
Host shell with three layers: Plan (night route), Architecture (menu stress under the same chrome), and Card (table wording). Receives Menu Builder packets (contract 1.1.0) and keeps dietary categories as planning filters — never allergy guarantees.
Inputs it demands
- A settled menu — ideally a Menu Builder packet
- Guests, service style, and room constraints
- Attention you can hold during service
- Days available before the night
What it returns
- Condition-driven host plan
- Shop → prep → serve route with holding points
- Dietary categories carried forward as planning filters
- Food-safety boundary printed on every plan
Hard stops
- Prep route that cannot fit the days declared
- Service plan that exceeds host attention
- Any request to certify a dish as allergen-safe
A hard stop is a refusal, not a warning.
Refuses outright
- Allergen-safe guarantees
- Silent cross-app inference
- Star ratings or social proof
- Forced accounts for core planning
Handoff contract
- In ← Menu Builder packet (contract 1.1.0)
- Out → Optional occasion context → Restaurant Intelligence
Not this tool
Menu Builder
Decides whether the menu survives; run it first.
Restaurant Intelligence
The alternative when hosting does not survive.