🍳 Foodlangalpha
ORF-compatible Works offline Open source

Recipes you write by hand. Machines can run.

Foodlang is a tiny, readable recipe language. Write a recipe like a little script — then compile it to coffee machines, robots, industrial systems, and the web.

Try the Playground Get Started View on GitHub

No account required · Runs in your browser · MIT licensed

iced-vanilla-latte.food
drink "Iced Vanilla Latte" {
  ingredients {
    coffee 18 g
    vanilla_syrup 20 ml
    milk 10 oz
    ice 140 g
  }

  phases {
    preinfuse coffee { pressure 2 bar; flow 2 mlps; time 6 s }
    brew coffee to shot { pressure 9 bar; stop 40 g; max 28 s }
    build cup { vanilla_syrup; shot; stir 5 s; ice; milk }
  }
}

One Recipe, Every Layer

Foodlang isn't just a format — it's a compiler from a single source to the human, web, appliance, robot, and industrial layers.

📖

Human (Cooklang)

Export a friendly, app-compatible Cooklang version for cooks to read and follow.

Cooklang export →
🌐

Web (Schema.org)

Publish recipes as Schema.org Recipe JSON-LD for rich results on the web.

Web publishing →
☕

Appliances

Map to OPC UA, MQTT, Matter, and smart-appliance program payloads — ready for your driver.

Appliance automation →
🤖

Robots

Generate action graphs, PDDL domains, and FOON functional units for planners.

Robot planning →
🏭

Industrial

Express recipes as ISA-88/S88-style batch procedures of operations and phases.

Industrial batch →
🥤

Nutrition (BevFacts)

Export an FDA-style Nutrition Facts label — calories, sugars, caffeine, %DV — estimated from ingredients. Integrated with BevFacts.

BevFacts export →
📱

Scannable QR

Compile a recipe to a QR code (by qrpuppy). Scan it at a machine — if it speaks Foodlang, it runs the recipe.

Recipes as QR →
⌨️

CLI & Library

Validate, inspect, and compile from the terminal or embed the TypeScript library.

Explore the CLI →
The key idea

Food is transformations

Normal recipes describe ingredients and human steps. Foodlang adds the missing layer — culinary transformations — that makes a recipe executable.

Typed inputs in known states become typed outputs in new states. That transformation graph is the bridge between a human recipe and a machine that can run it.

Read the philosophy 
coffee grounds + hot water  →  espresso
cold milk                   →  steamed milk + microfoam
onion:whole  →  onion:diced  →  onion:sautéed
dough:raw                   →  bread:baked

Compile to Eleven Targets

Every target declares its fidelity, so you always know whether the output is directly usable, a mapping, or illustrative. Foodlang refuses to overpromise.

Schema.org JSON-LD

executable

Web-ready recipe structured data.

ORF-clean YAML

executable

Base recipe with X-foodlang stripped.

OPC UA mapping

mapping

Recipe-parameter writes + StartRecipe.

MQTT payload

mapping

Topic + command payload.

Robot action graph

mapping

DAG of dependent actions.

ISA-88 / S88

mapping

Operations and ordered phases.

Cooklang

illustrative

Human-friendly, lossy export.

PDDL

illustrative

Planner-compatible domain + problem.

FOON

illustrative

Functional object-oriented network.

Appliance program

mapping

Smart-appliance coffee program mapping.

Matter

illustrative

Future-compatible device mapping.

Honest by Design

Foodlang grades every recipe across seven levels — from human-readable to industrial — reporting pass, partial, or fail, never pretending a mapping is a running machine.

0readable
1parseable
2structured ingredients
3process-aware
4appliance-mappable
5robot-plannable
6industrial-mappable

How validation works →

Ready to make your recipes executable?

Open the playground and watch a recipe compile to every layer — entirely in your browser.

Open the Playground Read the Docs