Nobody owns a dish
Everything I cook was handed to me. Ownership is the wrong shape for any of it — say what your version is a version of.

There's a recipe on Amanah I called Father's Office Burger.
I didn't invent it. Sang Yoon did, in Santa Monica, and he's famously unwilling to change a thing about it — no ketchup, no substitutions, no apologies.
What I'd been doing for the couple of weeks before I ever attempted it was learning to caramelise onions the Indian way. Butter, very low heat, no sugar, no water, no shortcuts of any kind. Just patience and a lot of hand-stirring so nothing catches. By the time I made the burger for the first time, those were the only onions I knew how to make. They've been the onions ever since.
They come out sweeter than the usual ones. Sweet enough that I want far less ketchup and balsamic than canon calls for. I still put some in. Not because the burger needs it — I'd rather the onions and the bacon carry it — but because it's his burger, and that's what his burger has in it.
So the technique came from one tradition, the dish came from one man, and the balance is mine. I put my name on it. I also put his in the title, because anyone can see what I'm doing and I'd rather say it plainly than pretend.
That deliberate splash of vinegar I don't especially want is the whole argument in miniature. Nobody makes me keep it. It's there as a mark of where the thing came from.
For a while I wondered whether a recipe like that belonged on a platform built around attribution. Then I realised it's the reason the platform exists.
Every few months the food world has this argument. Someone's recipe shows up in someone else's cookbook, the ingredient list is a little too familiar, people take sides, somebody mentions lawyers, and nothing gets settled.
It never gets settled, because we're arguing with borrowed words. Plagiarism. Copyright. Citation. They come from other people's fields and they don't survive the trip.
Here's what I think instead.
A recipe is not the dish
Everything else follows from this one, and almost everybody skips it.
In academia, the paper is the contribution. In journalism, the article is the work. Copy either one word for word and you've taken the thing itself.
A recipe isn't like that. Nobody eats the recipe. It's a set of instructions for making something else, and its whole purpose is to be carried into somebody else's kitchen and done by somebody else's hands. A recipe nobody copies has failed at the only job it has.
Which puts cooking somewhere no other field is. Copying isn't the abuse of the form. Copying is the form working.
And anyway, you can't really copy one
Republish an essay word for word and it's the same essay. Cook my recipe and you've made something else — your stove, your flour, a tomato from a different month, your own hand with the salt, your own idea of what "until golden" means.
There's no identical copy in cooking. Every time anyone makes anything, it's already a variation. A hundred people follow the same braise and produce a hundred different dinners, which is why one correct version of anything falls apart the second you press on it.
Most of the people who built this are gone
Nobody invented braising. Nobody owns the emulsion, or the sofrito, or salting an eggplant before you cook it, or the trick of finishing a sauce off the heat.
Everything any of us makes today sits on thousands of years of work by cooks whose names were never written down. Mostly women. Almost none of them credited, because they were busy feeding people.
Any theory of who deserves credit in food that can't account for them isn't describing cooking. It's describing publishing, with dinner as the subject.
I named this thing after a mother's cooking. I'm not going to turn around and act like the tradition starts with whoever first got a byline.
Her name was Isabel Güemez Ruyan. She was my grandmother. Everyone called her Titi. She was born in Culiacán, in Sinaloa, and spent most of her life in Mexico City, where she and Manuel Gómez Domínguez raised twelve children and kept a table where there was always room for everyone.
She cooked Mexican and Spanish and whatever else caught her attention. She cured her own jamón serrano. She made chorizo español and sobreasada de Mallorca in a kitchen in Mexico City. There's a sopa japonesa in her recipes, and a jambalaya, and a Hyderabadi wedding chicken, and a tomato aspic, and a caviar mousse. She was cooking the whole world out of one kitchen, decades before that was an easy thing to do.
I got the Sundays. Every week there was a feast and it took me in, and that's where all of this actually starts — not the platform, but the wanting to know where a dish came from and whose hands had made it that way first.
She died a few years ago. She hasn't entirely gone.
Forty-eight of her recipes are on Amanah now. She has a profile, at @la_titi. She never had an account and she never will.
That's what I mean about the cooks whose names didn't get written down. Somebody has to write them down. The format all of this runs on is called Ummi, which means my mother, and it isn't branding.
The closest thing isn't a research paper. It's a jazz standard
Everybody plays "Autumn Leaves." Every recording belongs to the person who played it, the composer still gets named, and nobody seriously thinks the fiftieth version stole from the forty-ninth. Each performance really is that musician's — their phrasing, their choices, their work — and the line back to the original is just a true thing that travels along with it.
That's about right for food. There's a Philly cheesesteak the way Pat's makes it and the way Geno's makes it, and there can be fifty more, and every one of them can be honestly and completely its cook's own.
Making your own version was never the dishonest move. Pretending yours came from nowhere is.
So what's actually yours?
Two things.
What you wrote. Your words, your photographs, your explanation of why the pan has to be that hot, the thirty attempts it took to get the ratio. That's work and it belongs to you. The law more or less agrees — a bare list of ingredients isn't protected, but what you built around it can be.
Where it came from. The true story of how your version got here. Not a permission you had to go and ask for. A fact, which ought to survive being handed on.
The second one is the thing nobody's ever been able to write down properly. It's why I built Amanah.
What that looks like here
Nobody owns a dish. You own your version of it. Cook whatever you like. Say what it's a version of.
Credit is a fact, not a permission. Recording that your recipe came from someone else's asks nobody's approval and gives nobody control over you. It's a statement about history, not a negotiation.
A fork isn't theft. A fork with the trail rubbed out is. As far as I can tell, that's the only real offence in cooking — taking someone's work, changing three things, and serving it up like it arrived from nowhere. Not the copying. The erasing.
Adapting is the point. Every recipe here can be forked, and translations are forks too. The one thing I don't allow is an exact copy with nothing changed, because that isn't cooking, it's a duplicate.
Grandmothers count. A recipe's source doesn't have to be another recipe. It can be a restaurant, a cookbook, a region, a stall on a corner, or your mother. Those get recorded like anything else, because "I learned this from my mother" isn't a vaguer claim than a citation. Usually it's a more honest one.
I record. I don't adjudicate. This isn't a court and I'm not going to rule on who invented the brownie. I can give cooks a way to say where things came from, permanently, in a form both people and machines can read. What anyone makes of a particular claim is between cooks.
Why it matters more now
For most of the history of food writing, credit got carried by manners. You mentioned the cookbook. You wrote "adapted from." It was informal and it mostly worked, because the chain ran between people who could be embarrassed.
That's over. Recipes now get read, blended and re-served at scale by systems with no manners to observe and no memory to appeal to. When a machine fuses three cooks' work into one anonymous set of instructions, nobody's been plagiarised in any way a lawyer would recognise, and all three of those cooks have still lost something that was theirs.
It isn't malice. It's that a recipe on the internet has never carried its own history in a form anything could read. The ingredients are structured. The steps are structured. Where it came from sits in a sentence above the ingredient list, if it's there at all, and that sentence is the first thing thrown away.
So I made it part of the recipe. On Amanah, where something came from lives in the page, in the data, and in the open format underneath. It's still there after the copy.
I'm not trying to stop anyone from cooking anything. I'm trying to make the credit stick.
Where I might be wrong
I'd rather say this than have you find it.
Some chefs guard particular dishes closely, and a few would tell you that reverse-engineering someone's signature plate and publishing it takes something real, no matter how carefully you credit it or how many times you burned it first. That's a serious view held by serious people. I don't agree with it. I don't think it's stupid.
There's also no clean line between a dish that's passed into common practice and one that hasn't. Pizza has. Something invented last year in one dining room hasn't. In between is a wide grey stretch, and I can't give you a rule — it gets settled by judgement and by time. Writing down where your version came from is what lets everyone else make that judgement at all.
And plenty of cooks will think this whole framing is wrong. That argument is worth having out loud, which is why I've put my side of it here.
Come tell me about it. Preferably over something you made.