Cookwala / For

For governments, ministries, regulators, legislators and standards bodies

Cooking machines are arriving under regulations written for appliances and software separately. Cookwala gives regulators something concrete to point to, and food-donation programs a data standard with no personal data. It is royalty-free and headed for neutral governance.

Why it matters to you

Safety limits enforced on the device, refusal before heat, a local stop with specified latencies, signed records, anonymous incident reporting, a conformance suite anyone can run and a report format behind any claim. For food rescue: organizations only, aggregates with small-cell suppression, a cold-chain record at every handover, rules derived from public guidance, awaiting professional review (none reviewed yet) and replaceable by national codes. Model clauses that match what the standard does. No government or agency endorses this; the brief says so.

Ways in, light to deep

Read the two-page brief. Then check three things in the repository: the safety limits pack, the conformance runner, the humanitarian data-protection rules.
Use the model language. Food-donation data, cooking-machine safety, household data held by robots, procurement.
Ask your standards body to review Core 0.2. Complementary to the hardware safety standards a device must already meet (ISO 13482, IEC 60335), which this standard does not replace.
Run a national registry node and recall feed. Recalls reach kitchens without a foreign server.
Fund a pilot with your school-meal program. Pre-registered, with an independent evaluator; results published whatever they show.

First success, under 15 minutes

Read the brief (two pages), then open profiles/core/safety-limits.default.json and conformance/ on GitHub and run:

python tools/run_conformance.py --report report.json

conformance: 137/137 passed · report.json

The path after that

Brief → review by a national standards body → reference in guidance → pilot → certification scheme