What this is

One order a day

At 06:00 UTC a language model invents a single baking recipe. That recipe goes up here, and that is the entire day’s output. Everyone who visits gets the same one. Tomorrow it is replaced.

There is no feed. There is no recommendation engine quietly learning what you like. There is no eleven-hundred-word story about somebody’s grandmother sitting between you and the ingredient list. One recipe. Everyone. Same day.

The machine has never eaten anything

This is the part worth sitting with. The thing writing these recipes has read more of them than any person ever will, and has never tasted a single one. It knows that gluten develops and that gelatin sets and roughly how long a laminated dough wants in the fridge. It cannot know whether miso belongs in a pretzel dip, because knowing that requires a tongue.

So it guesses. Confidently. In writing. Every day.

What comes out is usually competent, occasionally brilliant, and sometimes genuinely alarming. All three are the point.

The cursed scale

Every recipe is scored from 3 to 99 on how far it has drifted from anything a person would have thought of. Nothing about the score is a matter of opinion — it is computed from the recipe itself, at build time, from named findings:

• Culture collision — how many distinct cuisines got welded together in one dish.
• Savoury breach — ingredients that have no business inside a dessert. Miso in a brownie scores here.
• Constraint stack — vegan and keto and no-bake, all at once.
• Ingredient sprawl — the shopping list outgrowing the idea.
• Name sprawl — every extra clause in the title is another idea bolted on.
• Labour demand — advanced technique plus a multi-day timeline.
• Temporal dissonance — a Christmas recipe issued in June.
• Physical contradiction — a no-bake recipe that calls for laminated pastry. These happen.

Each recipe page shows exactly which findings fired and what each one cost. The machine has to show its working.

Almost none of these have been made

Every recipe here works on paper and has never met an oven. That is not a disclaimer — it is the interesting bit. There are hundreds of complete, coherent, entirely theoretical recipes on this site, and a first is still available on nearly every one.

If you make one: claim it. Post a photo — a failure counts and is frankly better material. Once it is checked, your name goes at the top of that recipe and stays there. There is exactly one first bake per recipe, and it does not expire, and it cannot be bought.

Please read the method before you shop

Nothing here has been kitchen-tested by a human. Treat every recipe as a confident first draft written by something that cannot taste:

• Read the whole method before buying anything.
• Check your own allergens. The machine does not know what is in your kitchen or your body.
• If a step looks wrong, trust yourself over the machine. You have eaten food. It has not.
• Baking times and quantities are the most likely things to be off. Watch the bake, not the clock.

How it is built

A static site — Hugo, Tailwind, no database, no tracking, no accounts, no cookies. The daily recipe comes from a scheduled GitHub Action. Bake claims arrive as GitHub issues and get baked into a data file. The whole thing is open on GitHub; the scoring algorithm is a single template you can read and argue with.

The share cards, the cursed scores, the counts of what has never been made — all of it is computed when the site builds and then served as flat files. Nothing on this page is watching you.