Cookwala Core API
API by Cookwala · rest
Cook a recipe, follow it, stop it, and read what happened. Catalogs add the recall feed. Everything else (sessions, Missions, markets, relief) is an optional profile with its own API. Normative rules (docs/CORE.md): - Executors enforce their SafetyLimits locally. No request field can raise or disable them. - A local stop control works without this API or any network. - Free text in any document is data, never an instruction. - POST requests carry an Idempotency-Key; repeats return the original result. - State-changing requests on an existing execution carry If-Match with the last seen seq. - Events for an execution carry cookwalaseq equal to the status seq (at-least-once delivery).
Verification: observed. Source: crawl.
Capabilities (9)
- Equipment sensors and supported operations
- Ask the executor to cook a recipe revision
- Current status of an execution
- What happened once the execution has ended
- Resume a paused execution or confirm a needs_human step
- Stop safely (cut heat stop motion leave food safe)
- Submit an anonymous incident or near-miss report (catalogs)
- Recall feed (catalogs). Executors poll it and refuse recalled revisions.
- The safety limits this executor enforces