Gateway v1 Implementation Checklist

Cloud identity

• Physical Gateway has standard DeviceSerial
• MQTT credentials and ClientId are server-issued and persisted
• ClientId is never locally constructed
• encryptionKey is used only for Gateway-cloud AES

MQTT

• uses .../v1/gw/{gatewaySerial}/... namespace
• Gateway-cloud topics carry /AES
• HTML Live topics do not carry /AES
• QoS/retain match the topic reference
• up/status has LWT
• reconnect is non-blocking and restores subscriptions

Child runtime

• Child DeviceSerial is separate from native address
• Driver registry exists
• NativeBusExecutor has single-owner I/O
• downlink translation is Driver-only
• Analyzer is uplink-only
• one Child failure does not stop others

Command

• bounded mid deduplication
• PUBACK is not confused with execution ACK
• supports unknown execution outcome
• successful ACK does not fabricate state

Sync and offline

• API token is not persisted to flash
• snapshot activation is atomic/last-known-good
• localRuntimeReady is independent from cloud connectivity
• cloud failure does not reboot or erase credentials

Onboarding

• discovery and association are separate
• manual onboarding is supported where required
• compatibility = Device requirements ∩ Driver ∩ hardware
• Backend Project/association authority is enforced