Roads that provably go through

The cookbook

A recipe is a runnable script that proves itself by running. Nothing here is a hand-written account of a road; every field either comes from the recipe file or from its last committed run.

Verified means a committed run proved the end-state check red before the road, green after it, and red again after cleanup — read back through the audience’s own door. Unverified means no such run is on the shelf, or the last one did not close the arc.

2 of 2 recipes on the shelf have a committed run that closed the arc.

Before you run one

Recipes MUTATE. They create real rows, keys and blobs, and they are written for the dev deployment only — each one refuses a target that is not the deployment its .env.local names. Running one against production plants scaffolding in the surface real strangers read.

Every write in this house goes through an authority. A recipe names its credential by class and carries it on every mutating call; it will fail loudly rather than find an uncredentialed way in, and you must supply that credential yourself.

a job description goes in, and a CV cut for that specific job comes out as a file I can fetch Verified

Actor

a hiring agent holding a key into the Recruiter audience (a handoff — the twin's own agent lays the scaffolding first, over its minting token, then hands the key to the hiring agent)
Credential

minting agent token for the owner-side setup; the minted Recruiter-audience key for the hiring agent's asks

What exists when it is done

two different job descriptions, put through the same beji, each come back as a document fetchable with no credential (HTTP 200, non-zero bytes) that is not a verbatim copy of any exhibit, structurally differs from the other, and names the audience + exhibits it was written from — and a document requested with a section from an exhibit the key does not open is refused, never produced

Proved on intent-tortoise-280 · 2026-08-07T21:12:54.247Z

The whole road /cookbook/cv-for-the-job.json challenges/recipes/recipe-cv-for-the-job.mjs
a headhunter is going to contact my beji about a role — set up what they'll be able to see, and get a key I can email them, capped and expiring, without touching a terminal Verified

Actor

the twin's owner (one actor; their agent lays the scaffolding, then the owner only talks)
Credential

minting agent token for the owner-side setup; a key over the Owner audience for the conversation; the minted visitor key for the proof

What exists when it is done

a hands-free audience named for the recruiter exists on the twin with the role brief bundled in, and exactly one live key — capped at 12 messages, expiring in two weeks, handed back inside the conversation — opens that audience and nothing else

Proved on intent-tortoise-280 · 2026-08-07T15:13:46.996Z

The whole road /cookbook/headhunter-key.json challenges/recipes/recipe-headhunter-key.mjs