Incident logs at water utilities are built to answer operational questions: which main broke, which pump tripped, how long a zone stayed under a boil notice. They were not built to answer questions about intent. When an interruption comes from a deliberate act, the record has to show that, and the way a utility sets its cause codes decides whether anyone can later separate that category from ordinary failure.
What the source describes
Circle of Blue published an interview by Brett Walton with Peter Gleick on the rise in water violence, available as Circle of Blue's interview with Peter Gleick. The published summary notes that for people living through war, "daily life is more dangerous than in conflicts past," and it lists the possibility that "Your water supply could be cut" among those dangers, alongside exploded dams. This article works only from that summary, so it makes no claim about the full argument of the interview.
Why violence falls through the cracks
Most incident taxonomies sort events by mechanism: a main break, a power loss, a treatment train failure, a backflow event, a contamination detection. Deliberate damage does not fit that structure cleanly, so it lands in an "other" field or in whichever mechanism it produced. A pump station destroyed by an attacker can be logged as equipment failure. A chemical release can be logged as a process upset. The mechanism is accurate, but the cause disappears from the record. A year-end count then shows a rise in equipment failures with no indication of why.
The fix is not a single new category. A cause field that mixes physical mechanism with actor intent will fail in both directions. Keep the two apart. The mechanism field records what physically happened: physical damage, loss of power, loss of pressure, chemical release, or loss of control system access. A separate intent field records what the utility currently knows about cause, with values such as unknown, natural, accidental, deliberate, and under review. The "under review" value matters most in the first days, when staff cannot yet tell a vandalized valve from a corroded one.
The tradeoffs
Recording intent carries a cost. A deliberate-act entry may be sensitive, may be requested under public records rules, and may describe weaknesses that should not circulate widely. Utilities should decide in advance which fields go to regulators, which go to the board in summary form, and which stay with security staff. The tension is real, and it is easier to resolve in a written policy than during an active event.
Revisions need a rule too. An incident record should never be overwritten when the cause changes. A first entry marked "under review" stays in the log, and a later entry states the new value, the date of the change, and the staff member who made it. Without that trail, a count built in January can disagree with one built in June, and no one can say why.
Laboratories have a separate stake. A sample drawn after a deliberate release looks like any other contaminated sample on the bench, and the result does not carry its cause. If the sample record lacks the incident identifier and chain of custody, a later reviewer may read the result as a treatment problem and change a process that was working. The safer practice is to link each sample to the incident number at collection, not at reporting.
The household end
The same question reaches homes. When service stops and returns, household equipment such as pressure tanks, softeners, and under-sink filters can be damaged, and a homeowner's question about who pays for repairs is separate from the utility's cause code. Households weighing coverage for home systems and appliances should keep their own dated notes, photographs, and service receipts from the event, because the utility's record will not describe the household's losses.
A count is only as informative as its categories. A utility that cannot say how many interruptions were deliberate cannot judge whether its security posture is changing, and it cannot tell its board whether a rise in equipment failures reflects a maintenance problem or something else. Fill the intent field before the next event, not after it.