feat: add cross-domain Mol data profile

scripts/README.md

@@ -1613,6 +1613,33 @@ take a long time because every VMM WCS tile is bounded, rate-limited and
 validated. This is expected operator work; the app never fetches these rasters
 on page load or map click.
 
+## Cross-domain Mol profile
+
+Load the five official policy rasters for the exact Mol municipality Area and
+immediately verify each persisted selection result:
+
+```bash
+docker exec geointel python /app/scripts/provision_thematic_rasters.py
+```
+
+Plan the later complete Kempen rollout without source fetches or writes:
+
+```bash
+docker exec geointel python /app/scripts/provision_thematic_rasters.py \
+  --project-name "Kempen Regional Workbench" --all-municipalities --dry-run
+```
+
+Load the official DOV soil map for Mol:
+
+```bash
+docker exec geointel python /app/scripts/provision_mol_soil_map.py
+```
+
+`--fetch-only` builds the soil artifact and manifest without API import;
+`--force` is the only way to bypass an existing ready soil Dataset. Both
+operators use canonical APIs and persistent operator-evidence storage. They do
+not run on application startup.
+
 ## Tower deployment
 
 Push the local branch to Gitea, then rebuild the Unraid/Tower Docker runtime: