Evidence & credibility
A simulation platform is only as useful as the evidence trail it produces. UAVSimNet is built so that every claim in a run report is traceable back to a named source, a confidence class, and an approval event.
Every parameter is tagged at registration time with a confidence class — reviewed, provisional, or imported — and every downstream record preserves that tag unchanged. A run composed entirely of provisional inputs cannot accidentally masquerade as validated.
Parameters with sources outside our own engineering ship with the reference embedded (literature, a published airframe spec, or a customer-supplied document). The reference follows the parameter into every run report that uses it.
For kinematic runs, the engine is fully deterministic — same inputs, same outputs, byte-for-byte. A replay is used in regression testing so a new release cannot silently change a trajectory.
Flight-dynamics backend uses JSBSim, an independently maintained 6-DoF library with decades of aerospace provenance. We do not modify the core solver; we stitch airframe, environment, and control integrations around it.
Analysts submit; reviewers approve, request changes with notes, or reject. Only approved runs can be promoted to golden references. Every state transition is audited with user id and timestamp.
At submit-time, every parameter that contributed to the run is frozen into an immutable snapshot on the run record. The snapshot survives later edits to the underlying library blocks — what ran was what ran.
