Deterministic runs
The same declared inputs and seed reproduce the run. Run identity stays with the results.
Assurance
How results are checked.
Deterministic runs, versioned scenarios, human authority, and auditable records keep simulated evidence reviewable and reproducible.
Assurance
Checks applied to every study.
Each mechanism keeps a run tied to its declared inputs, models, and human decisions.
Versioned scenarios and provenance
Versioned .awsim scenarios keep entities, constraints, revisions, model versions, and run settings with the evidence.
Human authority
Orders bind to the signed-in participant's seat. Orders needing higher authority are held for approval, and assisted suggestions need operator approval.
Audit and recovery
Actions are recorded in an audit trail with tamper verification. Recovery bundles preserve audit history byte for byte, keeping verified and quarantined entries separate.
Release checks
Engine, server, browser, and desktop test suites and recorded evidence run before release.
Run record
What a run keeps.
Each run retains the inputs and decisions needed to replay and review it.
- Scenario revision
- Seed
- Model and policy versions
- Run settings
- Orders, approvals, and denials
- Event history
- Audit entries
What results mean
Simulation results are decision-support evidence within the assumptions and fidelity of the selected models. They are reviewed with their scenario revision, model versions, run settings, and known limits.
Validation and use limits
- Live command-and-control certification is outside scope.
- Operational mission systems remain authoritative.
- Real-world combat predictions are not validated.
- Specific-weapon engineering and firing solutions are outside scope.
- Flight, launch, safety, and mission-assurance certification is outside scope.
Capability coverage
Review capability coverage