One alarm. The whole context.

Not Explain, not Decide. Wavepin Explain names the physical cause of one pipeline alarm where a line model exists; otherwise the alarm text stands. Wavepin Decide simulates line responses. Alarm joins any alarm to consequence, planned work and the rehearsed response.

The incident twin and its one-alarm-with-the-whole-context flow (telecom harness, separate codebase), recorded from real MCP calls: read, what-if, refuse, dry run. The harness session over MCP. Structural-break detection for floods. Wavepin's hypothesis engine, typed decision and deterministic safety validator; the read-only adapter framework; per-step receipts for the shift view. Not built: alarm-journal and historian adapters, the consequence and planned-work inputs, the oil and gas drill library. The shift-handover view (the 192.631(b)(4) / 195.446(b)(4) shift-change record assembled from receipts plus one SCADA export) follows on the same code; the live overlay beside the SCADA display needs a replica and an on-premises bench.

Replay one month of an anonymised alarm-log export through the flood finder (count, duration, peak rate, decay after rationalisation) and the monthly point review; compare flood counts and peak rates with the operator's own KPI report. No connection, no write access. In parallel, the public-data demo on the simulated 20 km line (one straight line, one product, no branches, no batches, no gas; 12,800 simulated scenarios): pressure drop at 02:14, pump trip at 02:31, delivery at risk by 03:01, decided with context, receipts and a dry-run dispatch. The reel on the site today is the telecom session; the oil re-cut is pending.