Build the application

## Build
Simulate district cooling pipe isolation to coordinate emergency customer shutoffs while preserving fire-flow pressure. Formulate valving plans that maintain regulatory network pressure thresholds.

## User
District cooling hydraulic engineers and municipal water network dispatchers

## Workflow
1. Ingest pipe segment isolation requests and customer cooling supply connection coordinates.
2. Simulate hydraulic pressure variations and residual flows using WNTR distribution network modeling.
3. Identify downstream tenant chilled water heat exchangers starved below critical delta-T thresholds.
4. Assemble an isolation valving schedule and bypass pumping plan for engineering director approval.

## Interface
Interactive pipe topology schematic highlighting isolated loops, boundary valves, and customer pressure alarms.

## Data
Use WNTR synthetic network INP models adapted for dual-pipe district water and cooling networks.
Starter examples below are synthetic. They are not downloaded records.

## Source
[Water Network Tool for Resilience](https://raw.githubusercontent.com/USEPA/WNTR/main/README.md)
Uses WNTR network simulation objects to evaluate pressure-dependent demands and isolation valving impacts.

## Tools
langgraph, pydantic-ai, wntr.
langgraph structures the multi-step cycle of network isolation, pressure recalculation, and mitigation routing.
Hosted LLM API capable of validating hydraulic simulation state and drafting procedural isolation runbooks.

## Deliverables
Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.

## Acceptance
- Simulates pipe isolation valves to determine impacted customer junction nodes using WNTR.
- Flags any connected customer junction experiencing pressure drop below minimum service levels.
- Generates a step-by-step valve closing and reopening sequence to prevent hydraulic water hammer.
- Requires signed operational authority sign-off before simulated isolation plans can be marked verified.

## Starter Examples
```json
[
  {
    "input": {
      "isolation_pipe_id": "P-402",
      "valve_ids_to_close": [
        "V-12",
        "V-13"
      ],
      "network_nodes": [
        {
          "node_id": "J-80",
          "base_pressure_bar": 4.5,
          "customer": "MALL-RETAIL"
        },
        {
          "node_id": "J-81",
          "base_pressure_bar": 4.2,
          "customer": "HOTEL-TWR"
        }
      ],
      "min_required_pressure_bar": 2.5
    },
    "expected_output": {
      "isolation_possible": true,
      "lowest_post_isolation_pressure_bar": 3.1,
      "isolated_customers": [],
      "valve_sequence": [
        "V-12",
        "V-13"
      ],
      "advisory": "Hydraulic bypass active via Loop-B; pressure remains acceptable."
    }
  },
  {
    "input": {
      "isolation_pipe_id": "P-101",
      "valve_ids_to_close": [
        "V-01",
        "V-02"
      ],
      "network_nodes": [
        {
          "node_id": "J-05",
          "base_pressure_bar": 3.8,
          "customer": "FINANCIAL-CTR"
        }
      ],
      "min_required_pressure_bar": 2.5
    },
    "expected_output": {
      "isolation_possible": false,
      "lowest_post_isolation_pressure_bar": 0,
      "isolated_customers": [
        "FINANCIAL-CTR"
      ],
      "valve_sequence": [],
      "advisory": "Isolation isolates FINANCIAL-CTR completely; mobile bypass pump required."
    }
  }
]
```

## Safety
Simulation environment only; network valve operations must follow physical tagging and lock-out procedures. Examples are simplified synthetic app records, not complete official schema files.
Use mock external writes. Require human review before any real deployment.