# From approved release to machine report

For enterprise release, platform and security engineers operating AI across machines and sites.

Vraelis Contour compares an approved AI release with what machines report. It keeps release identity, reporting context and differences together so an operator can investigate a mismatch or a gap.

1. Identify the approved release and its model, configuration and release records.
2. Associate machines and their reporting context with the organization.
3. Compare incoming reports with the approved reference. Treat missing or stale reporting separately from a matching report.
4. Inspect differences and reporting timelines before deciding whether to repair a deployment, refresh its report or review its approval.
5. Use fleet analysis to review recurring differences, reports before approval, metadata gaps and architecture distribution.

## Enterprise access

Access is restricted to eligible organizations. The public [Vraelis Contour page](https://vraelis.com/contour) shows synthetic examples; named organizations in those examples are not evidence of customer deployment. Use [account access](https://docs.vraelis.com/prompto-account) and [fleet analysis](https://docs.vraelis.com/contour-fleet-analysis) for current workspace instructions.

## What a report establishes

A machine report is a claim from its reporting path. Comparison alone is not hardware attestation, proof that the model was loaded, or a guarantee that the device is uncompromised. Reporting gaps require investigation. The underlying reference experiment is not a production-security assurance.

Product version and download availability belong to the selected platform in [Downloads](https://data.vraelis.com/downloads). Public endpoint health is listed separately on [System status](https://status.vraelis.com).

---

Vraelis documentation, Products. https://docs.vraelis.com/contour-workflow
