One Food

The problem

Food information is written as recipes, labels and articles. None of it answers the question people actually have, which is what to do next with the food in front of them, given the season, the diet and what is growing locally.

Why it matters

Food is thrown away because nobody knows what they have, how long it lasts or what it could become. That's a knowledge problem before it's a behaviour problem.

What we built

A food decision engine built on a food graph rather than a recipe index: ingredients, seasons, varieties, growing conditions, substitutions, storage and dietary constraints, connected so a question returns an answer with the reasoning attached.

Where it is now

In build. The tomato work in The Tomato Post is the first slice of the food graph.

Stage

Disciplines

Looking for

• Chefs
• Retailers
• Nutritionists
• Storage and shelf-life researchers

Latest progress

• Now

  Food graph in build: season, storage, substitution, diet.

• Next

  Measuring whether it changes what actually gets thrown away.

Questions it answers

• What should I cook with what I have?
• Is this in season?
• Can I freeze it?
• Can I eat this on my diet?
• What's growing locally?
• What variety should I grow?
• What's a good substitute?

Who it's for

Components