Cookwala

Cookwala / For

For farmers, cooks, chefs, home cooks and culinary schools

A recipe written for Cookwala keeps your name and your cuisine alive on every device that cooks it, with the steps a machine must never skip written down. A farm with a glut could list it by SMS to any program that runs the profile; none does yet.

Why it matters to you

The recipe format carries what a dish is: its essential parts, its flexible parts, what is never added, the cook's language and the cook's name. A planner substituting for a budget may change the flexible parts; if it changes an essential one, it is no longer making your dish and must say so. Machines that cook from consented recordings credit the household that taught them. Culinary schools can teach food safety with a format that checks itself.

Ways in, light to deep

  1. Farmers. FARM 120KG TOMATO A BB0411 to a program's gateway where one runs; later, read supply and demand signals that treat every producer the same.
  2. Cooks and chefs. Turn one recipe you know by heart into a Cookwala recipe; review the step sentences in your language; later, record consented sessions with credit.
  3. Schools. Use the nine example recipes as teaching cases; add your own; use the lesson kit.

First success, under 15 minutes

Cooks, no tools needed: write your recipe with one plain sentence per heat step saying how you know it is done and what must never happen; a contributor converts it and keeps your name on it. If you like the command line:

cookwala init my-dish
# edit my-dish.cookwala.json: every heat step gets an until condition and a hazard
cookwala validate

Farmers: send one SMS offer to a program that runs the profile. None runs yet; the parser and the vectors exist, and the walkthrough shows what happens.

The path after that

  1. Recipe → validation → catalog
  2. Dry run on devices
  3. Execution logs show how it performs on real machines
  4. Revisions with evidence; the recipe climbs from V1 to V3

Other paths