Skip to content
Government and institutions

Model release evidence a reviewer can read.

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

Computer servers in a data center.

Intended application areas. Vraelis has no customer deployments in them.

Why it matters

Oversight runs on records.

Systems built by suppliers

Model updates arrive from outside the institution.

An unapproved release is a security event

For the institution responsible for the system.

Readable by someone outside engineering

Including what could not be confirmed.

How Vraelis Contour would apply

Five steps, release to record.

How Vraelis Contour works
  1. Identify the release

    Working in the experiment: model and configuration digestsProposed: preprocessing identity
  2. Bind approval to the release and destination

    Destination-bound approval covers that system and no more.

    Working in the experiment: signed bindings
  3. Integrate with a supported runtime

    Working in the experiment: ONNX Runtime 1.23.2, CPUProposed: customer runtime adapters
  4. Compare approved and reported

    Version mismatch shown as reload pending, in a view a reviewer can follow.

    Working in the experiment: evidence app
  5. Preserve discrepancies, missing evidence and recovery

    Working in the experiment: recorded observationsProposed: investigation workflow
Approved cpu-2 beside reported loaded cpu-1, with the differing fields marked.
Read-only evidence app, inside the controlled ONNX reference experiment.
Limits

What we do not claim.

  • 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.

Release evidence a reviewer can read.

Join us in building it for government and institutional review.