Delivery State Needs Its Own Table
Content intent and remote-delivery progress are different state machines and should not be collapsed into one post status.
state machine
Release Channels Have to Follow Promotion State
Calling a release STABLE while its channel remains canary creates two sources of truth.
A Sticky Heartbeat Result Almost Became a False OTA Rollback
Telemetry from a previous release must not be allowed to mutate the state of a newly assigned release.
Transfer Pending Prevents Ownership Change from Becoming a Race
Moving a device between accounts needs an intermediate state while old and new authority are resolved.
Release State and Release Channel Drifted Apart
A release promoted to STABLE was still carrying old channel metadata, creating two competing sources of truth.
Provisioning Failure Needs a Recoverable Path
A device that loses power or Wi-Fi halfway through setup should not become permanently ambiguous.
The Device State Machine Is Part of the Product Contract
Factory, pairing, active, blocked and retired are operational states with different permissions.