Models & Blueprints
The difference between simulation logic and a reusable launch package.
Model
A Model defines a system: its state, transition rules, accepted inputs, timing, randomness, and outputs. It may be an early private experiment, a research implementation, or production-quality code.
Blueprint
A Blueprint is an immutable, versioned package built around a Model. It adds the information a Launcher and verifier need to use it responsibly:
- schemas and canonical serialization;
- configuration limits;
- runtime and dependency versions;
- data and provenance manifests;
- tests and benchmark profiles;
- checkpoint and verification rules;
- license, limitations, and royalty policy.
Why the distinction matters
A Model can change during development. A Blueprint version cannot silently change after publication. Any modification that can alter state, outputs, replay, cost assumptions, or settlement behavior requires a new version.
One Blueprint can support multiple Worlds. Each World chooses an allowed configuration but inherits the exact Blueprint version and its attribution.
Blueprint maturity describes technical readiness. It does not certify scientific truth, security, profitability, or suitability for every use.