About and research / Messaging rules Edit on GitHubMarkdown

Messaging: what Cookwala says, and how

Status: 2026-10-04. Written before the pages. Every page follows this document.

1. The one sentence #

Cookwala is the open standard for cooking safely: people, kitchens and robots.

Arabic: كوكوالا هو المعيار المفتوح للطهي الآمن: للناس والمطابخ والروبوتات.

2. The triad, used everywhere #

A Cookwala recipe says three things a machine can check:

  1. What to make. Recipes as steps a machine can plan.
  2. When it's done. Temperatures, food-state cues and times it can measure.
  3. What must never happen. Safety limits the device enforces on itself.

Arabic: ماذا نطبخ. متى ينضج. ما الذي لا يجوز أن يحدث أبدًا.

3. The mission, told honestly #

  • Mission: help end hunger, make people healthier, and put robots to work for people.
  • How we say it: "Cookwala helps end hunger by…" followed by a mechanism (less waste, safer rescue, cheaper meals, coordination), never "Cookwala ends hunger".
  • The caveat, once per page where the mission appears: hunger has many causes: poverty, conflict, climate, prices, policy. Cookwala's part is real and partial.

4. Three horizons, with restraint #

HorizonSayDo not say
Now (to 2028)Safer devices that refuse rather than guess; recipes that work across machines; food banks rescuing more with phones and spreadsheets; agents that can't be tricked; open tools you can run today"widely adopted", "proven"
Next (2028 to 2036)Home and commercial robots that cook every cuisine; a consented dataset that keeps recipes alive; new roles; less waste; cheaper, healthier meals; a standard regulators point to"robots in every home", numbers of robots
Later (2036 and beyond)Cooking as infrastructure: nutritious food for anyone, anywhere, including disaster zones and people who can't cook; less waste and lower emissions; human time returned; machines that inherit culinary heritage instead of erasing itdates, counts, "end hunger"

The reader discovers the scale by following the mechanisms; we do not announce it.

5. Writing rules #

  • Plain words, short sentences. One idea per sentence.
  • No buzzwords: not revolutionary, disruptive, AI-powered, world-class, first and largest.
  • Every number is measured, modelled or assumed, with its source, visible next to the number.
  • Now / next / later for anything that does not exist yet. Never imply a service exists.
  • No partner, user, pilot, quote, logo or endorsement that does not exist. Organizations appear as sources or as "who we want to work with", labelled.
  • People are described by role and situation, never by deficit. No "the vulnerable" as a noun; "children under five", "people who cannot cook for themselves".
  • Safety is a number with a unit, never the word "safe" alone.
  • Refusal is good news. Say "the device refuses before anything heats up" with pride.
  • Say what we do not know and what went wrong, on every impact and roadmap page.
  • Code in code blocks; expected output after every command.
  • Arabic is a first-class version, not a translation afterthought: same structure, same honesty, right-to-left layout, Arabic numerals as the reader expects (Western digits are acceptable in technical content).

6. Vocabulary #

UseInstead of
recipe, step, done, safe band, limit, refuse, check, verify, consentinstruction set, AI brain, smart, autonomous
device, executor, hubthe robot (unless a robot is meant)
people who cannot cook for themselvesthe elderly, the disabled
food bank, community kitchen, programbeneficiaries, recipients
measured, modelled, assumedestimated, projected (without a label)
now, next, latercoming soon, roadmap item (without a horizon)

7. Proof we may show today #

Counted from the repository at build time (/v1/stats.json): operations with physical definitions, conformance vectors, safety limits, agent-safety tests, humanitarian rules, schemas, published recipes, languages, simulators. Each shows its kind. Nothing else is a number unless a source is cited.

8. Calls to action by verb #

try (dry run, simulator) · read (quickstart, Core, whitepaper) · build (SDK, hub, MCP) · publish (recipe, device, pack) · pilot (humanitarian) · review (rule pack, envelopes) · teach (lesson kit) · legislate (model language) · partner and invest (investors page) · contribute (RFC, translation, vectors).

9. Headline bank #

  • The open standard for cooking safely.
  • What to make. When it's done. What must never happen.
  • Devices that refuse rather than guess.
  • Food that would be thrown away, reaching a plate, safely, by SMS.
  • Every cuisine, with the cook's name on it.
  • Safety is local. Consent is explicit. Records can be checked.
  • Robots are learning to move. Nobody had written down how to cook.

10. What every page carries #

A status chip (Core normative, draft profile, experimental, planned), the one sentence in the footer, licences per layer, a link to the critiques, and a "what we don't know yet" block on any page that states an outcome.