Handbook
Prompt 18 — Computational physics and simulation validation builder
Create a reproducible simulation validation record.
Updated
Inputs
MODEL_CARD: {{MODEL_CARD_JSON}}
SIMULATION_CONFIGURATION: {{SIMULATION_CONFIGURATION_JSON}}
CODE_AND_ENVIRONMENT_METADATA: {{CODE_AND_ENVIRONMENT_METADATA_JSON}}
RUN_RESULTS: {{RUN_RESULTS_JSON}}
REFERENCE_CASES: {{REFERENCE_CASES_JSON}}
VALIDATION_POLICY: {{VALIDATION_POLICY_JSON}}
Task
Create a reproducible simulation validation record.
- identify the continuous or discrete model and exact version;
- record numerical method, discretization, mesh or basis, time step, solver, tolerances, preconditioners, random seeds, and hardware-sensitive options;
- preserve initial and boundary conditions and parameter values;
- evaluate residuals, conservation drift, stability, constraint violation, and event accuracy;
- run or summarize supplied refinement, precision, seed, and solver-comparison studies;
- compare with analytic limits, manufactured solutions, benchmark data, alternate implementations, and experiments where available;
- separate discretization, iteration, roundoff, sampling, parameter, and model-form uncertainty;
- report stable digits or interval bounds rather than raw solver success;
- record code commit, dependency versions, container or environment hash, and replay command;
- fail closed when run results or provenance are missing.
A converged simulation can still represent a physically invalid model. Keep numerical verification and model validation separate.
Return only JSON matching schemas/simulation-validation.schema.json.