FoodRescue
The food exists. The hunger exists. The clock is running.
A refrigerated pallet dated for tomorrow is not waste — not yet. FoodRescue is designed to turn donor offers into safe-to-redistribute batches, verify cold chain and consent on both sides, and propose a route for a human dispatcher to approve. It moves nothing itself. Today it walks through food-safety and matching checks from what you describe, and no donors, drivers or deliveries are connected.
- Channels (designed)
- Web todayPlanned: WhatsApp · SMS · API
- Languages (designed)
- English · Spanish · Portuguese · French · Arabic
- Designed for
- Latin America · Europe · Africa · Asia
- Tools
- 9 declared3 not connected · 6 illustrative
Forty-seven yoghurts, one Thursday
An illustrative scenario, not a real rescue or a real person: Aaliyah Khan runs the day shift at a community kitchen in inner-west Sydney — about 160 meals daily for newly arrived Afghan and Hazara families. FoodRescue’s own system prompt opens with her: at 14:30 a nearby supermarket offers forty-seven refrigerated yoghurt pots, dated tomorrow, binned at 17:00 unless collected. In the design, within two minutes the batch is classed and its allergens disclosed, the kitchen’s halal and lactose-mixed policy checked, consent confirmed on both sides, and a volunteer driver proposed — with a handover protocol drafted in Dari, queued behind the always-ask gate until a named dispatcher says yes. FoodRescue proposes everything; it moves nothing.
“Never propose a match that would let a single recipient go hungry tonight while honest food goes to landfill.”
Seventy-five minutes, two checkpoints
Every rescue is designed to run the same wire: posted, gated, matched, routed, delivered. The gates are not advisory — they are checkpoints the flow cannot pass until the evidence does. Replay one specimen rescue below, then watch the second specimen, where the cold-chain gate refuses a batch of dairy and the match drops a tier rather than bend a rule.
Two specimen rescues, replayed step by step. The clean pass: a bakery’s forty loaves posted at 18:40 clear the cold-chain and allergen gates, are matched at 18:52 to a community kitchen for tomorrow’s breakfast for sixty, routed past the always-ask dispatch gate, and delivered at 19:55. The refusal: dairy custard out of refrigeration since 14:10 is blocked at the cold-chain gate, never reaches the allergen gate, and is re-matched a tier down the food recovery hierarchy to animal feed — never a person’s plate. Each step below carries its detail and the rule that enforces it.
Select a step to read the rule behind it.
A bakery lists forty wholemeal loaves, baked this morning. Ambient class; allergens disclosed — gluten (wheat).
The rule: A listing exists only with donor consent to publish it, and the allergen field is required. “Unknown” is an answer the second gate will refuse.
Ambient class: no refrigeration clock to spend. Hot or chilled food would start a timer here.
The rule: Per the hot-food-handling-safety skill, danger-zone time is cumulative: two hours hot-hold (four in the EU and UK), four refrigerated, six frozen. A spent clock blocks tier 2 in code, not in guidance.
Disclosure complete; best-before tomorrow, inside the runway.
The rule: Per the allergen-and-dietary-policy skill, FDA Big 9 and EU Annex II live in one field — undisclosed blocks the match outright. Expiry: before use-by; one day’s grace after best-before, shelf-stable only.
A community kitchen three kilometres away — tomorrow’s breakfast for sixty. Consent confirmed on both sides.
The rule: The matching engine refuses internally if either side’s consent is missing, and below 0.80 confidence no match is proposed at all — in the planned deployment, the case goes to a named human instead.
One volunteer driver, one stop; the assignment queued behind the always-ask dispatch gate.
The rule: Per the vehicle-routing-with-perishables skill: Clarke–Wright savings, with time-to-spoil — not distance — as the dominant cost. The route is proposed; in the planned deployment, a named dispatcher approves.
Handover stamped. Forty loaves become breakfast for sixty instead of landfill.
The rule: Per the food-loss-and-waste-protocol skill, every rescue is ledgered under the FLW Standard — mass, greenhouse gas and water avoided, with the avoided destination named.
The rule behind each step
Hover over, focus, or select any step on the wire to read the rule that enforces it — and the named skill the rule comes from.
A specimen rescue, not telemetry: the times, the loaves, and the custard are illustrative. The gates are written into the tools — the danger-zone clocks, the allergen and expiry checks, the 0.80 confidence floor, and the always-ask dispatch gate. Today no donor, kitchen, driver or delivery is connected, so no rescue like this has taken place.
Upward on the hierarchy
Every item is meant to route to the highest tier it can safely reach on the EPA and FAO food recovery hierarchy — its food-recovery-hierarchy skill counts each step down as a missed meal. Tier 2, feeding humans, is the default, behind five preconditions written into its tools — the ticker’s two gates among them.
Cold-chain integrity
Hot food past the two-hour danger-zone clock — four in the EU and UK — is blocked.
Complete allergen disclosure
FDA Big 9 and EU Annex II in one field; unknown blocks the match.
Expiry runway
Before use-by; one day’s grace after best-before, shelf-stable only.
Donor consent
To publish the listing and disclose allergens to the recipient.
Recipient consent
To the temperature class, allergen profile, and dietary policy.
The language of a rescue
Food rescue keeps a precise vocabulary. The ticker’s gates spend danger-zone clocks and cold-chain budgets; two more terms it uses without stopping to define:
- Handover stamp
- The wall-clock moment the donor releases the food — t₀ for every clock that follows.
- The avoided destination
- Rescued food never left the supply chain; the planned FLW-Standard ledger records where it would have gone — usually landfill.
What it will never do
- Never match without consent on both sides — the engine refuses internally, and the refusal is surfaced, not worked around.
- Never route past a broken cold chain, an undisclosed allergen, or a kitchen’s religious dietary policy — halal kitchen, pork lard: excluded, whatever the probability.
- Never dispatch a driver itself — dispatch is always-ask and nothing is proposed below 0.80 confidence; in the planned deployment, a named human approves. Today no driver, listing or delivery is connected.
- Never publish recipient identities — no names, no location finer than about a kilometre.
- Never accept opened infant formula, per the WHO Code on breast-milk substitutes.
- Never displace a local market — where one supplies the same commodity, recommend the cash route instead. Do No Harm.
“Cultural fit overrides numerical optimisation.”
The arithmetic of arrival
Under the warmth sits hard logistics — on paper, so far: no rescue has taken place. Routing is treated as a pickup-and-delivery problem with time windows, solved by Clarke–Wright savings where the dominant cost is time-to-spoil, not distance. Demand is read in WFP consumption scores and IPC phases — urgency weighted by distress, per wfp-food-security-indicators — and humanitarian catchments get the Sphere Handbook’s 2,100-kilocalorie daily floor. Every rescue is to be accounted under the FLW Standard — mass, greenhouse gas and water avoided — against named SDG 2 and 12.3 indicators.
Designed for a network, not an app
No affiliation or endorsement. These are the organisations whose published guidance the design draws on. No partner system is connected.
The design looks to the organisations that already run food-recovery networks and publish how they work — WFP, Too Good To Go, Olio, Feeding America, and Banco de Alimentos — for registries, demand intelligence and last-mile practice. None of their feeds is connected: recipient examples in the Hub are sample data, and FoodRescue is instructed never to fabricate a donor record or a recipient ID.