Release ID Is Stronger Than a Version String

The OTA bug was not in the downloader. The real problem was that Version text alone could not uniquely identify artifact lineage or distinguish reissued builds.

The system behind this series is LOUP's production-style OTA control plane: per-device identity, explicit release objects, compatibility metadata, assignment state, heartbeat observation, A/B application slots, signed artifacts, first-boot validation, append-only events and staged rollout. The point is not the exact API shape. It is the state discipline required when server, device and bootloader can each be correct locally while disagreeing about the fleet globally.

The evidence for this case was specific: The device integration contract says compare release_id, not merely version string; releases also carry immutable artifact/source metadata. I keep that claim tied to this implementation and policy rather than presenting it as a universal OTA benchmark.

The result I retained was: Heartbeat and assignment causality became release-ID based.

The state I was actually debugging

operator -> release state -> device assignment (desired)
                           |
                           v
device heartbeat ----> running_release_id (observed)
       |                   |
       |                   v
       +---- desired manifest if eligible/compatible
                           |
                      inactive OTA slot
                           |
                      reboot pending verify
                           |
                 local self-test -> accept / rollback
                           |
                  release-scoped event + heartbeat

The control plane carries at least three truths at once: immutable release identity, operator desired assignment and device-reported running identity. OTA is the convergence process between them.

This case became a distributed-systems boundary test. Device observation, server intent and release policy did not mean the same thing. The failure was Version text alone could not uniquely identify artifact lineage or distinguish reissued builds. Evidence showed The device integration contract says compare release_id, not merely version string; releases also carry immutable artifact/source metadata. The mechanism was A release ID identifies one control-plane object while a semantic version is only one label on that object. and the useful conclusion was Heartbeat and assignment causality became release-ID based.

The practical rule was: Use immutable identity for state transitions; keep versions for humans. That rule is more durable than any one endpoint or database column because it defines which component is allowed to claim which truth.

Reconstructing the transition

release object: DRAFT -> REGISTERED -> TESTED -> CANARY -> ROLLING_OUT -> STABLE
                                      |
operator assignment -----------------+--> desired_release_id
                                               !=
device heartbeat --------------------------> running_release_id

I used one question to keep the model honest: What event would prove the transition rather than merely suggest it?

For this case, the answer starts with the observed problem: Version text alone could not uniquely identify artifact lineage or distinguish reissued builds. The control plane already had evidence that The device integration contract says compare release_id, not merely version string; releases also carry immutable artifact/source metadata. That evidence only becomes useful when it is attached to the correct transition. The underlying reason is A release ID identifies one control-plane object while a semantic version is only one label on that object.

Now consider the counterfactual. Suppose the server keeps its desired state, but the device never reports the corresponding running state. Nothing should silently advance. Suppose the device reports a terminal-looking string that belongs to an older release. The new assignment should not inherit that causality. Suppose a release is cryptographically valid but persistent-state compatibility is wrong. Delivery still has to stop. These are all examples of locally reasonable facts that become globally wrong when their scope is lost.

The shortcut I rejected was Using 1.2.3 equality as proof that server and device refer to the same artifact. It removes a state or validation step, but that apparent simplicity only pushes ambiguity into recovery. The retained result—Heartbeat and assignment causality became release-ID based.—keeps the ambiguity visible until a component with the right authority resolves it.

Implementation boundary

The control plane needs separate columns and API semantics for release identity, desired assignment and observed running release. Assignment should not mutate the running fields. Heartbeat should not mutate release policy. Promotion should not depend on a version comparison alone. The admin UI can derive “pending” from desired_release_id != running_release_id while the assignment is non-terminal, which makes convergence visible without pretending it already happened.

The device should report facts it can observe and avoid guessing operator intent. In this case, the key observation is The device integration contract says compare release_id, not merely version string; releases also carry immutable artifact/source metadata.. I would expose enough state to verify that observation without copying secrets or giant diagnostic payloads into the event stream.

The minimum useful operational record includes the device identifier, release identifier where relevant, previous and target versions, assignment state, boot/update state, and a sanitized result. For device-side acceptance I also want the generations that determine compatibility. These fields are not decoration: they let an incident review distinguish “server wanted release X,” “device downloaded release X,” “device booted release X,” and “device accepted release X.”

The unsafe alternative was Using 1.2.3 equality as proof that server and device refer to the same artifact.. That alternative usually saves one field or one state transition, but it makes recovery ambiguous. When the system later fails, an operator has to infer what probably happened from timestamps and logs. I would rather spend a little more schema/API complexity up front and make the transition mechanically provable.

The failure test I would run

I would deliberately try to promote REGISTERED directly to STABLE.

The expected outcome is not merely “the request fails.” I want the resulting state to remain explainable. The device row, assignment state, release state and append-only event history should agree on what happened and which release the event belonged to. If recovery occurs, it should happen through a defined transition rather than an administrator manually editing the database until the dashboard turns green.

This case is particularly useful because the rejected shortcut was Using 1.2.3 equality as proof that server and device refer to the same artifact.. The failure test forces that shortcut to reveal its ambiguity. A good state model should make the unsafe interpretation impossible or at least operationally visible.

Operational consequence

The retained engineering rule is Use immutable identity for state transitions; keep versions for humans.. I want that rule enforced in code or policy wherever possible, not left as a runbook sentence that an operator must remember under pressure.

That means state transitions should reject incompatible releases, release promotion should have explicit blockers, heartbeat processing should be conservative about terminal states, and artifact serving should repeat compatibility checks. The event log should preserve who or what caused each important transition. Recovery should be a first-class path rather than an exceptional database repair.

For this article, the operational result was Heartbeat and assignment causality became release-ID based. That makes the system easier to reason about because each dashboard badge corresponds to a bounded claim rather than an optimistic summary.

Incident contract

I keep this matrix because OTA incidents are easy to rewrite after recovery. Once a device comes back, an old heartbeat string, an assignment row and a release state can all look consistent even when they referred to different transitions. Recording causal identity while the incident is active prevents that retrospective simplification.

The rule I kept

Use immutable identity for state transitions; keep versions for humans.

The result from this case was Heartbeat and assignment causality became release-ID based.

That is the core of production OTA for me. The hard problem is not moving a .bin file over HTTPS. The hard problem is preserving causal truth while identity, policy, persistent data, bootloader state, device observations and operator intent change at different times.

A successful update is therefore not “download returned 200.” It is a sequence of authorized, compatible and observable state transitions with a recovery path at every irreversible boundary.