MajiShiftRESERVOIR OPERATIONSWorking prototype

JKUAT PILOT EXPLORATION / 7-DAY PLANNING

Keep the reserve.
Plan the next move.

Compare a fixed pumping schedule with a plan that prepares for interruptions.

About the inputs

Mixed-evidence scenario. Official Conduit CSV observations from 29 Aug-4 Sep drive daily rainfall and temperature-derived reference evapotranspiration in this replay. Dam storage and operating values remain editable assumptions.

CONDUIT@EMPATHY · STATION 61

JKUAT observation

Connecting

Reading the latest station observation…

Open source platform ↗

ADAPTION ACTION MODEL

Observation to operator brief

Conduit conditions and the checked water balance form the model context. The adapted model turns that context into a short, localizable explanation; it never changes the calculated volumes.

Conduit data→Water balance→Adaption brief→Operator review

Integration state: Adaptive Data completed 160 rows. The first 30B AutoScientist run trained for three iterations and scored 53.71% against an 80% target. The enhanced-label experiment also completed three iterations and scored 55.67%. The corrected fused-context 4B run completed at 53.45%, so it did not beat the enhanced 30B result. Model serving and held-out validation are not connected yet.

Explore a situation

Lowest end-of-day reserve

5,007 m³Proposed schedule

Days below reserve

0 / 7Fixed schedule: 5 days

Essential demand unmet

0 m³Covered in this scenario

CONDUIT TO DECISION IMPACT

Weather data adds 36 m³ of estimated seven-day surface loss

The official station history recorded 0.0 mm rain across this replay. Conduit temperature ranges produce 32.4 mm of FAO-56 Hargreaves reference evapotranspiration, compared with 28 mm from the fixed assumption. The proposed schedule pumps 0 m³ more and its minimum storage changes by -15 m³.

This is a historical counterfactual replay using real Conduit weather and synthetic reservoir operations. It demonstrates the decision contribution without claiming a forecast or measured dam evaporation.

CAMPUS WATER ATLAS

See the plan in place.

The dam and campus reference come from OpenStreetMap. Station 61 is placed from the Conduit observation feed. Supply connections still need operator confirmation.

Loading campus context…
Open-map dam + Conduit stationTopology pending operator review

Basemap © Esri and the GIS User Community · Building context © OpenFreeMap / OpenStreetMap contributors. Map geometry does not establish storage capacity, pipe routes or service outcomes.

STORAGE OUTLOOK

Two plans. One water balance.

m³ · daily steps
02,2504,5006,7509,000StartDay 1Day 2Day 3Day 4Day 5Day 6Day 7
Proposed scheduleFixed scheduleMinimum reserve

THE NEXT MOVE

Plan 4.5 hours of pumping on day 1

Build a buffer before 2 unavailable pumping days. Future rainfall is not counted on for that buffer.

The end-of-day reserve target is met throughout this scenario. Operator review is required before real use.

PROPOSED OPERATING PLAN

Every day, accounted for.

DayDateRain (mm)Ref ET (mm)Pump (h)Irrigation (m³)End storage (m³)Status
Day 12026-08-290.04.74.52508,437Reserve met
Day 22026-08-300.04.30.0 · unavailable2506,752Reserve met
Day 32026-08-310.03.50.0 · unavailable2505,075Reserve met
Day 42026-09-010.04.66.52505,013Reserve met
Day 52026-09-020.05.27.02505,071Reserve met
Day 62026-09-030.05.06.52505,007Reserve met
Day 72026-09-040.05.17.02505,065Reserve met

Essential use is served before irrigation. Irrigation not served: 0 m³. Pumped volume: 7,875 m³. Overflow: 0 m³. Daily balance does not establish intraday availability.

A plan is only as good as its inputs.

This is a daily scenario calculator, not a validated digital twin or a live dam-control system.

What is connected?

The official Conduit CSV supplies measured daily rain totals and temperature ranges for a seven-day historical replay. Temperature drives a transparent FAO-56 Hargreaves reference evapotranspiration estimate, which changes water loss, storage and pumping outputs. The live endpoint adds current context when available; no upstream river-flow prediction is made.

Conduit data platform ↗

Next: the operator meeting

If the team advances to the October event, replace the synthetic operator layer with approved storage, pumping, demand and outage records before making operational claims.

Adaption processed 160 rows and produced a 30B checkpoint after three AutoScientist iterations. Its 53.71% win rate remains below the 80% target. The enhanced-label experiment also completed three iterations and scored 55.67%. The corrected fused-context 4B run completed at 53.45%, so it did not beat the enhanced 30B result. Every checkpoint still needs held-out validation and a separate serving endpoint before it can generate briefs here.