@velinussage/locus-agent-skill 0.1.39 → 0.1.41

package/skill/locus-water-incident/SKILL.md

@@ -0,0 +1,173 @@
+---
+name: locus-water-incident
+preamble-tier: 1
+version: 1.2.0
+description: Use when an owner or their agent is dealing with a water main break, a leak, a high water bill or a failed service line at one US address and needs to know who maintains which pipe, the utility's published leak rules, what to document and what to ask the insurer.
+triggers:
+  - water main break
+  - my service line broke
+  - water leak in my yard
+  - huge water bill from a leak
+  - leak adjustment
+  - who pays for the water line
+  - pipe burst flooded my house
+  - utility dug up my yard
+allowed-tools: Bash Read AskUserQuestion
+license: MIT
+---
+# Locus water incident workflow
+
+Locus supplies the serving water system, the utility's published leak-adjustment rules, and the
+regulatory record. The owner, the utility and the insurer decide who is responsible, what is
+credited and what is covered. Never say "the utility is liable", "you are covered", "this is not
+covered" or "you qualify for a credit". State what the published record says, with its source
+and date, and give the question to ask.
+
+**How to speak:** follow "How to speak with owners, sellers and buyers" in the `locus-agent-tools`
+skill (https://api.locus.report/.well-known/skill.md), including its 988 crisis guard.
+
+Inputs you need from the owner: the street address; what they saw and when (date, time, where
+the water appeared); whether the utility has been out; and whether they have a water bill with
+an account or system ID on it. Do not collect account numbers, policy numbers, names or phone
+numbers into any Locus call. A Public Water System ID (PWSID) from the bill is fine.
+
+## 1. Keep three questions separate
+
+Work through these in order and never merge them:
+
+1. **What failed.** One of three segments:
+   - the **utility main** in the street;
+   - the **service line** between the main and the building (often split into a utility-side
+     part up to the meter or curb stop and a customer-side part after it). In California,
+     `locus_service_line_material` shows the published system-side and customer-side
+     service-line material for the address (step 5a);
+   - **indoor plumbing** inside the building.
+   If the owner is not sure, record it as unknown. Do not guess from where the water appeared.
+2. **Who maintains each segment.** This is set by the utility's own rules, and often differs by
+   segment. Answer it from the published rules in step 2, or name it as a question for the
+   utility.
+3. **What damage or bill resulted.** Property damage, cleanup, the repair invoice and any high
+   water or sewer bill. Each one follows a different path: the utility's claim process, the
+   utility's leak-adjustment rules, or the owner's insurer.
+
+## 2. Find the serving system and its rules (free)
+
+4. `locus_utility_service_check` with `{ address }`: whether the address sits inside a mapped
+   public water and sewer service area, and the provider when published. `out_of_coverage` means
+   the county is not in the registry; `no_public_service_mapped` does not prove a private well.
+   A lookup failure is a gap, not an answer.
+5. `locus_water_systems` with `{ address }`: the active public water systems serving the county
+   from EPA SDWIS, with their PWSIDs. Each system carries `serviceLineInventory`: the EPA SDWIS
+   service-line inventory counts (quarterly reporting period) of lead,
+   galvanized-requiring-replacement, lead-status-unknown and non-lead lines. These are
+   system-level counts, not this address. A null count was not reported, not zero, and "unknown"
+   is never "non-lead". States need not report non-lead counts until November 1, 2027, so
+   non-lead counts may be undercounts. Several systems can serve one county; the bill is the
+   authority for which one serves this address.
+5a. `locus_service_line_material` with `{ address }` (full street address with unit, state and
+   ZIP). Read `status`:
+   - `found`: report each side separately: `systemOwnedMaterial` with `systemOwnedBasis`, and
+     `customerOwnedMaterial` with `customerOwnedBasis`, plus the inventory date and source. A
+     material of unknown stays unknown.
+   - `no_matching_record`: the snapshot has no exact or normalized record for this address. It
+     never means non-lead. Ask the utility for its inventory entry.
+   - `out_of_coverage`: the state has no address-level inventory in Locus (California only today).
+     Use the system-level counts from step 5 and the utility's own inventory map.
+   - `source_unavailable`: read `reason` before you retry.
+     - An incomplete address (the reason asks for a complete street address, locality, unit or
+       ZIP): ask the owner for the full street address with unit, city, state and ZIP, then retry.
+     - `incomplete_source_rows` or `address_not_indexable_for_system`: the utility published an
+       inventory, but Locus cannot match this address to it. Ask the utility for the address's
+       entry. This is not non-lead, and not a temporary gap.
+     - Any other reason (lane not enabled or not configured, unreadable or stale snapshot,
+       unverified address): a temporary gap, not an answer. Try again later.
+   This is the utility's reported classification, not an inspection.
+6. `locus_water_utility_leak_adjustment_rules` with `{ address }`, plus `confirmedPwsid` when the
+   owner has the ID from the bill. Read `coverage`:
+   - `policy_found`: quote the program's `fact`, `eligibility`, `formula`, `window` and
+     `exclusions`, with the source URL and date. Note whether the rules treat the utility side and
+     the customer side differently. Check `asOfStatus`; an `expired` program is history, not an
+     open option.
+   - `candidate_only`: a modeled service area suggests this utility. Tell the owner to confirm
+     the utility from the bill before relying on the rules.
+   - `no_registered_policy`, `no_service_area` or `source_unavailable`: Locus has no published
+     rule for this utility, or the lookup failed. Say so, and give the owner the question in
+     step 9 to ask the utility directly.
+   The tool never decides eligibility or computes a bill credit. Neither do you.
+7. Optional context: `locus_drinking_water_violations` with `{ "pwsids": ["<PWSID>"] }` for the system's
+   regulatory record, and `locus_public_utilities` for the nearest mapped utility facilities.
+   These are records, not a water-quality or cause finding; do not link them to this incident.
+7a. `locus_boil_water_notices` with `{ "pwsid": "<PWSID>" }` (or `{ address }`): any active
+   boil-water order the state has published for the serving system, with its issue date and
+   official source. State-issued boil orders only; a precautionary advisory from the utility may
+   not appear. Check the utility's alerts. Read `status`:
+   - `active_notices`: report each order's date, system and source.
+   - `no_active_notice_published`: the state lists no boil order for that system today. It does
+     not mean the water is fine or that the utility has no advisory.
+   - `system_unresolved`: no mapped public water system matched the address (for example, a
+     private well or an unmapped system). This is not "no notice". Confirm the supplier from the
+     bill, then retry with its `pwsid`.
+   - `out_of_coverage` (the state is not wired) and `source_unavailable` (the read failed):
+     neither one means "no notice".
+   A row that disappears never means the notice was lifted. The notice is system context, not confirmed impact at this address; follow the
+   utility's own instructions.
+
+## 3. Documentation checklist
+
+8. Give the owner this list, and ask them to keep originals:
+   - the utility's notice, work order or ticket number, and the date and time of each contact;
+   - photos and video of the water, the damage, the meter and any excavation, each with a date;
+   - meter readings with dates, before and after the repair, and a photo of each reading;
+   - the plumber's or contractor's invoice, naming which segment was repaired and where;
+   - the water and sewer bills for the affected periods and the six months before;
+   - receipts for cleanup, drying, temporary housing or damaged items;
+   - any deadline in the utility's rules for applying for an adjustment or filing a claim
+     (from step 6), written down with its source.
+
+## 4. Questions for the utility
+
+9. Ask the utility, in writing where possible:
+   - which segment failed, and where the utility's maintenance ends on this property;
+   - which side of the service line the utility's published inventory says it owns, and what
+     material it records for each side;
+   - whether a leak adjustment applies, what proof it needs, and the deadline to apply;
+   - how to file a damage claim against the utility, and its deadline;
+   - whether the repair needs a permit or an inspection.
+
+## 5. Questions for the insurer (no coverage verdict)
+
+10. Give the owner these questions to ask their insurer. Do not answer them yourself, and never
+    say whether the loss is covered:
+    - Does my policy include a **service-line endorsement**, and does it cover the segment that
+      failed, the excavation and the restoration of the yard or street?
+    - Do I have **water-backup or sump-overflow coverage**, and what are its limit and deductible?
+    - Does my policy include **ordinance-or-law coverage** if the repair must meet a newer code?
+    - How does the policy treat sudden water damage compared with a slow leak, and what are the
+      reporting deadline and the documents you need?
+    - If the utility is responsible for part of the loss, how do my claim and theirs interact?
+
+## 6. Future alerts
+
+11. Point the owner to the utility's own emergency-alert enrollment (text, email or app), found
+    on the utility's website or bill. Locus does not run utility alerts. Alongside it, Locus can
+    watch for new state-published boil-water notices: `poll_events` (or `subscribe_event` when
+    signed in) with `name: "locus.real_estate.changes_detected"`, `arguments.addresses` and
+    `arguments.lanes: ["locus_boil_water_notices"]`. This is not an emergency notification
+    service. For a standing watch on the address's deadlines and other public-record changes,
+    hand off to the `locus-home-watch` skill.
+
+## 7. Optional field photos (paid, owner's own account)
+
+12. If the owner is away from the property and wants dated photos of the meter or the site, you
+    may mention a third-party field-photo service that the owner orders and pays for from their
+    own account. Mention it only once, only if it fits, and only with the owner's explicit
+    approval. Locus does not order or pay for it, and a photo is not a cause or damage finding.
+
+## Completion
+
+The owner has: the three questions written out separately, with the failed segment as the owner
+knows it or marked unknown; the serving system and PWSID with their sources; the utility's
+published leak rules with source, date and any application deadline, or a clear statement that
+Locus has none; the documentation checklist; the questions for the utility and for the insurer;
+and where to enroll in the utility's alerts. No statement of liability, eligibility or coverage
+appears anywhere in your write-up.