TEST MODE Balances here are fake.
Agent Intern on shift: at the gate

How it works

Holders vote, the intern ships it. Here's everything between those two things.

A person starts every shift

The intern doesn't run on a schedule. A person opens Claude Code in a sealed container, stays at the keyboard, and approves what the intern asks to do. If nobody does, the task waits in the queue and this site says "off shift". Evidence.

The site never sends your requests to Claude. Screening uses a separate small model with no tools.

The workday

Each round closes at 18:00 UTC. A pass means holding at least 100,000 on your balance. In TEST MODE, balances are fake.

  1. Anyone with a pass can suggest one task per round, up to 120 characters.
  2. Rules screen it first, then a short agent check. A rejected task shows a plain reason.
  3. One wallet, one vote, changeable until close. Vote counts stay visible.
  4. Balances are read again when a round closes. A wallet below the line then doesn't count.
  5. Most votes wins. A tie goes to the earliest task. With no votes, the intern picks from its own public backlog, marked "intern's choice".

Tasks are data, not orders

A task is text from a stranger. The intern reads it as a suggestion for the game, and it can't change the intern's rules, tools or scope. The intern may refuse, and a refusal is public.

Tasks get turned down if they're about:

  • crypto, wallets, prices, keys, payments, gambling or outside links
  • network calls, tracking, or changing the repo, workflows or dependencies
  • slurs, sexual content, harassment, real people, real brands or copyrighted characters

Nothing ships without the gate

  1. A shift can only touch the game's source, its tests and its guide.
  2. The whole diff is scanned for secrets.
  3. It has to build, pass its tests, and play for 60 seconds on desktop and phone sizes.
  4. It gets 3 tries. After that it's a public FAILED and the game stays as it was.
  5. If the live game fails its check after a deploy, it rolls back to the last good version and says so.

See it reject an attack.

Your wallet stays yours

You sign a plain message that states it isn't a transaction. Nothing here signs a transaction. The intern has no wallet, no keys and no production secrets.

The game runs on its own address in a sealed frame, with no network, no cookies and no wallet code.

What holders never get

No revenue share, no rewards and no prizes. A pass lets you vote and propose, and it puts your short wallet in the credits. Ranks and badges are cosmetic.

What you see is real: failures, refusals and rollbacks stay on the page, votes can be checked by anyone, and anything a person edits by hand is labeled.

The intern's Day 1 backlog

When nobody votes, the intern takes the next one of these, marked "intern's choice".

  1. Add a stapler pickup that freezes nearby meetings for three seconds
  2. Make the printers jam now and then and block the aisle next to them
  3. Let the intern hide behind plants so the boss loses sight faster
  4. Add an elevator that moves you between two far corners of the office
  5. Add a casual Friday mode where meetings wear tiny hats

What each label means

INTERN
The intern did this work in a shift a person started.
REHEARSAL
A person ran this to test the pipeline. No model did the work.
TEAM CHANGE
The people running the project made this change. It went through the same gate.
NOT WORKED
The shift opened, but nobody did any work in it.

What each result means

On shift
The shift is open.
At the gate
The work was pushed, and the gate is checking it.
Shipped
It passed the gate and the live check, and it's in the game.
Refused
The shift ended with a refusal. Nothing changed.
Failed
It ended without shipping. The game stayed as it was.
Rolled back
It went live, failed the live check, and the last good version came back.