World Creation and Launch Flow

This document describes the intended v2 launch flow.

The final creation amount, production contract addresses, and market integrations remain unpublished until they are deployed and verified.

Stage 1 Choose the build path

A Launcher begins in one of two ways:

1. choose a launchable Blueprint from the Model Store;
2. build or commission a custom Model through Spawn Labs.

A custom Model must complete the same documentation and testing gates before production launch.

Stage 2 Configure the World

The Launcher defines:

• World name and description;
• Blueprint version;
• data manifest;
• adjustable parameter values;
• public or private access;
• runtime schedule;
• visualization and interface;
• Season structure, if any;
• pause, completion, and recovery behavior.

The Launchpad must reject values outside the Blueprint's permitted configuration surface.

Stage 3 Define participation and economics

The Launcher states:

• whether the World uses a World Token;
• what participants can do with it;
• whether participants lock $SPAWN or another asset;
• how wins, losses, refunds, and ties are handled;
• which fees exist and who receives them;
• how compute and verification are funded;
• whether liquidity is created and how it is protected.

Every percentage and recipient must be visible before a user enters.

Stage 4 Test the launch candidate

The complete World is tested with its intended Model, data, parameters, interface, contracts, and runtime policy.

Required checks should include:

• configuration validation;
• repeated runs across many seeds;
• extreme and adversarial inputs;
• compute and storage benchmarks;
• checkpoint and replay tests;
• pause and resume behavior;
• settlement bounds;
• wallet and transaction failure states;
• mobile and desktop interface testing.

Stage 5 Review the final manifest

Before launch, the system shows the complete manifest in readable form:

• Designer and Launcher;
• Blueprint and World versions;
• provenance and data references;
• configuration hash;
• economic policy;
• runtime budget;
• verification class;
• contract addresses when applicable;
• known risks and limitations.

The Launcher signs the exact manifest being deployed.

Stage 6 Create and fund the World

The working design requires the Launcher to satisfy a $SPAWN creation gate and fund initial runtime costs in $ETH.

If the production launch gate is irreversible, the interface must show its verified contract, exact amount, and effect before confirmation.

If a World uses a World Token or protected liquidity, the applicable contracts should create and register those components through a bounded launch process.

Stage 7 Publish and operate

After successful deployment, the World page publishes its manifest, current status, runtime balance, checkpoint history, and verification information.

The Launcher can operate the World only within the powers disclosed before launch. Frozen Season rules cannot be changed retroactively.

Current application flow

Before production contracts are live, Spawn may collect applications from Designers, Launchers, and Players. An application is an expression of interest. It is not a token purchase, contract deployment, or promise of acceptance.