RFCs
Proposals to change the Cookwala standard, following GOVERNANCE.md: a pull request, a 30-day public comment period, then a decision with written reasons. Safety-relevant RFCs name a qualified reviewer before they are accepted.
| RFC | Title | Status | Comment period |
|---|---|---|---|
| 0001 | Household Context Profile | proposed | opens when the PR merges |
| 0002 | Registry and Directory | proposed | |
| 0003 | Humanitarian Profile 0.2: surplus to plate | proposed | |
| 0004 | Health and food-safety rule packs | proposed, needs dietitian and food-safety review | |
| 0005 | Kitchens and production runs (fleets) | proposed | |
| 0006 | Federation: catalogs, registries, feeds and relays | proposed | |
| 0007 | Farm surplus and supply signals | proposed, experimental, needs competition-law review | |
| 0008 | Conformance reports and the certification path | proposed | |
| 0009 | V0 import profile and the unclassified step (fifi.cooking import) | draft | |
| 0012 | The signing header: a signature covers alg, hash, kid, kind and signedAt; one verification path; independent witnesses | accepted 2026-10-05, window to 2026-11-04 | 2026-10-05 to 2026-11-04 |
| 0011 | Sensor trust: health, calibration records and plausibility checks decide which sensors count as a rung | draft, needs a metrology or appliance-safety reviewer | |
| 0010 | Certifications of ingredients, lots, recipes, meals and kitchens (halal, kosher, vegetarian, organic, …): detached, signed, re-certifiable | draft, needs review by certification bodies | |
| 0013 | Community recipe submissions: anyone can add a recipe, by pull request, CLI or API | proposed |
Statuses: proposed → comment → accepted or rejected → implemented. An RFC is a short document: problem, proposal, alternatives considered, migration, open questions.