Orbital Engine
Physics-oriented engine concept for orbital dynamics and space-system simulations.
Maturity
CONCEPTConcepts are not represented as launchable until validation gates are passed.
Compute
C3A measured Compute Profile is required before launch.
Verification
NEEDS PROOFVerification class is separate from Model maturity.
World lineage
0Example descendant Worlds.
Models are reusable infrastructure.
A Launcher can select a launch-ready version, configure only the declared surface, benchmark the resulting World, and preserve immutable lineage back to the Designer.
Customize the World, not hidden physics.
The Designer publishes the allowed parameter surface. A Launcher can choose values within that surface. A material change to state representation, transition rules, arithmetic, serialization, or verification creates a new Blueprint/fork.
Read Launcher Configuration →C3 planning class.
This is not a final price. A launch configuration must be benchmarked for CPU, GPU, memory, I/O, storage, active data, tick duration, and verification overhead before runtime funding is quoted.
Read Compute Profiles →Source material stays attributable.
Launch-ready Blueprints should identify datasets, origin, license, content hashes/manifests, derived datasets, and the boundary between sourced material and Designer choices.
Read Data Availability →NEEDS PROOF
A Model's maturity status and its execution-verification class are different things. Replayability makes state transitions checkable; it does not by itself prove scientific correctness.
Read Verification Classes →Useful Models can become parents of many Worlds.
Eligible descendant activity can route disclosed fees back to the registered Blueprint Designer without requiring the Designer to launch every World themselves.
Read Economic Lineage →