FACTORY ROADMAP
Spriteworks is being built in public.
The factory begins as a playable prototype. Machines become useful. Sprites gain real capabilities. Research moves outside the factory. Compute becomes real. Then the factory expands.
Every phase represents another part of Spriteworks coming online.
PHASE 01 // FACTORY ONLINE
The first phase establishes Spriteworks as a place.
Before adding complex infrastructure, the product needs a recognizable world, understandable machines and interactions people actually want to use.
The goal is to validate whether users enjoy the core Spriteworks experience.
A persistent pixel-art facility containing the machines, Sprites and Orbio Core.
Scout, Brain, Critic, Degen.
HUNT, BATTLE, ROAST, MUTATE.
/hunt, /battle, /roast, /mutate
Users can select a machine directly or submit a job through the main Factory terminal.
A visible compute resource that powers machine animations.
Local history of previous experiments.
Users can inspect each Sprite and understand its role.
Factory manual explaining Spriteworks.
Users can see what is currently being built.
A new visitor should be able to enter the Factory, understand the four machines, run a job and want to try another experiment. No explanation from the creator should be required.
PHASE 02 // SPRITES GET BRAINS
Phase 02 replaces simulated intelligence with live AI execution.
The visual factory already knows how to show a job being processed. Now the work behind those animations becomes real.
Degen receives an idea. A real model generates structurally different mutations. Brain organizes the result. Outputs become dynamic rather than predefined.
Critic receives real user input. The model examines weaknesses, assumptions and risks. Brain produces a structured critique.
Experiments return predictable data structures so the interface can display results reliably.
Each Sprite receives a clear role, system instructions and behavioral boundaries.
Animations correspond to actual request states: request sent, processing, handoff, response received, complete, error.
If an AI request fails, the factory reacts appropriately instead of pretending the job completed.
Users begin returning because the machines are useful, rather than only because the Factory looks interesting.
PHASE 03 // SCOUT LEAVES THE FACTORY
Scout becomes a real research worker.
Instead of relying only on the user's prompt and a model's existing knowledge, Scout can retrieve current information.
Scout discovers relevant pages and sources.
Important pages can be inspected rather than relying only on search snippets.
Research results show where important information came from.
Where supported, Scout can inspect useful public social information.
Where supported, crypto-related jobs can include relevant onchain information.
HUNT becomes a genuine research workflow.
Users enter a ticker or project ($TOKEN). Scout investigates available information, Critic examines questionable signals, Brain creates a compact brief.
Summary · What's happening · Recent signals · Catalysts · Risks · Sources · Open questions.
HUNT becomes something users use before opening multiple research tabs themselves.
PHASE 04 // THE FACTORY THINKS TOGETHER
Individual AI calls become coordinated multi-stage jobs.
Scout's output becomes Critic's input. Critic's findings become Brain's input. Each stage has a reason to exist.
Information produced by one Sprite is passed into the next stage.
Scout researches both subjects. Critic challenges weak comparisons. Brain synthesizes the evidence.
Critic can challenge unsupported or contradictory findings.
Not every job needs every Sprite. Spriteworks chooses the smallest useful workflow.
Where useful, multiple research tasks can execute simultaneously.
Users can inspect what Scout found, what Critic challenged and what Brain concluded.
Using several Sprites produces visibly better results than sending the same prompt to a generic chatbot once.
PHASE 05 // ORBIO CORE ONLINE
The Orbio Core stops being a simulated game mechanic and becomes a representation of actual AI capacity used by Spriteworks.
Spriteworks routes supported model/tool requests through secure server-side Orbio infrastructure.
The Factory can display a real available AI balance where technically appropriate.
Jobs consume actual AI resources.
Completed experiments can display the resources used to perform them.
The visual Orbio Core reacts to real jobs.
Factory statistics can show jobs completed, AI usage, machine usage and Sprite activity.
If Spriteworks launches through Orbio, integrate the relevant project infrastructure according to the live launch terms at that time.
If applicable under the final launch setup, project creator fees can contribute toward Spriteworks' AI capacity through Orbio's mechanism. Always reflecting real data and current protocol rules.
The Orbio Core becomes a functional part of Spriteworks rather than visual lore.
PHASE 06 // EXPAND THE FACTORY
Once the original four machines are useful, Spriteworks can expand.
Introduced only when a genuinely different role is needed. Possible roles: Builder, Verifier, Watcher, Archivist — conceptual examples, not confirmed features.
New experiments can be added around proven user behavior.
Users can generate public links for useful experiments.
Optional accounts can preserve work across devices.
Move beyond local browser history.
Show which machines and Sprites are doing the most work.
Users can suggest machines they want built.
Add new research capabilities where they improve existing workflows.
The Factory grows because users repeatedly ask it to perform new kinds of work.
PHASE 07 // SPRITEWORKS ARCADE
Once Spriteworks has useful infrastructure, the Factory can become a place for stranger AI-native experiments.
Spriteworks is being built experimentally. Features can move, change or disappear based on what people actually use.