Supported by the cited source
The FDA describes the Food Code as a model for retail and food-service safety that jurisdictions can adopt or use when developing their own rules.
RCML-ICUD-007 · evidence companion
What the Food Code claim actually supports
This companion inspects one boundary from the Recipe Revival guide. It does not plan an event, decide whether food service is legal, or infer rules from your location.
Boundary: authoritative federal source ≠ local permission.
Claim under review
The FDA Food Code is a model, not a universal permit
Still unresolved for an actual event
Which state, local or tribal rules apply; whether the activity is regulated as a food establishment or another category; permit or inspection duties; and the venue's own policy.
Do not infer: citing the FDA Food Code does not establish that a potluck, tasting, demonstration or ticketed Recipe Revival event is permitted in a particular place.
Source trace
From source to claim, without skipping the gap
- FDA publishes a model.The FDA's Food Code overview identifies the code as a model used by food-control jurisdictions.FDA Food Code overview ↗
- The 2022 edition is offered for adoption.The current full edition says the model is offered for adoption by governmental jurisdictions with food-service or retail responsibilities.FDA Food Code 2022 ↗
- Adoption varies.FDA tracks state and territorial adoption and separately points readers to state retail and food-service rules.FDA adoption report ↗
- Therefore, local applicability needs a local source.The Recipe Revival guide's instruction to confirm venue rules and the applicable local code is a boundary-preserving next step, not proof of a particular requirement.FDA state regulation index ↗
Evidence states
Keep four different things separate
| Statement | State | Why |
|---|---|---|
| The FDA Food Code is a model. | Source-supported | Directly supported by FDA's own description. |
| The code version and local rules that govern a specific event. | Unknown until located | Depends on the actual jurisdiction and regulatory framework. |
| The venue permits the proposed activity. | Unknown until confirmed | A venue policy is separate evidence from a model code. |
| A no-food story-and-recipe session is the first-test format. | Planning option | It is an ICU proposal for reducing complexity, not a sourced legal conclusion. |
What would resolve the unknowns
A future check needs named evidence, not a guess
- Jurisdiction: the state and relevant local authority for the actual venue.
- Official rule source: the regulator's current code, guidance or permit page, with its version or effective date.
- Activity classification: how that authority treats the exact food path being considered.
- Venue evidence: the room's written policy or direct confirmation for the proposed activity.
- Recorded date: when each source was checked, because rules and venue policies can change.
Audit trail
Inspect the companion's own provenance
The structured source ledger records the reviewed claim, source URLs, access date, supported inference and unresolved fields. No third-party media is used.
Open source ledgerReturn to the Recipe Revival guide →
Scope and caution
This page is an evidence-reading aid, not legal advice and not an event authorization. For an actual event, use the current official regulator and venue sources for that place and activity.