Recipes

Open Data → Recipes in a project, between Checkpoints and Profiles, to browse registered ANS Recipes. Search by name or ANS URI, filter executable Recipes and source packages, and use the shared pagination controls.

Each name has one catalog row and a Versions count. Open the name to see its published immutable manifest Revisions, then select a Revision to inspect its full ANS URI, pinned manifest SHA-256, source commit, file count and size. Overview shows the entrypoint, Runner contract and parameter defaults/schema. Files shows the published tgz package with its filename, compressed size and SHA-256. For executable Recipes, expand Package contents to inspect internal paths, sizes and hashes. Source packages show only the tgz and aggregate file count/unpacked size; they do not store a per-file inventory in new manifests or offer an expandable member list. Files in package and Unpacked size describe the contents, separately from the compressed package. If no published package metadata is available, the page states that explicitly. Dependencies links to pinned Recipes readable in the same project. Source packages have no execution entrypoint.

The page is read-only: it does not publish Recipes or submit Jobs. Historical Artifact inputs remain Artifacts. An unconfigured or unavailable catalog displays an error; no matching entries display an empty state.

New publications use manifest schema envloop.recipe/v1. Historical revisions retain their original schema and digest; Overview displays the schema recorded in that revision.

Recipe versions use the full manifest SHA-256. They do not create a semantic version or a mutable default. Historical Revision links remain readable.