For university faculty and laboratories
Give students a software laboratory for turning mission requirements into bounded engineering conclusions. The public University Lab and all thirteen runnable pilot missions at ML-D depth expose configuration, provenance, evidence quality, limitations and V&V reasoning. Supported workflows additionally expose comparison and replay. Mission Studio adds signed-in persistence where configured.
Buyer summary · Print or save this page
For undergraduate spacecraft engineering, suitable graduate coursework, laboratories and capstones. The lab helps faculty teach model-based mission decisions with visible evidence and limitations, using current software rather than a separate university simulator.
Frame a requirement, run a current ML-D mission or the public University 3U Mission Control, compare supported configurations, replay and inspect provenance, then write a bounded V&V conclusion. Outputs include simulated/derived channels, run identity and Evidence V2 export where supported.
Current University Lab workflow, runnable mission catalogue, public Mission Control, model and configuration visibility, evidence tools and guided evaluation support. Local/private Developer API access is optional only when explicitly enabled.
Faculty choose course objectives, a mission question and suitable student scope, provide devices and facilitation, and own course mapping, rubrics, grading and accreditation decisions.
Public Lab and Mission Control need no account or hardware. Mission Studio persistence requires sign-in and configured access. This evaluation includes no measured hardware evidence, flight qualification, hosted learner code or production-public Developer API.
Start with a guided evaluation of the existing Lab workflow and ML-D missions. A standardized six-lab teaching sequence is being packaged; it is not part of the current completed offer. Model limitations remain visible, and faculty own assessment.
Next: open the public Lab, request a demo, or discuss a scoped quote.
Inspect visible channels, their provenance roles, deterministic run hashes, and the claim each artifact can support.
Compare bounded configurations, evaluate evidence sufficiency, and state what a longer or more detailed software run still cannot establish.
Local practice has zero measured channels and is not verified recognition. Institutional and Challenge authority remain separate workflows.
Engineering workspace
Create and revise persistent mission records for supported engineering workflows, and keep their evidence with model and channel provenance visible. Public Mission Control runs are separate practice until an accepted persistence handoff exists. Mission Control is the engineering instrument used to inspect runs, not a separate product.
Bounded developer access
The versioned Developer API and TypeScript, Python and Jupyter source clients support explicitly enabled local/private evaluation. A stable production-public or browser API is not available, and MissionLab does not host arbitrary learner Python, JavaScript or shell execution.