Story 01 — The Silent Optic of Coastal Bend

Riverflow · tenant delta · sensor S041 at site SITE_CF. A field note. See The EDA Book for the principles behind it.

A map full of grey

It started with a map that wasn’t saying anything.

The Riverflow field-network map plots every sensor at its river coordinates, and it’s supposed to colour each marker by health. Instead: a field of uniform grey. Thirty-one river sites, every dot the same slate.

That was the first finding — and a quiet lesson. The map was colouring sites (keyed by site_id) using a sensor-level signal (keyed by sensor_id). The keys never matched, so every marker fell through to the default colour. The tool itself wasn’t listening. We taught it to — a small bridge that re-keys a sensor’s health onto the site where it’s deployed (gold_sensors.current_site_id) — and the map came alive: twenty-two sites lit up, twenty-one amber, one red.

(Principle: look first. Before any conclusion, get the picture to actually render the data. A grey map isn’t “no problems” — it’s “not listening yet.”)

One red among the amber

Twenty-one amber sites is a pattern — a broad tail, probably firmware. One red site among them is a question. Resistance says the summary is “the fleet is mostly fine, with a firmware tail.” The single red outlier says: go look at that one.

So we did. We pointed at the dot and asked the only EDA question that matters — why is that one different? — and jinflow answered.

Following the light

The red dot is SITE_CF, “Coastal Bend”, in watershed WS_CASCADE. The sensor deployed there is S041 — an RK2-Plus, serial RK2P-A-2542, running firmware FV_1_2_9. Status: active. Days since last seen: 42.

That last pair is already a contradiction. Active, but not seen in six weeks.

Two signals fire on S041:

• deprecated firmware — medium. FV_1_2_9 is an old build.
• datastream inactive — high. This is the red. The sensor has gone silent while the rest of the fleet keeps reporting.

The raw measurements confirm it, coldly. S041’s last reading — across temperature, turbidity, and level — is 2026-06-02. The dataset runs to June 30. It went dark almost four weeks ago, and nobody pulled it. It’s still sitting in the roster as “active,” faithfully being counted, saying nothing.

The tell was in the turbidity

Here the picture forced us to notice something we hadn’t gone looking for.

Split S041’s readings by what it measured, and one column is different:

Property	Readings	Suspect (bad quality)
Water temperature	5,136	0
Water level	5,136	0
Turbidity	5,136	73

The thermistor and the pressure sensor were clean to the end. The turbidity optic was throwing bad readings — 73 of them — before the device went quiet. The optic was failing first.

That’s a residual worth its weight: not the silence itself, but the texture just before it. A story assembled:

Deprecated firmware → a degrading turbidity optic → total silence. A sensor that was already lying (in one channel) before it stopped talking altogether.

Why one dot mattered

This isn’t a curiosity. S041 is the single finding behind the tenant’s fleet_reliability_risk thesis being plausible. One silent sensor at Coastal Bend is, right now, the fleet’s entire strategic-risk case. The red dot on the map and the amber verdict in the diamond are the same fact, seen from two heights.

The tool the story asked for

There was a gap. When you brush a site on the map, a chart of its stream slides up — but it was showing temperature only. And the trouble here lived in turbidity. The exploration had found the thing it couldn’t yet see.

So the story earned a tool: a Temp / Turbidity / Level toggle on the brushed chart. Now, clicking Coastal Bend and switching to Turbidity draws exactly what we deduced — the suspect readings scattered through the spring, and then the trace stopping dead at the start of June.

(This is the loop the whole book is about: explore → find → build → see. The finding told us which instrument we were missing; we built it; and it showed the finding its own face.)

Listen, then talk

The thing to keep from Coastal Bend isn’t the sensor. It’s the motion.

We listened: the map, once it could speak, showed one red among the amber. Then we talked back: pointed at the dot, and the whole picture answered — the site named itself, the signals surfaced, the stream drew its own death, the quality flags confessed the optic. Listen, ask, answer, ask again. That back-and-forth is EDA in jinflow, and it’s how a single grey field turned into a named failure with a cause and a date.

Try it yourself

1. Open the Riverflow field-network map for delta.
2. Find the red marker — Coastal Bend.
3. Click it. The stream answers, and the marker takes a halo.
4. Toggle to Turbidity. Watch the optic degrade, then fall silent on June 1.
5. Ask the next question. There are still two other silent sensors on that map — do they share the story?

Miss EDA · the lighthouse points; we follow. 🌊