How We Validate Before Building

MetroVolt is validated in layers — code verification, physics validation, digital twin, then hardware — so that each build tests specific predictions.

Validation in layers

Validation is not one act but a sequence. Each layer catches different errors: code verification checks the math is solved correctly, physics validation checks the models match known experiments, the digital twin integrates them into a machine-level prediction, and hardware tests the whole against reality.

Predictions, then tests

The point of validation is to enter each hardware step with specific, falsifiable predictions. The ~2032 test unit is not an open-ended experiment; it checks named predictions about confinement, field, DEC efficiency, and materials. Where measurement disagrees with prediction, the models are corrected before the next build.

• Verify the code, validate the physics, integrate in the twin, test in hardware.
• Enter hardware with falsifiable predictions.
• Feed disagreements back into the models between builds.

This layered approach is why MetroVolt calls itself a design and simulation study today, and why the honest gates are stated before, not after, the hardware.