AT THE CODE presentsFood · Creativity · Tech
Inside the buildTHE SIGNAL

What happens when one food idea gets two different answers?

Inside Cook-Off · AT THE CODE Recipe Builder

Two recipe ideas.
You decide.

One brief. Two independent concepts. A decision made by the person who will actually cook it—not by the name of the AI behind it.

The Signal ·
Project introduction · Early access

You have ingredients, a craving or an idea for food that does not quite exist yet. You could ask for a single recipe and stop there. Cook-Off asks a more interesting question: what happens when you compare two different directions?

Cook-Off is the comparison feature inside AT THE CODE Recipe Builder. Its core design gives two independent AI models the same food brief and presents the concepts as Model A and Model B. The labels keep the attention on the recipes. The creator chooses what deserves a real-world test.

Crown Bites: two possible directions

Example · Model A

Saltfish Crown Bite

Saltfish and callaloo inside a plantain shell, finished with guava-lime dip.

Example · Model B

Oxtail Crown Bite

Reduced oxtail inside a plantain shell, with a dark-fruit finishing glaze.

Existing concept examples from the app. No fresh AI round was run to produce this article. The display is not a claim that these dishes have been physically tested.

Start with a brief that means something to you

A useful brief can describe the food, the occasion and what matters most. Is it a family dinner? A handheld party snack? Something using ingredients you already have? The clearer the starting point, the easier it is to judge the suggestions against it.

Example brief to try:
“I want a handheld party snack using plantain, saltfish and callaloo. Give it a Jamaican-British influence, keep the method realistic for a home kitchen, and explain what I should test first.”

This is an example prompt, not a tested recipe or a promise of what the AI will return. Your own brief can be completely different.

How the idea is meant to move forward

  1. Give both models the same starting point.Describe your ingredients, idea and constraints. The comparison should begin with the same brief, not two different questions.
  2. Compare the concepts before picking a favourite.Look at ingredients, method, effort and whether the result sounds like something you would actually want to make.
  3. Choose a direction and question it.The Cook-Off design includes critique and a record of the chosen direction. A confident-sounding idea is still open to challenge.
  4. Test it in a real kitchen.Record what worked, what failed and what you changed. Recipe Builder’s wider journey is about creation, testing and improvement—not treating generated text as the finished product.

You are still the creator

AI cannot taste your food for you. A concept may sound exciting and still need changes to the texture, timing, filling or method. The value of comparison is having options to assess, not being told that either answer must be right.

Optional heritage and inspiration choices are part of Recipe Builder’s interface. They give someone a way to describe the connection they want a dish to have. A flag or a generated description does not make an idea an authoritative version of a culture’s food; the creator’s knowledge and choices still matter.

A concept is not a sign-off. Treat AI suggestions as starting points. An idea, a presentation score or a creation record does not certify food safety, originality or readiness for commercial sale.

Part of a bigger building story

Cook-Off brings the creative side of AT THE CODE into view. Alongside the books, HEARD, Build It Live and this magazine, it asks what a person can build when an idea is given room to develop.

The app is an early-access project with further release work under way. This feature is an introduction to its purpose and workflow—not a claim that every planned feature is finished. Follow the access information in the app for the version currently available.

Open AT THE CODE Cook-Off ↗Read Farrah’s building story →