Host / facilitator
Open the event, guide two shares and keep participation separate from publication permission.
ICUD-007 · interactive companion
Recipe Revival Event Builder
Turn the first-test guide into a concrete, browser-local plan. Choices shape the run sheet, roles, collection plan, printable cards and transparent scenario math.
Ready. Nothing has been saved.
Plan 01
Host timeline
From guide Builder support
- Builder supportConfirm room, activity boundary, exits, accessibility plan and food path.
- From guideWelcome, state story and food boundaries, and offer the recipe-story prompt.
- From guideFeatured recipe and story share 1.
- From guideFeatured recipe and story share 2.
- From guideShare recipe artifacts only; no food is planned.
- From guideComplete a recipe-memory card without assuming permission to publish.
- From guideRun the closing vote and ask for one concrete follow-up action.
- From guideRecord attendance, cancellations, direct costs, time spent and what people valued.
Plan 02
Role cards
One person may hold more than one role. These are planning assignments, not legal staffing requirements.
Timekeeper / observation recorder
Protect the 90-minute run sheet and record arrivals, costs, time and follow-up actions.
Recipe provenance steward
Record contributor, source, adaptation notes and permission scope.
Plan 03
Ingredient and recipe collection
12contributor requests
2featured shares
2provenance cards
12closing responses
- Invite each planned participant with a recipe title, short story and private/public permission preference.
- Select two shares; the host decides, the builder does not rank contributors.
- Collect exact ingredients, source and participant-reported allergen notes before planning food quantities.
- Keep attendance, interest in another date and ticket/payment signals separate observations.
Plan 04
Transparent first-test budget
Every amount starts unknown. Enter quotes, receipts or an explicit assumption; enter 0 only when you intentionally model no cost.
Formula reused from the ICU break-even tool: ticketed break-even = ceil(fixed cost ÷ (ticket price − variable cost per participant)). If contribution is zero or negative, no finite break-even is reported.
Plan 05
Printable cards
Use the printable view for a host timeline, contributor card and two recipe provenance cards. The cards state unknowns instead of fabricating detail.
Host timeline
- T−60 Confirm venue and boundaries.
- T+00 Welcome and story prompt.
- T+20 / T+35 Two featured shares.
- T+82 Closing vote.
Contributor card
Recipe title, contributor, source or publication, adaptation notes, permission scope and participant-reported allergen notes.
Recipe provenance card
- Recipe
- Not yet recorded
- Source
- Not yet recorded
- Permission
- Not yet recorded
Safety and source boundary
Plan carefully, do not over-promise
Venue and local rules
Confirm the venue's rules and applicable local requirements before preparing, serving or selling food. The FDA Food Code is a model for jurisdictional adoption, not a universal permit.
Allergy and cross-contact
Collect ingredient and participant-reported allergen information. Do not promise an allergen-free event unless the operating model can support it; cross-contact can occur.
Stories and recipes
Participation does not grant permission to publish a story, image or recipe text. Record a specific permission scope.
Sources reviewed 2026-09-12: FDA Food Code 2022 · FDA Food Allergies · ICU source guide.
Reusable event-builder data · Event-plan JSON Schema · Integration record