Make Mol the primary operating context

docs/CODEX_EXECUTION_LOG.md

@@ -7233,4 +7233,28 @@ Open:
 
 ## Next recommended pass
 
-- Re-export the seven-AOI evidence portfolio from the deployed backend, render the Turnhout/Herentals/Geel sheets and inspect the real orthophoto evidence. Keep all CSV decisions `unreviewed` until an operator makes an explicit visual classification; do not start another model training run yet.
+- Re-export the seven-AOI evidence portfolio from the deployed backend, render the Mol/Geel/Turnhout sheets and inspect the real orthophoto evidence. Keep all CSV decisions `unreviewed` until an operator makes an explicit visual classification; do not start another model training run yet.
+
+# Sprint 177 - Mol-first operating context
+
+## Product and workbench focus
+
+- Declared Mol as the primary operational context while preserving the broader Kempen for cross-area validation and regional interoperability.
+- Centralized Mol coordinates, default region and a compact 1 km EPSG:4326 MultiPolygon AOI in the frontend focus configuration.
+- Initial project discovery now recognizes Mol from project metadata or persisted dataset provenance and inspects those candidates first.
+- Explicitly selected and newly created projects still take precedence, so the focus rule does not fight operator intent.
+- The empty MapLibre workbench starts over Mol; loaded AOIs and data continue to determine map bounds normally.
+
+## Operator provenance
+
+- Moved Mol to the first position in default real-data sample preparation without dropping any existing Kempen sample.
+- Multi-sample quality runs now forward their AOI slug, and future persisted matrix project names retain that origin instead of appearing as anonymous model/tile runs.
+- No provider fetch, AI output, QA metric, migration, API contract or model configuration was changed.
+
+## Validation
+
+- Focused Mol-primary regression coverage: `3 passed`.
+- `bash scripts/run_readiness_check.sh`: passed with `481` backend tests, API-contract audit, single Alembic head, frontend typecheck and production build.
+- Frontend production bundles: app `217.69 kB`, React vendor `140.74 kB`, MapLibre `801.82 kB` before gzip.
+- `python -m alembic upgrade head --sql`: complete migration chain rendered through single head `202606120900`.
+- Both changed matrix scripts pass `bash -n`; no migration file changed.

docs/PRODUCT_VISION.md

@@ -32,11 +32,13 @@ GeoIntel moet bewijzen dat de ontwikkelaar de volledige keten begrijpt:
 
 De Kempen vormen de afgebakende regio. Dit maakt het project concreet, realistisch en demo-baar. Voorbeelden:
 
-- gebouwdetectie in Geel
-- infrastructuurdruk rond Mol
+- gebouwdetectie en infrastructuuranalyse in Mol
+- vergelijkende validatie in Geel
 - verstedelijking rond Turnhout
 - natuurfragmentatie rond Kasterlee of Retie
 
+Mol is de primaire operationele focus. De standaardkaart, nieuwe AOI-context en operator-volgorde vertrekken daarom vanuit Mol. De bredere Kempen blijft bewust onderdeel van de productscope voor onafhankelijke validatie, overdraagbaarheid en regionale vergelijking.
+
 ## Richting
 
 De definitieve richting is:

docs/TODO.md

@@ -18,6 +18,7 @@ This file now starts with the current implementation status. Older preparation/b
 
 ## Current implementation status
 
+- [x] Make Mol the primary workbench, AOI and operator-sample context while preserving broader Kempen coverage.
 - [x] Backend FastAPI foundation, health endpoint and service structure.
 - [x] React/TypeScript frontend foundation and MapLibre workbench.
 - [x] Map layer visibility, opacity and feature property inspection.