โ† Back to the chapter

Technical detail ยท Edge ML and TinyML Deployment

Runtime boundaries behind the release claim

Edge deployment changes the operating boundary of a model. Training may have used clean batches, stable timestamps, full precision, large memory, and cloud-side observability. The device may have noisy sensor streams, clock drift, missing packets, reduced precision, tight memory, limited power, intermittent backhaul, and delayed outcomes.

The runtime boundary is also a software boundary. The review should name the operator set, tensor arena or memory pool, compiler/runtime version, quantization calibration sample, preprocessing code path, and scheduler assumptions that make the artifact behave like the evaluated model. A firmware update that changes sampling order, task priority, clock source, or radio duty cycle can invalidate the evidence even when the model checksum is unchanged. That is why runtime changes belong in the retest trigger.

Feature Boundary.

Online windows, filters, units, missing-data rules, and sensor timing must match the training recipe or the model sees a different problem.

Precision Boundary.

Quantization, pruning, distillation, or runtime conversion can change confidence, rare-class behavior, and borderline decisions.

Resource Boundary.

Inference shares memory, power, processor time, storage, and communication windows with firmware tasks that also matter to the product.

Observability Boundary.

Privacy, bandwidth, and offline operation can hide inputs and outcomes, so telemetry must prove enough without collecting too much.

A strong deployment plan treats fallback as part of the model. If input quality is poor, confidence is low, the runtime is overloaded, or the model version is suspect, the system should choose a documented safe behavior: defer to a rule, ask for cloud review, use a conservative threshold, hold the previous state, or escalate to a human owner.

The under-the-hood rule is to preserve diagnosability. A field model that cannot report version, input quality, confidence, fallback frequency, resource pressure, and drift signals is hard to improve and unsafe to broaden.

โ† Back to the chapter