# Driver-expansion β€” Waves 0–2 tracking > **Living status tracker** for the driver-expansion program (Waves 0, 1, 2). One row per > deliverable, each pointing at its **design doc**, its **implementation plan** (once written), > and its current **status**. The authoritative *architecture* index is the program design doc; > this file is the authoritative *progress* index. > > **Program design (architecture / shared contract / build order):** > [`2026-07-15-driver-expansion-program-design.md`](2026-07-15-driver-expansion-program-design.md) > > Last updated: 2026-07-24. ## Legend | Status | Meaning | |---|---| | βœ… **Done** | Merged to master, tests green. | | 🟑 **Live gate open** | Code merged; a live `/run` or hardware-gated verification still outstanding. | | πŸ“ **Plan ready** | Executable implementation plan (`*-implementation.md` + `.tasks.json`) written; not yet built. | | πŸ“ **Design only** | Design doc exists; **no** implementation plan yet β€” writing-plans is the next step. | | β›” **Not started** | No design, no plan. | **Doc types** (per the writing-plans skill): a *design* states architecture, decisions, and risks; an *implementation plan* is the bite-sized, TDD, file-path-level task list the subagent-driven executor runs off, with a co-located `.tasks.json` for resume. A deliverable is only buildable once it reaches πŸ“. ## Summary | Wave | Deliverable | Design | Impl. plan | Status | Effort | Fixture / hardware | |---|---|---|---|---|---|---| | **0** | Universal Discover-backed browser | [design](2026-07-15-universal-discovery-browser-design.md) | [plan](2026-07-15-universal-discovery-browser-implementation.md) Β· [tasks](2026-07-15-universal-discovery-browser-implementation.md.tasks.json) | 🟑 **Live gate open** | S–M | none (retrofits shipped drivers) | | **1** | Modbus RTU (extend Modbus) | [design](2026-07-15-modbus-rtu-driver-design.md) | [plan](2026-07-24-modbus-rtu-driver.md) Β· [tasks](2026-07-24-modbus-rtu-driver.md.tasks.json) | 🟒 **Built β€” live gate PASSED** (11 tasks, branch `feat/modbus-rtu-driver`, pending merge) | **S (lowest)** | `pymodbus` `rtu_over_tcp` β€” CI-simulatable, no new infra | | **1** | SQL poll | [design](2026-07-15-sql-poll-driver-design.md) | [plan](2026-07-24-sql-poll-driver.md) Β· [tasks](2026-07-24-sql-poll-driver.md.tasks.json) | πŸ“ **Plan ready** (22 tasks) | S–M | **existing central SQL Server** `10.100.0.35,14330` + SQLite unit | | **2** | MTConnect Agent | [design](2026-07-15-mtconnect-driver-design.md) | [plan](2026-07-24-mtconnect-driver.md) Β· [tasks](2026-07-24-mtconnect-driver.md.tasks.json) | πŸ“ **Plan ready** (23 tasks) | S–M | Dockerized `mtconnect/cppagent` β€” CI-simulatable | | **2** | MQTT / Sparkplug B | [design](2026-07-15-mqtt-sparkplug-driver-design.md) | [plan](2026-07-24-mqtt-sparkplug-driver.md) Β· [tasks](2026-07-24-mqtt-sparkplug-driver.md.tasks.json) | πŸ“ **Plan ready** (27 tasks, P1+P2) | M–L | Mosquitto/EMQX + C# Sparkplug sim β€” CI-simulatable | > Waves 3+ (BACnet/IP, Omron) and the deferred MELSEC are tracked in the program design doc Β§6/Β§8, > not here. Omron CIP is the program's sole real-hardware wire gate; BACnet's broadcast/BBMD leg is > env-gated live. Both are out of this file's scope until they're pulled forward. --- ## Executing a plan (git worktree + subagent-per-task) Each πŸ“ plan is executed with the **subagent-driven-development** skill: it sets up an isolated **git worktree** first (via `using-git-worktrees`), then dispatches a **fresh subagent per task**, running the classification-driven review chain (`trivial` = implement only … `high-risk` = spec-review β†’ code-review β†’ integration review) between tasks. The `.tasks.json` next to each plan tracks progress and lets a later session resume. **Paste one of these into Claude Code to build a driver:** | Deliverable | Command | |---|---| | Modbus RTU (Wave 1) | `Use superpowers-extended-cc:subagent-driven-development to execute docs/plans/2026-07-24-modbus-rtu-driver.md in a new git worktree` | | SQL poll (Wave 1) | `Use superpowers-extended-cc:subagent-driven-development to execute docs/plans/2026-07-24-sql-poll-driver.md in a new git worktree` | | MTConnect (Wave 2) | `Use superpowers-extended-cc:subagent-driven-development to execute docs/plans/2026-07-24-mtconnect-driver.md in a new git worktree` | | MQTT/Sparkplug (Wave 2) | `Use superpowers-extended-cc:subagent-driven-development to execute docs/plans/2026-07-24-mqtt-sparkplug-driver.md in a new git worktree` | - **Slash-command form** (equivalent): `/superpowers-extended-cc:subagent-driven-development `. - **Parallel-session / resume form** (batch execution with checkpoints, no fresh-subagent-per-task): `/superpowers-extended-cc:executing-plans ` β€” reads the same `.tasks.json` and continues from the first pending task. - **Recommended order:** Modbus RTU β†’ SQL poll β†’ MTConnect β†’ MQTT/Sparkplug (lowest effort first; see each wave below for the gating notes). Run one plan per worktree; the four plans are independent, so separate worktrees may run concurrently. --- ## Wave 0 β€” Universal Discover-backed browser 🟑 **What it is.** One generic `DiscoveryDriverBrowser` (+ `CapturingAddressSpaceBuilder`, `CapturedTreeBrowseSession`, `BrowserSessionService` fallback, and the `ITagDiscovery.SupportsOnlineDiscovery` gate) that turns any driver's `ITagDiscovery.DiscoverAsync` into an AdminUI browse tree. It is the **Wave-0 gate**: every browsable new driver depends on this seam, and it retrofits browse to the already-shipped AbCip / TwinCAT / FOCAS drivers for near-zero marginal cost. - **Design:** [`2026-07-15-universal-discovery-browser-design.md`](2026-07-15-universal-discovery-browser-design.md) - **Implementation plan:** [`2026-07-15-universal-discovery-browser-implementation.md`](2026-07-15-universal-discovery-browser-implementation.md) Β· [`.tasks.json`](2026-07-15-universal-discovery-browser-implementation.md.tasks.json) - **Status: 🟑 code-complete + merged, live gate open.** - Merged to master β€” `056887d6` (*Merge feat/universal-discovery-browser β€” Wave-0 universal Discover-backed browser*), 2026-07-15. - Implementation plan: **19 / 19 tasks completed.** - Lit up AbCip / TwinCAT / FOCAS pickers with zero per-driver browse code. - **Outstanding:** the full tree-render live `/run` gate is **fixture-blocked** β€” tracked as **Gitea #468**. Complete this before leaning on browse in Wave 2/3. --- ## Wave 1 β€” low-effort / high-leverage pair πŸ“ Both are **fully CI-simulatable with zero new hardware**; Modbus RTU needs no new infra at all, and SQL poll reuses the always-on central SQL Server. This is the recommended next build. ### Modbus RTU β€” 🟒 Built, live gate PASSED (branch `feat/modbus-rtu-driver`, pending merge) - **Design:** [`2026-07-15-modbus-rtu-driver-design.md`](2026-07-15-modbus-rtu-driver-design.md) - **Implementation plan:** [`2026-07-24-modbus-rtu-driver.md`](2026-07-24-modbus-rtu-driver.md) Β· [`.tasks.json`](2026-07-24-modbus-rtu-driver.md.tasks.json) β€” **11 tasks** (1 trivial / 5 small / 2 standard / 3 high-risk), all complete via subagent-driven-development. - **Scope:** extend the existing Modbus driver with a `Transport` selector (RTU CRC-16 + FC-aware length, no TxId) + a `rtu_over_tcp` `pymodbus` docker profile + the AdminUI selector. **Direct-serial transport is descoped** (user, 2026-07-15) β€” RTU-over-TCP via a serialβ†’Ethernet gateway is the only shipped mode, so there is no serial hardware gate. - **Fixture:** added the `rtu_over_tcp` profile (`framer=rtu`, host `:5021`, co-runs with `standard`) to the Modbus integration fixture. **Unknown confirmed:** pymodbus 3.13's simulator DOES honour `framer=rtu` on a TCP server (wire-probed a pure RTU FC03 response, no MBAP) β€” so the simple profile path was taken; **no stdlib fallback server was needed.** - **Verification (all green):** unit suite **344/344**; full solution build 0 errors; the 2 RTU integration tests pass **live** against the real `framer=rtu` fixture (read HR5β†’5, write+readback HR200←4242). Per-task review chain (spec + code reviewers) + a final whole-branch review, all approved-to-merge. - **Live `/run` gate β€” PASSED (2026-07-24, docker-dev rebuilt from this branch):** - AdminUI `/raw` Modbus **driver** config modal renders the new **Transport** selector (with the operator hint) β€” set to `RtuOverTcp`, saved. - **Device Test Connect β†’ `OK Β· 23 MS`** β€” the probe built a `ModbusRtuOverTcpTransport` via the factory and spoke **FC03 over real RTU framing** to `10.100.0.35:5021`. - Authored raw tags HR5 (r/o) + HR200 (r/w) β†’ **deployment `06ec1632` Sealed** (all 6 nodes acked). - Client.CLI on `opc.tcp://localhost:4840` (`multi-role`/`password`): **read** `ns=2;s=rtu-gate/Device1/HR5` β†’ **5, Good**; **write** `ns=2;s=rtu-gate/Device1/HR200` = 4242 β†’ readback **4242, Good**. - **Effort:** **S β€” the lowest on the roadmap.** Delivered first, as recommended. ### SQL poll β€” πŸ“ Plan ready - **Design:** [`2026-07-15-sql-poll-driver-design.md`](2026-07-15-sql-poll-driver-design.md) - **Implementation plan:** [`2026-07-24-sql-poll-driver.md`](2026-07-24-sql-poll-driver.md) Β· [`.tasks.json`](2026-07-24-sql-poll-driver.md.tasks.json) β€” **22 tasks**. `ISqlDialect` seam in from day one; only the SQL Server dialect built in v1 (Postgres/ODBC deferred). - **Scope:** a bespoke schema-browser driver polling a SQL table into equipment tags (SQL Server P1; Postgres/ODBC land in P2/P3 behind `ISqlDialect`). - **Fixture:** SQLite unit fixture (primary) + an **env-gated integration fixture against the existing central SQL Server** (`10.100.0.35,14330`) with a seeded `SqlPollFixture` DB. The blackhole/timeout live-gate pauses a **dedicated** `mssql` container β€” **never** the shared central SQL Server (it hosts `ConfigDb`). - **Effort:** S–M. --- ## Wave 2 β€” strategic telemetry / UNS pair πŸ“ Both CI-simulatable on the shared docker host, no hardware. ### MTConnect Agent β€” πŸ“ Plan ready - **Design:** [`2026-07-15-mtconnect-driver-design.md`](2026-07-15-mtconnect-driver-design.md) - **Implementation plan:** [`2026-07-24-mtconnect-driver.md`](2026-07-24-mtconnect-driver.md) Β· [`.tasks.json`](2026-07-24-mtconnect-driver.md.tasks.json) β€” **23 tasks**. Task 0 is the TrakHound-vs-hand-rolled client decision; browse-picker live-verify is gated on Wave-0 #468. - **Scope:** P1 Agent MVP (`IDriver`+`ITagDiscovery`+`IReadable`+`ISubscribable`+probe+rediscover), browse **free via the Wave-0 universal browser** (`SupportsOnlineDiscovery=true`, no browser code), typed editor, `UNAVAILABLEβ†’BadNoCommunication` mapping, ring-buffer re-baseline paging. - **Fixture:** canned XML unit fixtures (bulk of coverage) + a dockerized `mtconnect/cppagent` integration fixture (env-gated). Depends on Wave 0's browse seam being live-verified (#468). - **Effort:** S–M (β‰ˆ1–1.5 wk with TrakHound, β‰ˆ2.5–3 wk hand-rolled). ### MQTT / Sparkplug B β€” πŸ“ Plan ready - **Design:** [`2026-07-15-mqtt-sparkplug-driver-design.md`](2026-07-15-mqtt-sparkplug-driver-design.md) - **Implementation plan:** [`2026-07-24-mqtt-sparkplug-driver.md`](2026-07-24-mqtt-sparkplug-driver.md) Β· [`.tasks.json`](2026-07-24-mqtt-sparkplug-driver.md.tasks.json) β€” **27 tasks** (P1 plain MQTT = Tasks 0–14, a complete shippable milestone; P2 Sparkplug B = Tasks 15–26). Task 0 is the mandatory MQTTnet-5/net10 + central-pinning validation spike. - **Scope:** P1 plain MQTT (MQTTnet-5 connect/TLS/auth + hand-rolled reconnect, subscribeβ†’ `OnDataChange`, retained last-value read, `#`-observation browser); P2 Sparkplug B ingest (vendored Tahu proto, birth/alias/seq-gap/rebirth state machine, deathβ†’STALE). - **Fixture:** Mosquitto/EMQX broker (TLS + real auth, not anonymous) + a **project-owned C# Sparkplug edge-node simulator** for the rebirth/seq-gap/death test matrix + env-gated live suite (`MQTT_FIXTURE_ENDPOINT`). - **Effort:** M–L. **Top risks:** Sparkplug state-machine correctness; MQTTnet-5/net10 + the repo's fragile central pinning (mitigated by hand-rolling Tahu over one MQTTnet-5 client). --- ## Next actions 1. **Close the Wave-0 live gate** (Gitea #468) β€” unblocks browse verification for MTConnect/BACnet. 2. **Build Wave 1** β€” Modbus RTU first (lowest effort, no new infra), then SQL poll. Both plans are πŸ“ ready; run the command from the [Executing a plan](#executing-a-plan-git-worktree--subagent-per-task) table (subagent-driven-development in a git worktree). 3. **Build Wave 2** (MTConnect, then MQTT/Sparkplug) β€” both plans πŸ“ ready. MTConnect's browse leg wants #468 closed first; MQTT's Task 0 pinning spike gates everything after it. Update this file's Summary table and per-wave status whenever a deliverable changes state.