# Government and institutions

Which model was approved, for which system, and what that system reports running.

> **Intended, not deployed.** Intended application areas. Vraelis has no customer deployments in them.

## Oversight runs on records.

### Systems built by suppliers

Model updates arrive from outside the institution.

### An unexpected release is a security and operational risk

For the institution responsible for the system.

### Readable by someone outside engineering

Including what could not be confirmed.

## The workflow, in this area

1. Identify the release.
2. Bind approval to the release and destination. Destination-bound approval covers that system and no more.
3. Integrate with a supported runtime.
4. Compare approved and reported. Version mismatch shown as reload pending, in a view a reviewer can follow.
5. Preserve discrepancies, missing evidence and recovery.

![Approved cpu-2 beside reported loaded cpu-1, with the differing fields marked.](https://vraelis.com/v8/contour/crop-pair-pending.webp)

*Read-only evidence app, inside the controlled ONNX reference experiment.*

## Not claimed

- No government deployments, contracts or customers.
- No procurement status, and no authorization to operate.
- No access to classified or restricted environments.
- No certification or regulatory compliance.
- No hardware attestation. Runtime identity is a worker self-report.

- [Government and institutions on vraelis.com](https://vraelis.com/applications/government): The page this summary comes from.
- [Security evidence](https://docs.vraelis.com/security-evidence): Related research.
- [Machine trust](https://docs.vraelis.com/machine-trust): Related research.
- [Model integrity](https://docs.vraelis.com/model-integrity): Related research.

---

Vraelis documentation, Vraelis. https://docs.vraelis.com/government