Government and institutions

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.

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.