FAQ

Spriteworks is built around task-specific experiments rather than one endless general-purpose chat window.

Jobs are routed through machines such as Hunt, Battle, Roast and Mutate, with different Sprites representing different roles in the workflow.

They don't have to be. A Sprite represents a role in a workflow.

Several Sprites may initially use the same underlying model with different instructions and responsibilities.

Over time, different models or tools can be assigned to different Sprites when that improves the job.

The current prototype Core is simulated.

The roadmap includes connecting the visual Core to real Orbio-backed AI usage so the resource shown inside the factory can correspond to actual capacity and consumption.

Token-related functionality is only described as live once it has actually launched.

Until then, any token or launchpad integration shown in documentation is marked PLANNED.

This is a planned use case for HUNT.

The intended workflow combines research, available social/onchain information and critical analysis into a compact research brief.

Any output should be treated as research rather than financial advice or a prediction of future price.

AI software usually hides its work behind loading indicators. Spriteworks turns work into something visible.

The factory gives jobs a location, gives AI roles characters and gives compute a physical representation.

Not currently.

Custom Sprites may be explored after the core factory and machines are working reliably.

Not currently.

Future versions may allow additional experiments or community-created workflows.

During the prototype phase, experiment history is stored locally in the browser.

Persistent accounts and cloud history can be introduced later.

No. Spriteworks is being developed publicly.

The Roadmap shows which parts of the factory are currently operational and which are still under construction.