Building and Launching on Spawn

Spawn has two connected workflows. Designers create reusable Blueprints. Launchers use those Blueprints to create Worlds.

One person or team can fill both roles.

Designer workflow

Define the idea

The Designer describes what the Model represents, who should use it, which decisions or experiences it supports, and what it explicitly does not claim to do.

Specify the Model

The Designer defines the state, transition rules, inputs, outputs, randomness, tick process, and configuration boundaries.

Document provenance

The Designer identifies datasets, references, licenses, transformations, assumptions, and original design choices.

Build and test

The Model is implemented in a supported runtime and tested for replay, boundary behavior, invalid inputs, resource usage, checkpointing, and recovery.

Benchmark

Spawn Labs measures representative execution cost and produces a compute profile. A Model cannot be priced honestly without this step.

Submit a Blueprint

The Designer publishes a versioned package for review. A Blueprint can progress through the following states:

• DRAFT — incomplete or still changing;
• REPLAYABLE — deterministic replay demonstrated where applicable;
• TESTED — required technical tests pass;
• LAUNCHABLE — satisfies the interface needed to create a World.

These labels describe implementation maturity. They do not certify scientific truth.

Launcher workflow

Choose or commission a Blueprint

The Launcher selects a Blueprint from the Model Store or works with Spawn Labs and a Designer to build a custom Model.

Configure the World

The Launcher chooses values within the Blueprint's permitted ranges, identifies the data snapshot, defines participation rules, and decides whether the World uses Seasons.

Design the economy

The Launcher declares:

• whether a $[New Token] is needed;
• what the token does;
• whether participants put $SPAWN or another asset at risk;
• how rewards and losses are calculated;
• which fees pay the Designer, Launcher, runtime, verifier, and protocol;
• what liquidity protections apply.

Test the complete World

The Launcher runs the exact configuration across many seeds and adversarial scenarios. Spawn Labs tests the interface, contracts, runtime budget, pause behavior, and settlement limits.

Fund and publish

The Launcher pays any disclosed $SPAWN creation requirement, funds initial $ETH runtime costs, and supplies any required liquidity or prize reserve.

Any $SPAWN creation requirement and contract flow will be published with the verified production contracts.

Operate the World

After launch, the Launcher manages the community and product within the immutable or predeclared rules. The Launcher cannot silently change a frozen Season configuration.

Spawn Labs support

Spawn Labs helps Designers and Launchers with research, specification, code, tests, benchmarking, interfaces, visualizations, contract integration, and deployment preparation.

AI assistance accelerates the workflow. Human review remains necessary for scientific claims, security, law, economics, and high-stakes decisions.

Current availability

Applications may be collected before the production Launchpad is live. Applying does not deploy a World or require a token transaction.