Plan → source → coordinate
Size a camp kitchen for the week, and this works out what to buy, which local farms should supply it and why, how to consolidate the pickups, who to contact, and what it does to footprint, cost, organic share and waste. Built for the crew doing the sourcing: a plan you can act on, not a chart. All farms, prices and contacts are synthetic.
Camp size
Headcount the kitchen serves, 10 to 200.
Build week through strike.
Extra bought over what gets eaten.
Storage & transport
Reefer and ice, 0 to 4 °C. Set 0 for no reefer. Binding constraint on fresh food.
Shaded or root store, 7 to 12 °C. Keeps tolerant items off the reefer.
Farm-to-playa cold chain. Caps how far a perishable can travel.
Menu & sourcing
Sets the food mix the camp buys.
What the plan optimises when it picks farms.
First three reshape the buy. Nut-free rides as an order-sheet note.
The week, in numbers
What the week needs, by food type
Storage · does the fresh food fit, by store?
The dance · how the four priorities trade off for this camp
Same requirement, sourced four ways. Lower is better for transport and cost; higher is better for organic. No single column wins all three, which is the point: pick the priority that fits what this camp cares about, then tune the menu and cold capacity until the plan sits where you want it. Your current choice is highlighted.
What to get, and from whom
How to run it · consolidated pickups
Who to contact · order sheet (copy-paste ready)
Contacts are synthetic. Replace each farm with the real operation from the USDA Organic INTEGRITY Database and the AMS Local Food Directories before any outreach. This is a coordination scaffold, not a directory.
Food type · click a type to follow it through both maps
Where it comes from · 100 mi foodshed
Where it goes · Black Rock City
Impact of what is currently selected
Lot register · click a row to trace it
A lot is one traceable consignment: one producer, one category, one camp, one delivery window, one route. The trace id is what would be written on the box.
Why this tab exists
Storage is what decouples harvest timing from delivery timing, which makes it the precondition for the consolidation finding on the Ledger tab. You can only aggregate camp orders into one full load if something can hold the harvest until that load is full. A foodshed with no cold storage cannot consolidate perishables at any price, and no amount of freight arithmetic changes that. Three of this set's producers have no on-farm cold storage, which forces their harvest onto a same-day dedicated run and therefore onto the losing side of the crossover before a single routing decision is made.
Capacity against demand, by delivery window
Facilities
Producers with no cold storage on the farm
Cold storage at the farm is a cheaper intervention than any change to the trucking, and it is completely invisible in a food-miles argument. It is also the one intervention here that keeps working after the event is over.
Shelf life against how long the chain actually holds a lot
Assumptions you can turn off
By category · local chain versus incumbent chain
gCO2e/kg is freight only. A category where transport is a small share of total footprint cannot be made good or bad by a routing decision. See DESIGN.md section 4.4.
Crossover · at what order size does the short chain win on freight
Series · every year carries its own status
2024 is reconstructed, 2025 is partially measured, 2026 is a target. None of the three is a clean measurement, and a trend drawn through three different epistemic statuses is not a trend. The status column is the point of this table.
Local share of food mass
Regional economic activity from food spend
What has to happen for this to become a real series
Freight and economic coefficients
Claims this tool rests on
Full records in projects/brc-foodshed.context.json. The evidence ledger projects/brc-foodshed.evidence.md is not written yet, and writing it gates every outward claim.
Method, stated plainly