Repository navigation
id: design: constrained-device providers (ESP32 + MQTT instantiation) (from #5686) #5901
Description
Summary
Follow-on design ticket from #5686 — its decomposition sketch names this as a separate design, and the parent's acceptance requires these tickets to be filed and linked. Filed in the 2026-11-04 gap pass (WS-F) so the design work exists and can be prioritised on its own merits; implementation timing is a separate decision, possibly months out.
What this design must settle
The provider model instantiated for constrained devices: ESP32 + MQTT bridge topic mapping, bridge trust, and device identity/ceiling provisioning. (The ESP32 hardware platform itself is designed in #5783; the bridge protocol in #2343 — this ticket is the provider-model instantiation.)
Context from the parent
The parent design fixes the single capability-provider model — declaration, discovery, negotiation, least-privilege grants — instantiated by ESP32/MQTT, terminal, Bevy, smartphone, and web providers. The parent issue carries the surrounding decisions this ticket must not re-decide; where this ticket's answer would change a parent decision, record that explicitly rather than silently forking it.
Decision record expected
Close this design with a recorded decision (on this issue or in a doc/ record linked from it): the chosen shape, the alternatives rejected and why, and the invariants implementation must hold. If the design splits further, file the splits and link them here rather than growing this issue.
Relations
Parent: #5686. Programme: epic #2056. Filed by WS-F (2026-11-04 ID design gap & expansion pass).
Activity
developing-today commentedon Nov 5, 2026
CODE-1584
dezren39 commentedon Nov 5, 2026
Field survey filed: #5931 (capability-provider research widening, per Drew's 2026-11-04 ruling) covers the current option space relevant to this issue in §5 — constrained-device option space: firmware stacks, MQTT/MQTT-SN/CoAP/Matter variants, broker table, 64 KiB-frame-relevant transport notes. It is an inventory, not a decision — the section ends with the open questions this design needs to answer.
dezren39 commentedon Nov 5, 2026
🤖 Agent note · done (triage)
Triage findings (verified fresh 2026-11-05 via
gh):task/triage,queue/queued,app/id. No hard-stop labels (held,user/owned,do-not-merge,do-not-auto-edit) and nouser/review/user/escalated.doc/record linked from it): chosen instantiation shape, alternatives rejected and why, and the invariants implementation must hold. Further splits get filed and linked, not grown into this issue.Triage complete for task 10303; issue #5901 stays open for the design decision.