Product · Program
The programme record. With receipts.
Your leak-detection and valve-rule programme as a compiled contract: KPIs, tests, drills, the 30-minute closure and the 90-day review. Rehearsed on a twin. Run across the detection systems whose logs you export, read-only, with a signed quarterly pack.
In designDesigned from existing building blocks. Not built.
1
KPIs and targets as a checked contract
2
Drills rehearsed and timed on a twin
3
Signed quarterly pack; 90-day receipts
Needs
- The written procedures and emergency plan
- Detection alarm and test logs, as exports (one loader per vendor, built per pilot)
- A procedures writer for the library
Is not
- Not a leak-detection system
- Never executes on DCS or SCADA
- Not an audit of your vendors
Where it stops
Scores detection systems from their logs; Wavepin Leak is one of them. The 30-minute closure applies to transmission and hazardous-liquid lines; the valve rule was vacated for gathering lines.
Built from
What exists, what does not
The Playbook engine (telecom harness, separate codebase): contracts checked, rehearsed, scored, compiled, fired by an event, receipts per step, approvals before any change. The request handoff: done-when lines, evidence, a party, a clock, independent acceptance. Wavepin's benchmark tournament on the simulated 20 km line (one straight line, one product, no branches, no batches, no gas; 12,800 simulated scenarios). The deterministic twin core for drills. The signed pack and the append-only ledger. Not built: the oil and gas standard library, loaders for third-party detection logs, the valve-rule timing contracts. The intent grammar is not public; the compiler boundary is an intermediate representation.
First proof
The experiment
Compile one public procedure shape, the response to a notification of potential rupture (evaluate, close valves within 30 minutes, record, review within 90 days), with a five-mechanic library: hold point, approval, clock, evidence, request. Rehearse it on the simulated line with a rupture scenario; feed the 12,800-scenario results in as the test set. Show the check report, the dry run, the 30-minute request with its clock and independent acceptance, the signed quarterly pack and the 90-day receipt. Labelled simulated. Then one month of a partner's detection alarm log, read-only, into the same pack.
Methods
- Moving-horizon leak detection, localisation and size estimation (the research-backed test scenarios)
- Benchmark tournament: detection probability, time to detect, localisation error, false-alarm rate
Rules and standards
- API RP 1175, Pipeline Leak Detection Program Management (2nd ed., April 2022)
- PHMSA valve rule (87 FR 20940, 8 April 2022): rupture-mitigation valves; closure within 30 minutes of rupture identification; post-failure review within 90 days
- 49 CFR 195.402: procedures manual for normal, abnormal and emergency operations
- Rupture-mitigation valve rule: recordkeeping notice (Federal Register, 31 July 2025)
Also
See Program on your asset.
Designed from existing building blocks. Not built. A conversation first; a data pilot when it is ready.