Add regional flood hazard provisioning

docs/STORAGE_ARCHITECTURE.md

@@ -118,6 +118,15 @@ 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.
 
+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`
+does not create a parallel storage layout: every municipality/scenario result
+is an ordinary Dataset and DatasetVersion with WCS request hashes, tile request
+URLs, response/coverage/normalized checksums, EPSG:31370 bounds, scenario
+metadata and explicit unsupported-volume flags. Repeat runs reuse matching
+ready Datasets through the acquisition service cache.
+
 BWK/Natura 2000 evidence lives under
 `storage/operator-evidence/bwk-natura2000-2025/mol/`. The `raw/` directory
 contains immutable WFS pages; the adjacent manifest records their URLs,