Model update architecture

A model release fixes the model bytes by digest and can carry framework, hardware profile, input shape and license metadata. TUF authorizes the exact target. The rollout engine separately decides which compatible devices receive it and in which wave.

The Linux model adapter stages a candidate into a separate slot, preserves the previous slot, changes the active reference, and runs the configured local evaluation. A failed evaluation restores the retained prior state when the adapter contract supports it. The result is reported as rollout evidence.

The optional ML SDK reports bounded aggregate windows by artifact version: sample count, quality metrics and latency summaries. Raw input, prediction, label and customer payload data are outside the protocol. Small windows are withheld by the SDK's configured minimum sample threshold.

Meshanics is not a training system or experiment tracker. See Model packaging, Runtime and eval, and Model quality telemetry.