WATERSHED
MEMORY
RECORDED AGENTCORE EXECUTION

FOR THE TEAM PROTECTING A DRINKING-WATER SOURCE

Three storms.
One memory.

After wildfire, the next storm can bring ash and debris into a water supply. The team’s work must carry forward with every new observation.

Watershed Memory connects new evidence to unfinished reviews, flags missing station evidence, and keeps the operator’s response with the case.

Recorded AgentCore execution · historical 2022 observations

GALLINAS, NEW MEXICO / FOUR RECORDED MOMENTS

Watch the work stay connected.

RECORDED EXECUTION

Loading the recorded run…

The saved case will appear here.

THE WORK BEHIND THE MOMENT

New sessions.
The same responsibility.

01

Strands selects the work.

The agent reads the saved case and source observations, then proposes the review and its evidence links.

02

AgentCore runs the turn.

August and September execute in separate cloud sessions. Each returns a proposal that the case service validates.

03

The case carries forward.

The external ledger keeps evidence, acknowledgments and request receipts. A repeated request returns the saved result.

The stakes are real: in July 2022, Las Vegas, New Mexico declared a disaster over flooding, ash and fire debris threatening its water supply. Read the official NMED account ↗

How this moment was executed
Verified behavior and source version
Historical evidence and attribution

Derived from Nichols et al. (2024), Gallinas field archive v1.0.1, under CC BY 4.0, with USGS gauge summaries. Changes include extraction, counting, summaries, unit conversion and inferred MDT timestamps. Full data attribution. Observation availability is simulated; station coverage describes the archive.