Add regional DHMV provisioning

docs/DATA_SOURCES.md

@@ -385,8 +385,9 @@ quality metrics.
 - Native raster: 1 m Float32, EPSG:31370, nodata `-9999`, hoogte in TAW
 - Opnameperiode: 2013-2015; geen uniforme recente peildatum
 - Cache: canonical raster Dataset plus WCS request/response/output checksums
-- Operator: `scripts/provision_mol_dhmv.py`
-- Prioriteit: P4 uitgevoerd voor Mol
+- Operators: `scripts/provision_mol_dhmv.py`,
+  `scripts/provision_regional_dhmv.py`
+- Prioriteit: P4 uitgevoerd voor Mol en operationeel regionaal uitbreidbaar
 
 The operator requests a bounded 5 m analysis copy by default so a complete
 municipality remains operationally manageable while retaining the official
@@ -396,6 +397,12 @@ DSM includes buildings and vegetation. Neither is exposed as water depth,
 water volume or a directly measured building-height product. A drainage model
 would require a separately governed hydrological processing pass.
 
+De regionale operator gebruikt exact de 28 persistente gemeente-Areas van de
+goedgekeurde Kempen-scope en plant twee outputs per gemeente. Die 56
+gemeentepartities vermijden een onnodig monolithisch hoogtebestand, blijven
+binnen WCS/pixelgrenzen en sluiten aan op de gebiedsgebonden datasetselectie in
+de kaart. Herhaalruns gebruiken de bestaande checksummed requestcache.
+
 ## VMM overstromingsgevaarkaarten
 
 - Naam: Overstromingsgevaarkaart Waterdiepte

docs/STORAGE_ARCHITECTURE.md

@@ -118,6 +118,13 @@ metadata records the 1 m native product, 5 m default analysis grid, EPSG:31370,
 derived browser views and are never authoritative. No raster binary is stored
 in PostgreSQL and no DHMV file is treated as water depth or volume.
 
+`provision_regional_dhmv.py` creates no separate evidence hierarchy and no
+monolithic regional raster. Each municipality/product result remains one
+ordinary Area-linked raster Dataset plus DatasetVersion. The retained
+provenance already includes every bounded WCS tile URL and aggregate response,
+coverage and normalized-output checksum. A repeat operator run resolves the
+same request identity and reuses the immutable file.
+
 VMM flood-hazard scenario outputs follow the same raster Dataset policy. The
 bounded acquisition service stores one normalized, compressed, Area-clipped
 GeoTIFF per scenario/request identity. `provision_regional_flood_hazards.py`

docs/TODO.md

@@ -35,6 +35,8 @@
 - [x] Execute the governed thematic-raster operator for every persisted Kempen municipality after the Mol live gate passes.
 - [x] Persist one bounded whole-region snapshot per thematic raster so drawn selections can cross municipality boundaries without changing source semantics.
 - [x] Generalize the DOV soil-map operator to all 28 approved Kempen municipality partitions with one regional snapshot manifest.
+- [x] Add a resumable regional DHMV DTM/DSM operator for all 28 approved Kempen municipality Areas.
+- [ ] Execute and audit the complete 336-product VMM and 56-product DHMV regional runtime matrices.
 
 ## Governed source expansion backlog