Technical · verification
Evidence and validation boundaries
Verification is organised as a chain of complementary evidence rather than a single solver-to-solver agreement test.
Numerical verification, cross-method comparison, cross-engine parity, physical calibration and experimental validation answer different questions and are published with different evidentiary requirements.
Verification framework
The current evidence ladder, active FDM/FEM checks, controlled FDM/FEM/FVM studies, cross-engine boundaries and publication rules for validation claims.
active / consolidatingNumerical verification
Analytical/reference problems, conservation, stability and refinement checks exist across the source tree. The method-independent manufactured-solution layer is still being consolidated.
activeCross-engine verification
Active GNU Octave and C++ sibling engines consume common resolved cases through an explicit exchange contract. Current tolerances are verification gates, not publication performance benchmarks.
future evidenceExperimental validation
Calibration and independent validation require traceable real-process observables, sensitivity/identifiability work, uncertainty treatment and an independent validation case.