VisionEdgeOS

What it is

A controlled product-image family that carries VisionAI and the ONNX inference runtime onto industrial hardware. It is not a Linux distribution and forks no kernel: it builds on a supported upstream base, either Ubuntu Core with strict snap confinement or a hardened minimal Ubuntu Server 24.04 LTS with Ubuntu Pro. Which of the two is chosen depends on hardware evaluation that has not happened yet.

Around the image sit the things that make an image accountable: a release manifest, an SBOM and provenance record, artifact signing, an update and recovery contract, and one shared verification harness that every variant runs.

Who it is for

The people who have to install inspection software on a device in a plant and later answer what exactly is on it. Hardware profiles are versioned and carry an explicit lifecycle: experimental, supported, qualified, retired.

How it is governed

A profile is qualified only when it has been tested on its physical hardware. Results from a virtual machine or a CI lane are development evidence and are labelled as such; hardware checks on a non-physical lane report a skip with a reason and never a pass. Schemas exist for the release manifest, the hardware profile, the commissioning record and the revocation record, so each of those is a document with a shape rather than a habit.

What it does not do

It makes no compliance claim. No operating system is certified for a regulated process by being built a particular way, and the repository says so directly. Nothing in it is qualified, secure, immutable, fail-closed or production-ready today.

Status

Design and scaffolding. The snap variant is an unproven prototype; the server variant is a provisioning sketch in which signed A/B rollback is named as a must-add and is not yet prototyped. No CI lane is built.

Related

VisionAI is the application it carries. VisionML supplies the models that run on it. VisionFleet reads what each device reports and compares it with what it was supposed to have.