Cookwala / Roadmap
Now, next, later
Every item carries a status: done, in progress, planned, not yet funded. Gates come from the action plan. Nothing moves from planned to done without the evidence named. Maintained in docs/ROADMAP.md.
Now (this release)
| Item | Status |
|---|---|
| Core 0.2: envelopes, sensor ladders, refusal, local safety limits, signed records, agent rules | done draft, under review |
| 137 conformance vectors (Core and profiles); conformance report format | done |
| Reference library, Python package and CLI, TypeScript types, MCP server, reference hub, ROS 2 interface package | done editable and source installs; package registries next |
| Nine example recipes in English and Arabic | done V1: structured, not field-verified |
| 2,042 fifi.cooking recipes imported, names in 25 languages, text in Arabic and English | done V0: described, not machine-verified (RFC-0009); four collections await the founder's licence confirmation Since 2026-10-05 the four credited collections publish structured facts only (no step text) until their rights are confirmed in writing. |
| SDK clients in 13 languages; 101 executed scenarios | done Go, Rust, Kotlin, C# and PHP not yet compiled on CI |
| Samples: clients, agents, orchestrators, gates, recovery and reporting in Python, JavaScript, Java and C#, with packages for 18 channels and functions for four clouds | done published on PyPI, npm, Maven Central, NuGet, Homebrew and GHCR; the other channels are in preparation |
| The site in six languages; core documents in those six | draft site pages in English and Arabic by hand; French, Spanish, German and Portuguese by machine, labelled; documents machine-translated and labelled, English is the reference; 18 more languages translated but not yet published |
| Humanitarian Profile 0.2: surplus to plate, SMS grammar and parser, four worked flows, impact summaries, pilot protocol, concept note | done draft |
| Rule packs (basic, care for vulnerable groups, school meals, sodium reduction) with a review template | done drafts awaiting professional review |
| Household Context Profile with a 139-type facet registry and disclosure vectors | done draft |
| Registry and directory API; honest registry.json and directory.json | done static |
| Kitchens and production runs; supply signals | done experimental |
| Federation rules and relay vectors | done draft |
| Four simulators with the protocol on and off | done illustrative |
| Website in English and Arabic, whitepaper, deck | in progress |
Every planned item has a gate: the one thing that has to happen first. If you can open one (a reviewer, a device, a food bank, funding), say so in GitHub Discussions; a direct address will follow from the founder.
Next (within about a year, as resources allow)
| Item | Status | Gate |
|---|---|---|
| Food scientist review of the operation envelopes | planned | reviewer agrees |
| Dietitian and food-safety officer reviews of the four rule packs | planned | reviews filed; packs move to reviewed |
| Data-protection impact assessment of the household profile | planned | reviewer agrees |
| A food-bank pilot (12 weeks, pre-registered, independent evaluator) | not yet funded | partner and funding |
| Agent-safety benchmark results for several model families | planned | runs published with method |
| pip install cookwala wheel and @cookwala/sdk on npm | planned | packaging that bundles vocabularies and schemas |
| Publish the samples to the remaining channels: Chocolatey (in moderation), Scoop, an apt repository, RPM, AUR, apk, conda-forge, Snap; Artifactory stays bring-your-own-instance | planned | registry accounts and namespaces (backlog D-12) |
| Registry service (validate, publish, tombstones) | planned | a worker and namespace proof |
| First device maker implementing the Core API against the reference hub | planned | one maker agrees; report published |
| Conversion of the first fifi.cooking collections | planned | founder decides rights per collection |
| Core 0.3 from device feedback | planned | two implementers' feedback |
| Steering committee | planned | three independent adopters or two implementations |
Later
- A real device cooking a Cookwala recipe, unedited, on video: not yet funded; needs a device partner
- Certification scheme with an independent certifier: no certifier engaged
- Neutral foundation for the specification, trademark and mark
- Contributor network: consented recordings of real recipes with credit
- Demand and supply signals published by programs and cooperatives, after competition-law review
- "Cook in simulation" benchmark
- Digital Public Good recognition for the Humanitarian Profile, after pilot evidence
- Cross-region relief flows and clean-cooking effects in the world simulator
What we will not do
Collect personal data; publish numbers without a method; name a partner before it agrees; claim a certification that does not exist; put household data on any ledger; build a central orchestrator that kitchens depend on; claim to end hunger.
Kill and pivot rules
If two external review rounds fail to produce a device maker or a pilot partner, Cookwala narrows to the Humanitarian Profile and the recipe format. If a pilot shows less than a 5 % gain, the results are published and the profile redesigned before any scaling.