Everything installable in Recued is made of three readable units. There is no black box: what a thing does is what its JSON says it does, and you can read that JSON before anything runs.
#Recipes
A recipe is a JSON description of a unit of work: fetch data, compute over it, render or act on the result. Its steps are inspectable one by one — inputs, outputs, the conditions that skip or halt them. Recipes contain no code; they compose ingredients and transforms.
A recipe can run manually, on matching pages, reactively on a self-gating interval, or on a schedule — see Authoring recipes.
#Ingredients
An ingredient is a manifest declaring one operation: an HTTP call, a page action, an AI function, a storage read or write, a call through a named connection. The manifest declares the operation's inputs and outputs, its category and risk tier, and what consent it requires — which is what lets the enforcement boundary reason about it before it ever executes. Ingredients are validated at install time, not discovered at runtime.
#Transforms
Transforms are the pure-function library between ingredients: around fifty deterministic operations over collections, objects, strings, dates, and numbers. They run locally, cost nothing, and always produce the same output for the same input — recipes lean on them so AI is reserved for judgment.
#Packs
A pack bundles recipes, ingredients, and policy into one reviewable install. The pack is where grants attach: which account it may use, at what access level, for which audience. Installing shows you the full contents before anything lands, and individual recipes cannot silently widen what the pack was granted — see Recipes and packs for how browsing and installing relate.
Pack authors pin those contents and disclosures in a versioned pack manifest. Recipe-only version 1 manifests remain supported; new app packs use typed version 2 contents.
#Where they live
The marketplace hosts community-contributed recipes, ingredients, and packs — free to browse and install, forever. The Kitchen is where you author, fork, and test your own. Any recipe URL can be installed — a gist, a friend's link — and every install gets its own credential scope, so two same-named recipes from different sources never share secrets.