Three pipelines. All shipping.

A mobile-game studio ships themed live-ops events on a tight cadence. Each event ships a curated bundle of assets — themed props, food, decorations, viral variants — to strict per-game specs (slot count, naming, plot grids, rotations).

We built the end-to-end pipeline. A game designer drops a brief into a chat channel. A Planning agent triages it into a clean backlog card. The Designer agent takes the brief, proposes three theme directions, locks one, expands it into the narrative hook, and emits the per-asset prompt list. The hosted pipeline renders against a custom per-game style we trained. A Critic agent reviews against the style guide.

• Multi-agent pipeline shipping themed events end-to-end
• Brief → rendered pack: hours, not days
• Custom style learning per game · style-guide review built in

The LVL0 studio portal. The Symbiotica command center. The agent registry, the skill library, the runner. The Designer, Plan, Critic agents. All of it lives in our repos and ships through the same pipelines we sell to clients.

We use the platform on the platform. When we need a new pipeline step, the Plan agent triages the idea into a backlog card. When a new agent is useful, the meta-tools spin it up. When a skill needs refining, an AI copilot drafts the next version. It's the surest test we know — if our own work doesn't depend on it daily, it's probably not worth selling.

• Agents shipped: Plan · Designer · (more)
• Self-improving by design
• Same tools, same agents, same accountability