WORKINGv2.0
Launcher Configuration
What Launchers may configure and when a change becomes a new Blueprint.
A key product question is how fifty Worlds can use the same Blueprint without being identical.
Configuration surface
The Designer publishes an allowed parameter domain Θ. For Climate Lab, examples could include:
- geography/region;
- spatial resolution within safe bounds;
- Season duration;
- initial climate state;
- maximum number of storms/agents;
- permitted player actions;
- scoring objective from an approved set;
- capital bands;
- tick cadence within benchmarked limits.
Locked Blueprint logic
A Launcher using Climate Lab should not silently change:
- core state representation;
- physics/transition equations;
- arithmetic semantics;
- verifier logic;
- serialization format;
- hidden randomness source;
- input ordering semantics.
Changing these creates a new Blueprint/fork, not a configuration of Climate Lab.
Why the line matters
The fork boundary determines attribution, royalties, reproducibility, benchmark validity, and what a user can reasonably assume when they see “Built on Climate Lab.”