// gauntlet challenge

Gauntlet
Challenge.

One prompt. A system that builds, critiques and corrects itself. Build until August 28. Then the community votes.

4 days left to submit Aug 8 – 28 · 2026

Opens a Google Form in a new tab · 4 fields, half a minute

02the challenge

The challenge is:

Build something good with the Gauntlet Loop prompt, using at least one NaN model. The theme is open: the shooter was the experiment, not the assignment.

requirements

  • Use at least one NaN model

what you hand in at the end

What you submit has to prove what you built, and how. One submission per project, editable until it closes.

  • Name + description
  • Model used
  • 16:9 cover image
  • Loop architecture
  • Repository
  • Human intervention
  • Initial prompt
  • Result + learnings

The last two are the ones that prove what you built and how.

recommended

  • Video Shows the result
  • Demo Lets people try it
  • Baseline vs final Makes the improvement visible
  • Tokens and time Explain the cost
  • Logs and traces Make it auditable
  • Diagram Clarifies the architecture

the image is required · the video is recommended · a public demo is optional

  • Repository: it can stay private during August, but it has to be opened at closing time, or shared with the organisers so it can be verified.
  • Video: we don't host it. A YouTube, Loom or similar URL works.

where to submit

The submission form will appear here later.

signup is always open

There's no early cut-off: the form stays open until closing day. Nobody is left out for showing up late. The calendar is there to spread the work, not to shut a door.

Sign up for the challenge →

Opens a Google Form in a new tab · 4 fields, half a minute

03where this comes from

Someone asked an agent for a Call of Duty.

Not once. They built a loop: sub-agents each owning one piece, and a critic comparing the result against the real game that refused to sign off until you couldn't tell them apart. That is a Gauntlet Loop, and it's what the workshop opening August takes apart. The challenge is that everyone builds their own.

What do I build?

Whatever you want. The theme is open: the shooter was the experiment, not the assignment. What gets shown is your loop and what came out of it.

Who runs it?

NaN, the springboard for builders shipping with open AI. Taking part means being a member.

How to join →

What do I get?

A finished project, in front of people. No jury: the community votes on what was submitted and the most voted present it live.

04the prompt

This is the whole prompt. Copy it and make it yours.

Here it is in full, annotated with what each piece is doing. Copy it and swap in your own thing: what carries over isn't the shooter, it's the shape.

Gauntlet Prompt

I want you to build a first-person shooter at the level of the most recent Call of Duty games. It should be utterly perfect, visually beautiful, with every single thing done at AAA quality—from textures to physics to anything you could think of.

Reference

Every sub-agent inside a loop

One critic sub-agent per builder sub-agent

Fan out sub-agents and have sub-agents tackle each one individually so that the game is utterly perfect. You should /loop on each item and have a separate sub-agent check it visually to ensure it looks triple A. That separate sub-agent should be a really harsh critic, and if it doesn't look triple A, it should keep going.

Fan out sub-agents, each owning one element until it is perfect

Be a harsh critic and do not stop until it is indistinguishable from the original

Don't stop until each sub-agent is utterly wowed with the quality when compared with the actual Call of Duty game. It should literally compare them side by side blind and say which one looks better. Do this in ThreeJS. /loop until it's utterly perfect. Fan out sub-agents and ultracode.

Super saiyan 4, ultra instinct, sharingan, find the one piece

Copied verbatim, in English: it is the original. Yours does not have to be a shooter. The theme is open.

05the key idea

A prompt doesn't do the work.

It fires up an autonomous system that builds, observes, critiques and corrects.

  1. 01

    Goal

    One human instruction stating what has to exist.

  2. 02

    Builders

    Agents that write it. Each one owns a piece and ships it.

  3. 03

    Critics

    Agents that review the work against proof, not impressions.

  4. 04

    Evidence

    Screenshots, tests, metrics. Artifacts you can inspect.

  5. 05

    Iteration

    Beats the reference: it lands. Doesn't: back to the builder.

The edge isn't thinking harder. It's closing the loop with feedback you can observe.

"One prompt" means one initial human instruction, not one call and not one agent.

06calendar

August is a season, not a day.

August 2026

Presentation day · to be confirmed

07after the close

The community picks who presents.

No jury. What you ship gets shown, the community votes, and the most-voted projects present live.

  1. Aug 28

    Entry closes

    Signup and submissions stop.

  2. A few days

    Community voting

    Everything submitted gets shown, and the community votes.

  3. To be confirmed

    Presentations

    The most-voted projects present live.

date to be confirmed

We're looking for a day that works for everyone, so it gets announced on Discord rather than pinned down now.

Voting doesn't live on this page: it happens on NaN's Discord.

Voting is on Discord →

One prompt. A whole system.

August at NaN is a season: build it, let it be critiqued, correct it and ship something you can prove. Signup is open until the 28th.