Cookwala / Registry and directory
Draft profile
Find and publish, under names that prove who published
A registry holds pointers, not content: what exists, who published it, which exact version, and its hash. Names are proven by DNS or a code-host account; versions are exact; withdrawn entries stay as tombstones. Anyone may run a registry. This one lists only what exists in the repository today, and says so.
Browse
| Name | Kind | Version | Status | Verified | Description |
|---|---|---|---|---|---|
| Loading /v1/registry.json… | |||||
Source: /v1/registry.json. Nothing here is a third-party product. When a device maker, a recipe publisher or a program publishes, it appears here under its own proven namespace.
Recipes in the reference catalog
Loading recipes…
The full index, with 2,042 recipes imported from fifi.cooking at V0, is at /recipes/. Nine example recipes at verification level V1 (structured; not simulated or field-verified), in English and Arabic. They exercise boiling, simmering, toasting, deep-frying with an oil sensor, baking with core-temperature control points, holding, cooling, chilling and no-heat steps. The recipe format.
Directory of organizations
Organizations that asked to be listed: device makers, catalogs, registries, food banks, community kitchens, school and relief programs, farms and cooperatives, grocers, restaurants, recipe publishers, certifiers, research labs, health bodies, governments, insurers, translator communities. Listing is not endorsement, certification or partnership. A conformance claim points to a published report, never a badge.
| Organization | Roles | Country | Verified | Conformance |
|---|---|---|---|---|
| Loading /v1/directory.json… | ||||
One entry: the operator of this site. Nobody else has asked yet, and nobody is listed who has not asked.
Publish
Validate locally with the same checks the registry runs.
cookwala validate cookwala hash my-collection/recipe.cookwala.jsonProve your namespace once: a DNS TXT record
cookwala-verify=<token>on your domain, a/.well-known/cookwala-verifyfile, or a GitHub or GitLab OIDC token from a CI job in your account.Publish the entry.
curl -X POST https://cookwala.ai/v1/registry/publish \ -H "Authorization: Bearer $COOKWALA_PUBLISH_TOKEN" -H "Content-Type: application/json" -d @entry.jsonnext The publish and validate endpoints are specified (registry.openapi.yaml) and come with the registry service. Today entries are added by pull request to
site/v1/registry.json.
Rules
- Names:
<reverse-dns-namespace>/<name>, lower case, 3 to 200 characters. - Versions exact (
1.4.2); ranges andlatestrejected. - Every version records its artifact's sha256; recipes also carry their own document hash.
- Lifecycle: active → deprecated → recalled (also in the recall feed) → deleted (tombstone). Names are never reused.