A respectful, evidence-first read of Edison International / Southern California Edison's public web surface and public regulatory record (CPUC / Energy Safety): what an investigator, an insurer, or an AI agent can and cannot verify today, and the one layer that would change it. Baseline credited first; then four findings, each reproducible from a URL and an HTTP status.
SCE runs one of the most technically serious public safety programs in the utility sector, and its surface shows real maturity:
The gap is not effort or sophistication. It is that after inviting the agents in and spending billions on the work, the completion of that work is still an internal record no third party can independently verify.
When a fire sparks a claim or an audit, the decisive question is whether a specific span was cleared on a specific day; a signed, photographed completion receipt turns SCE's billion-dollar effort into evidence a court or insurer can check: the strongest possible posture where wildfire liability is existential.
Edison already invited the AI agents in, then left nothing for them to act on; handing them a structured menu means the assistants shaping how investors and regulators see SCE work from SCE's own words, not guesses.
The wildfire plan is a giant PDF today, so an AI asked whether SCE is on track has only prose to guess from; publishing the key commitments as structured data, backed by per-task receipts, gets them read once and read right by every regulator portal and ESG rater.
Vegetation management, pole brushing to a clearance spec, and asset inspection are go-to-a-location → do-a-bounded-task → record-who-did-it-when-and-where. That is the EcoWealth Work Protocol lifecycle exactly. In a post-ignition proceeding, a subrogation claim, or an Energy Safety audit, the decisive question is whether a given span was cleared to spec on a given date. Today that lives in internal work-management systems; there is no object an investigator, insurer, or court can independently verify without discovery.
urban_canopy_survey 511 · civic_hazard_survey 352 · riparian_buffer_survey 22 · stormwater_maintenance_clearing 48 · clear_invasive_brush · construction_site_safety_walk 44. Re-verify: curl -s https://vealth.net/labor/statsedison.com's robots.txt is unusually forward: it names and Allows GPTBot, ChatGPT-User, OAI-SearchBot, OAI-AdsBot, ClaudeBot, Google-Extended, PerplexityBot, and CCBot. But when those agents arrive, there is nothing machine-actionable to act on: /llms.txt (the file AI assistants read first) and /ai.txt are true 404s, /.well-known/agent-card.json (a file that lets other AI agents discover and call you) is a 404, and both edison.com and sce.com homepages carry 0 application/ld+json (schema.org/JSON-LD: the invisible labels search engines and AIs read). The invitation is real; the room behind it is empty.
llms.txt, an agent card, JSON-LD on the WMP and safety pages. The agent kit in this concept drafts all of them.curl -s https://www.edison.com/robots.txt | grep -iE 'gptbot|claudebot|perplexity' (present) then curl -s -o /dev/null -w '%{http_code}' https://www.edison.com/llms.txt → 404; curl -s https://www.edison.com/ | grep -c 'application/ld+json' → 0.The 2026–2028 WMP is published as a large PDF on sce.com, and the ESG / sustainability material on edison.com is prose. Neither homepage carries structured data (0 ld+json each). An AI agent asked "what did SCE commit to in vegetation management, and is it on track?" has only PDF prose to parse, inconsistently, if at all.
curl -s https://www.sce.com/ | grep -c 'application/ld+json' → 0; curl -s https://www.edison.com/ | grep -c 'application/ld+json' → 0.edison.com returns Strict-Transport-Security: max-age=300, a five-minute HSTS window, versus the one-year (31536000) standard that sce.com and the other peers in this set publish. A 300-second max-age provides almost no real protection against SSL-stripping between visits. Neither edison.com nor sce.com publishes a security.txt, so a researcher who finds an issue has no standard disclosure channel.
includeSubDomains), and add a security.txt. Small, standard hardening for a critical-infrastructure holding company.curl -sI https://www.edison.com/ | grep -i strict-transport → max-age=300; curl -s -o /dev/null -w '%{http_code}' https://www.edison.com/.well-known/security.txt → 404.A vegetation-clearance or inspection task on a specific span becomes an EWP proof-verified work packet: bounded scope with hazard framing, claimed by a line/veg crew, closed with photo + GPS + signature proof scored by a deterministic proof-checker, and settled to a permanent receipt on Base. Each receipt appends to that circuit's, and that contractor's, verified wildfire-work history: the independently-checkable, court-grade upgrade to an internal completion record.
Live proof it's not slides: EWP contract 0x76c17C…A14B on Base mainnet (source-verified, first settled packet workId 14); the priced tool menu at vealth.net/.well-known/x402; and the end-to-end building-agent golden path.
| Step | What ships | Who owns it |
|---|---|---|
| 0 · Prove it (today) | One agent pays $0.10 to work-packet; one funded clearance/inspection packet in SCE's SoCal territory settles on-chain. | EcoWealth rail, live now |
| 1 · Fill the open room | llms.txt + agent card + JSON-LD on the WMP/safety pages (the crawlers are already welcomed) + edison.com HSTS + security.txt. | Edison/SCE web team (drafts provided) |
| 2 · Proof pilot | 10 clearance/inspection packets across one high-fire-risk circuit, each closed with proof + settled; verified wildfire-work history per contractor. | Joint, bounded scope |
| 3 · Standing rail | Completion receipts as the default output of WMP field work; tCO2e mapping where restoration applies. | Operator decision |
Two figures, both pocket change against a $6.2B wildfire program, and in your own service area:
work-packet endpoint and gets a bounded, hazard-framed packet back, keyless. Dry-run client: vealth.net/recipes.html.