orsel.manifest/1), the domain, a version number and the actions. Each action has an id, a name, a description, a typed input schema and output schema, and a risk class: read, write, sensitive, irreversible or financial. It also lists preconditions, postconditions (the checks that decide whether a run succeeded), the auth it needs, how it is made safe to repeat, and rate hints.api, webmcp, replay, dom, agent. Each tier has its requests or steps and the fields to extract, with timeouts. A recipe also carries canary inputs, the origins it may reach (only the site's own), who published it and how it was made.candidate, verified, degraded, quarantined or revoked, and it moves only when checks pass or fail. A candidate can be run only by the organization that made it.verify recomputes.