🚧 WIP

README.md

@@ -10,9 +10,12 @@ disconnects, hung RPC calls, tags marked BAD/UNCERTAIN, stale timestamps, frozen
 and flapping quality — as structured events (JSONL logs, Windows Event Log, optional
 HTTP webhook).
 
-> **Status:** planning. Read the
-> [specification](docs/SPECIFICATION.md) and the
-> [implementation plan](docs/IMPLEMENTATION_PLAN.md) first.
+> **Status:** in active development — discovery, browsing (`list-items`), one-shot
+> reads (`read`/`probe`) and the exe build are **live and field-verified** against a
+> real server; the continuous monitoring loop, reporters and Windows service host are
+> next. See the [TODO](TODO.md) for current status and the
+> [implementation plan](docs/IMPLEMENTATION_PLAN.md) for the phases; read the
+> [specification](docs/SPECIFICATION.md) for detection rules and behavior.
 
 ## Why
 
@@ -126,6 +129,15 @@ tags:
   - { name: "Channel1.Device1.Counter", expect_change: true }
   - { name: "Channel1.Device1.Level" }
 
+# D16 device-link indicators: tags saying whether the OPC server can reach
+# the device. DOWN (DEVICE_LINK_DOWN, CRITICAL) when the tag reads non-GOOD,
+# errors, or its GOOD value is NOT in ok_values. ok_values defaults to [true]
+# (boolean connected flags); inverted fault flags -> [false, 0]; string
+# states -> ["RUN"]. Do NOT also list these under tags:.
+devices:
+  - { name: "Conveyor 3", tag: "Channel1.Device3.Connected" }
+  - { name: "Pump A", tag: "Channel1.PumpA.Fault", ok_values: [false, 0] }
+
 latency:
   warn_ms: 1000
   critical_ms: 5000
@@ -257,6 +269,8 @@ Deployment notes:
 
 - [Specification](docs/SPECIFICATION.md) — detection rules, event model, operational behavior, acceptance criteria
 - [Implementation plan](docs/IMPLEMENTATION_PLAN.md) — phases, milestones, testing, risks
+- [TODO](TODO.md) — implementation status: what's done, what's next
+- [Changelog](CHANGELOG.md) — notable changes per release
 
 ## License