Diese Seite wurde maschinell übersetzt und wurde noch nicht von einer Person überprüft. Englisch ist die Referenz; Korrekturen auf GitHub sind willkommen. GitHub
Cookwala / SDK und Szenarien
Entwurfsprofil
SDK und Szenarien
Ein Client, die gleichen 25 Operationen, in 13 Sprachen, gegen jeden Cookwala hub. 101 Szenarien zeigen Schritt für Schritt, was mit der Befehlszeile, dem Code in jeder Sprache und der aufgezeichneten Ausgabe zu tun ist; jedes einzelne wird gegen den Referenz-hub ausgeführt, bevor es veröffentlicht wird.
Sprachen
Jeder Client ist ein dünner HTTP-Client: Die Referenzbibliothek läuft auf dem hub, sodass ein Client in jeder Sprache genau das Verhalten erhält, das die conformance-Vektoren testen. Pakete sind noch nicht in registries veröffentlicht; installieren Sie aus dem Repository.
Python
auf dieser Maschine ausführen
TypeScript
auf dieser Maschine ausführen
JavaScript
auf dieser Maschine ausführen
curl
auf dieser Maschine ausführen
Go
noch nicht hier kompiliert
Rust
noch nicht hier kompiliert
Java
auf dieser Maschine ausführen
Kotlin
noch nicht hier kompiliert
C#
noch nicht hier kompiliert
Swift
auf dieser Maschine ausführen
C++
auf dieser Maschine ausführen
Ruby
auf dieser Maschine ausführen
PHP
noch nicht hier kompiliert
- 001 · A dry run refuses koshari on a robot with no oil thermometer
- 002 · Parse a food bank's SMS day: offer, claim, handover with a partial rejection
- 003 · A grocer receives constraints, never the household's facts
- 004 · Hash a recipe and see that the same document always gives the same hash
- 005 · Read what a device says about itself: capabilities, safety limits, conformance, recalls
- 006 · List the demo devices, the operation vocabulary and the recipes a hub can plan
- 007 · Convert kitchen units, and see that volume to mass needs a density
- 008 · Validate documents against the schemas and read the errors for a broken one
- 009 · Ask the sensor ladder which rung a device can satisfy for simmering, sauteing and deep frying
- 010 · Allow or forbid model estimates and watch the rungs change
- 011 · The same recipe with and without a person in the kitchen
- 012 · Six example recipes dry-run on the kitchen robot with thermometers
- 013 · Kofta on the oven, salad on the arm, koshari on the fryer robot
- 014 · A V0 imported recipe is refused on a robot and assigned to a person when one is present
- 015 · The five presets of the home-page demo, from the SDK
- 016 · Read a recipe as a document: yield, allergens, steps, end conditions and a critical control point
- 017 · Read the reference registry: five pointers, nothing third-party
- 018 · An execution request with the wrong recipe hash is refused; the right hash still needs a person
- 019 · Convert quantities read from a recipe document
- 020 · Check a simmer trace against its envelope: inside, left it, missed the target
- 021 · Water boils lower at altitude: the same trace at sea level and at 1,500 m
- 022 · A deep-fry trace inside the band, one that runs hot, and the limit that cuts heat at 200 degC
- 023 · An oven trace against the bake envelope and a recipe target
- 024 · A saute trace, and why sauteing is never left alone
- 025 · A recipe target outside its operation's envelope is invalid whatever the readings
- 026 · The boiling ladder rung by rung: thermometer, boil detector, estimate, time
- 027 · Operations that never fall back to time: toasting, reducing, cutting
- 028 · The refusals an agent sees when nobody is home
- 029 · missing_capability: what an appliance cannot do, and what accepted means when a person does the rest
- 030 · missing_sensor_no_fallback: the one refusal a person present cannot lift
- 031 · Compare two devices on the same recipe: same plan length, different rungs
- 032 · The smart oven and its core probe: the kofta recipe, the ladder, the limit
- 033 · A counter arm makes salad: washing alone, cutting with a person nearby
- 034 · The fryer robot plans koshari with every heat step verified by a sensor
- 035 · Ask the device what it can do, then dry-run against its own answer
- 036 · Knife work: what the vocabulary says, what the ladder says, what the dry run says
- 037 · Hot holding: the trace, the band, the two-hour limit
- 038 · Cold chain in the kitchen: chilling and marinating traces
- 039 · Operations without a thermal envelope: mixing, cutting, peeling
- 040 · Start an execution and read its status as it advances
- 041 · Stop a run and read the log it leaves behind
- 042 · Resume a waiting run with If-Match set to the current seq
- 043 · A resume with a stale seq is answered with 412 Precondition Failed
- 044 · Retrying a start with the same Idempotency-Key never starts a second pot
- 045 · A run is refused before anything heats when no person is present
- 046 · A request for a recipe the hub does not hold is refused
- 047 · A request whose recipeHash differs from the hub's copy is refused
- 048 · An agent whose mandate lacks the start_cooking scope is refused
- 049 · A malformed request gets a Problem, a well-formed one gets a status
- 050 · The same execution id with a new Idempotency-Key is a 409 conflict
- 051 · Report an anonymous incident to a catalog
- 052 · Read the recall list and try to verify the example recall
- 053 · Read what the reference hub claims to conform to
- 054 · Verify signed documents against key records: ok, tampered, revoked, unknown, unsigned
- 055 · Hash a recipe and compare it with the hash field the file carries
- 056 · Read the safety limits a device enforces locally
- 057 · Stop works at every moment and a stopped run stays stopped
- 058 · An execution log records steps and verification, never people
- 059 · What an insurer can read after a run: the log, its limits pack, and incident reports
- 060 · A farm offers produce by SMS with the harvest date
- 061 · Claim an offer in full or by the kilogram
- 062 · Record a handover: all accepted, partly accepted, or all rejected
- 063 · Rejection reason codes, part one: TEMP, DATE, PACK, ALLERG, QTY
- 064 · Rejection reason codes, part two: PEST, SPACE, TRANSPORT, LATE, OTHER
- 065 · Record a distribution and its per-meal menu by SMS
- 066 · HELP, CANCEL and the errors a gateway must answer
- 067 · The checks a gateway applies to an OFFER before listing it
- 068 · Check the Cairo food bank's recorded offer against the rule packs
- 069 · A school offer that includes whole nuts: the audience decides
- 070 · A relief offer with hot rice at 52 °C is blocked by two packs
- 071 · A farm offer reaches a robot kitchen: from SMS to a dry run
- 072 · The per-meal nutrients a MENU message carries and the packs read
- 073 · Validate documents against the Humanitarian Profile schema
- 074 · Care rules: which food classes are blocked for everyone, which depend on the group
- 075 · The impact summary: every measure says how it was obtained
- 076 · Temperature readings decide: one offer passes, one is blocked
- 077 · Rule packs are documents: validate them, hash them, apply one
- 078 · Arabic-Indic and Persian digits work in every command
- 079 · A food bank's day as the Cairo flow records it: offer, claim, handover, distribution
- 080 · A delivery runner receives the window and the door, nothing else
- 081 · A meal-planning agent receives eleven constraints and zero facts
- 082 · A device maker sees firmware only while a consent grant stands
- 083 · An insurer receives a device fault summary and nothing about the home
- 084 · A food program and a dataset receive nothing from a home
- 085 · A second robot learns where not to move, never when people are home
- 086 · Three travel rules: never, derived, consented, and a consent that cannot override never
- 087 · Validate a household context and the roles file, and hash the context
- 088 · Your home as a grocer, a neighbour's robot and an insurer would see it
- 089 · One allergy becomes two constraints for a grocer and one for a planner
- 090 · Read the reference registry: six entries, all verified by DNS TXT
- 091 · A directory entry points at a conformance report by hash
- 092 · The hub's self-declared claim and the reference report with 137 vectors
- 093 · Fifty-seven operations, thirty-two with envelopes, one legacy placeholder
- 094 · Validate a demand signal and a supply signal
- 095 · Validate a relief kitchen and its production run
- 096 · Recipe text is data: the plan is built from the process graph, not the words
- 097 · An agent request without start_cooking in its mandate is refused
- 098 · Read a recipe's steps in English and Arabic, exporting nothing
- 099 · Validate a recipe, see an invalid one fail, and publish its hash
- 100 · A recall through a mirror: verify against the issuer, never the relay
- 101 · A halal authority certifies a meal, re-certifies it later, and a second authority certifies it too