feat: add temporal Mol explorer

backend/README.md

@@ -935,6 +935,36 @@ the same bbox-selected FeatureCollection as a normal export record with
 `export_type="vector_selection_geojson"`. This creates a handoff artifact only;
 it does not create a derived dataset.
 
+## Temporal Mol data and evolution
+
+Dataset uploads accept `temporal_series_key`, `observed_at`, `valid_from`,
+`valid_to`, `temporal_granularity` and `source_version`. Every new source or
+derived dataset also writes dataset version 1 in the same transaction.
+
+After the Mol municipality workspace is available, import the official source
+snapshots explicitly:
+
+```bash
+docker exec geointel python /app/scripts/provision_mol_population_history.py
+docker exec geointel python /app/scripts/provision_mol_historical_landuse.py
+```
+
+The first command imports Statbel sector population for 2021-2025. The second
+imports Digitaal Vlaanderen historical land use for 1778, 1873 and 1969. Both
+are idempotent, use the normal API/DatasetService flow and retain fetched
+artifacts in persistent operator storage. They never run on app startup.
+
+Historical land-use work can be bounded explicitly:
+
+```bash
+docker exec geointel python /app/scripts/provision_mol_historical_landuse.py --years 1778 1969 --themes forest water
+```
+
+`GET /api/v1/projects/{project_id}/temporal/series` discovers the series and
+`POST /api/v1/projects/{project_id}/temporal/compare` compares two snapshots
+inside one EPSG:4326 bbox. Partial statistical sectors are estimates; old map
+editions without stable identities do not produce invented object changes.
+
 ## Helpful repository scripts
 
 - `bash scripts/backend_install.sh`