feat: add cross-domain Mol data profile

2026-07-16 03:06:36 +02:00
parent 4aa0d6da24
commit 035ec3b233
39 changed files with 3049 additions and 22 deletions
@@ -205,6 +205,29 @@ The smoke never passes `--apply`. It fails if the cleanup summary is not a
 dry-run, if any export/file deletion is reported, or if the dry-run candidate
 fields are missing.

+## Governed cross-domain raster and soil evidence
+
+MercatorNet thematic products use the ordinary raster Dataset and immutable
+DatasetVersion paths under `STORAGE_ROOT`. `source_metadata` records product,
+coverage, native resolution/unit, render range, reference year and request
+bounds. `provenance_metadata` records every tiled WCS URL, transfer checksum,
+normalized checksum, exact Area id and validation result. No new storage table
+or provider-side path is introduced.
+
+The DOV Mol soil operator retains evidence under:
+
+```text
+storage/operator-evidence/dov-soil-map/mol/
+  raw/dov_soil_map_page_*.json
+  dov_soil_map_mol.geojson
+  dov_soil_map_mol.manifest.json
+```
+
+Only the normalized, exactly clipped GeoJSON enters DatasetService and
+`vector_features`. The manifest binds the persisted artifact, Mol boundary,
+source page URLs/checksums, feature completeness, class-area summaries and
+historical limitations. Raw source responses remain operator evidence.
+
 ## Model storage

 Model artifacts live under: