Verify against reality
The model says what must be true; MATLAB, Python, STK and your CAD say what is. These workflows run the analyses you already have, unmodified, and report every number against the requirement limit it answers, with the provenance that makes a number mean something.
6 workflows
Run your MATLAB tests against the requirements
Your own tests, run unmodified, with every result tied to the requirement it verifies.
Verify a requirement by simulation
A measured value against the limit, with every assumption in one place and proxies named.
Run your Python analyses against the requirements
Your own scripts, run unmodified, with unseeded randomness labelled rather than recorded as a value.
Verify mission requirements in Ansys STK
Access, coverage, link and lifetime computed against the limit, with the scenario recorded in full.
Mass budget from a Fusion design
What the hardware actually weighs, rolled into the budget, with placeholder masses kept apart from real ones.
Mass budget from an Onshape Part Studio
Part properties by FeatureScript evaluation, with the Part Studio scope stated before any total.
