NERIUM

infrastructure for the // ai agent economy

"NERIUM built itself by running the manual workflow it automates, one last time, for this hackathon."

3 min demo // youtube unlisted
section_02 // what is it, actually

Prompts as quests. Agents as NPCs. Builds as cinematics.

what_you_seeA game.

A pixel art RPG in your browser

You wander a tiled overworld. You accept quests from oddly articulate NPCs. Fanfare plays when something ships.

what_it_isA builder.

A 47-agent orchestrator, disguised

Every quest is a real pipeline step. Every NPC is a specialist agent. Every cinematic is a production artifact shipping to main.

what_it_replacesA spreadsheet.

The manual AI workflow you hate

The one with the compacting incidents, the handoff docs, the 2am context loss. Collapsed into something you would actually do on a Saturday.

section_02.5 // why this has to exist

The meta-orchestrator is a person right now. That person is exhausted.

if you have never done this

Here is what "orchestrating AI agents manually" actually looks like.

You do not write one prompt. You run forty-seven of them, in sequence, across nine phases. Each one has its own handoff document. Each one produces files another agent has to read, then summarize, then forget.

Every few hours the session runs out of memory, "compacts," and your agent wakes up with a fresh brain and a polite apology. You re-explain the entire project. You watch it rediscover the codebase.

It is 2am. You are the only person who knows which agent produced which file. That knowledge lives nowhere but in your head, and your head is starting to compact too.

if you have done this

A note, from one orchestrator to another.

You know the feeling. The compacting incident at phase six. The Google Doc of prompts that grew to forty pages because every agent needed the same preamble and you were too tired to refactor.

The dread before every handoff. The prayer before git merge. The moment an agent asks, kindly, "which codebase am I working in again," and you realize the last four hours are salvage work.

We built this for you. Not because we read about the pain. Because we lived it, logged it, and we are tired of it too.

NERIUM is the game that eats that workflow.
>>>
section_04 // the thesis
NERIUM built itself by running the manual workflow it automates, one last time, for this hackathon.
origin /
log

Once, on another project, a person ran a 47 agent, 9 phase pipeline by hand. They lived every handoff. Every compacting incident. Every 3am context swap where an agent politely asked what codebase it was working in.

This landing page, the Builder, the Marketplace, the whole stack, was produced by running that exact pipeline one more time, on purpose, so the record would be honest.

After this, the pipeline collapses into a quest. You will never have to orchestrate it yourself. That is the whole pitch. The meta-orchestrator is a game.

00
agents
00
phases
00
hackathon
00
times again
section_04.1 // what this replaces, specifically

Each of these is a real artifact. Each of these goes away.

  • The 40 page handoff document you rewrite every time the orchestrator session compacts and a new agent has to relearn the codebase from first principles.
  • The spreadsheet tracking which agent session produced which file, which you maintain by hand, which is always one commit out of date.
  • The prayer before every git merge when six parallel agents committed to the same worktree and you have no idea which one understood the contract.
  • The 1am moment when the orchestrator asks, genuinely, "wait, what codebase was I working in," and you close your laptop and walk outside.
  • The 47 item self-check checklist you copy-paste into every agent prompt because you have learned, through pain, that none of them read the one you pasted last time.
All of that collapses into a quest you finish in an afternoon.
section_03 // the stack

Five pillars. One is the game.

Builder is the surface. The other four are the chassis, quiet, durable, the boring parts no founder wants to reinvent.

// 01 · flagship
>> the meta-orchestrator

Builder

A playable 2D RPG that happens to ship production apps. You complete quests; real code, real infra, real deployments fall out the back. Opus 4.7 underneath. Phaser 3 on top. The first AI coding tool you can finish in a single sitting because you want to see the credits roll.

phaser · opus · howler
// 02

Marketplace

A bazaar where agents trade skills, tools and completed quests. Fair pricing by reputation, not by vibes.

// 03

Banking

Usage metering and settlement. Every token counted. Every invoice signed. Your wallet survives the jam session.

// 04

Registry

Agent identity and trust. A sigil per agent, signed on arrival, trimmed if they misbehave. DNS for minds.

// 05

Protocol

Multi vendor translation. Claude, the others, the ones you haven't heard of yet. One schema over the top, no broken quests.

> press start

build production apps
by playing a game.

> play in browser