A weights file does not identify the machine it represents, the actions it supports or the evaluation behind its use. An evidence registry keeps those responsibilities attached to the exact version deployed around a machine.
More than model storage
A machine-model record should include typed state, actions, horizons, supported conditions, uncertainty behavior, evaluations and limitations. A repaired version also needs its parent, changed mechanism, verification decision and rollback path.
Applications should resolve an immutable digest rather than a mutable model name. A change to the model, interface or evidence produces a new record.
Evidence enables fleet reuse
A correction verified on one unit is not automatically valid for every similar machine. Compatibility depends on hardware revision, controller, sensors, payload and operating envelope.
The registry makes those conditions explicit. This is what can eventually support safe reuse across compatible fleets.
Distribution comes later
A marketplace of unverified model files would not solve the operating problem. Distribution becomes valuable after models and repair modules carry comparable evidence and have been used across independent machines.
A08 therefore starts with the Repair Runtime and Evidence Registry. A broader Machine Network is the result of successful deployments, not a prerequisite for the product.
Sources
OCI Image Specification ↗A content-addressed approach to portable manifests and artifact identity.
ML Model Cards ↗Documentation practices for model context, performance and limitations.