No Enthalpy repository is public yet. The program is planned so that each released result will rest on code that readers can inspect, run, and extend. Code will be released under Apache-2.0A permissive open-source license. It allows commercial use, modification and redistribution, and it carries an explicit patent grant.; documents and data under Creative Commons AttributionA license that allows documents and data to be reused, including commercially, as long as the original is credited.. A release will identify the assumptions, inputs, version, and baselineThe existing or simpler method against which a new result is compared. Both methods must receive the same hardware assumptions, starting conditions and environment for the comparison to mean anything. behind its result, and a benchmarkA fixed set of scenarios, metrics and baseline methods that anyone can run, so that results from different groups can be compared honestly. result will require an independent run before it is treated as established.
Initiative 01 · Power- and thermal-constrained autonomy
| Planned repository | Purpose | Badge |
|---|---|---|
| enthalpy-specs | Numbered RFCsA numbered design document that proposes a change or fixes an interface, published for comment before the code is written. The practice comes from the standards that built the internet., schemas, and glossary. The design record of the project. | In progress |
| enthalpy | Models, environment, plannersThe software that decides what a robot or spacecraft does next, and in what order. It is separate from the control loop, which carries out each action once it has been chosen., simulator, and benchmark harness | Planned |
| enthalpy-solvers | Transient thermal networkA model that treats a vehicle as a handful of connected blocks, each held at a single temperature, instead of solving the full temperature field. At a suitable size and fidelity, it can run fast enough for a planning loop, and it remains an approximation., power flow, and planner inner loop | Planned |
| enthalpy-bench | Reference Mission 01A bounded, published mission scenario used to test one research claim. It fixes the assumptions, initial conditions, limits, metrics and comparison method so that another team can run the same study., transfer cases, metrics, baselines, and report generation | Planned |
| enthalpy-examples | Worked examples and tutorials for each scenario | Planned |
enthalpy-specs
Purpose
Badge
enthalpy
Purpose
Badge
enthalpy-solvers
Purpose
Badge
enthalpy-bench
Purpose
Badge
enthalpy-examples
Purpose
Badge
Design record
The planned specifications repository will be the public design record for the project. Its first six RFCs will cover the spacecraft graph schema, the model contract and fidelity tiersA declared level of physical detail for a model and the evidence expected for its use. The tier helps a reader distinguish a rough estimate from a result supported by validation evidence., the planner contract, the scenario and benchmark format, the environment interface, and the publication boundary. Once a repository is available, decisions that affect a public interface will be recorded there rather than left in conversation.
How we build
Reference first
Each physics model will have a plain reference implementationA plain version of a model, written for clarity rather than speed and checked against reference cases. Faster versions are compared with it against stated tolerances. that serves as the oracle. Optimized fast paths will be tested against it and must agree within a stated tolerance.
Explicit units
Public interfaces will carry units. A quantity will not travel as a bare number.
Reproducible scenarios
A scenario will carry its inputs, parameter sources, uncertainty range, and seed. The benchmark report will identify the exact release that produced it.
Citable releases
Each public release will include a version, license, citation record, and enough provenance to trace a result to its model, scenario, and baseline. Archival copies will receive persistent identifiers when the publication venue supports them.
Where Enthalpy fits
BasiliskAn open-source simulation framework for spacecraft dynamics, attitude and orbital motion. models spacecraft dynamics, while OpenMDAOAn open-source framework from NASA for optimizing designs whose parts interact, where changing one subsystem changes the others. connects design variables across engineering disciplines. Activity-planning and flight-software frameworks address other parts of the mission stack. Enthalpy is intended to carry power and thermal state into task planning through a common model contract, then measure the result against a reproducible baseline. It is designed to work alongside established tools rather than reproduce them.
What we do not publish
Flight-qualified control code for a specific vehicle, controlled component data, and partner-confidential scenario parameters remain private. Planned public benchmarks will use generic, published parameters only. A public research release will not claim flight qualification.
Contributing
Until the first repository opens, propose an RFC, challenge an assumption in Reference Mission 01, or contribute a benchmark scenario at research@mindpoollabs.com. Public releases will appear through the Mindpool Labs organization on GitHub. When scenarios are released, contributors can run them and report their results.