Add governed GRB refresh workflow

2026-07-16 17:59:00 +02:00
parent bbf56d762c
commit eed6ee796e
21 changed files with 1313 additions and 1 deletions
@@ -13,6 +13,13 @@ replaces source data. A separate `Officiële edities controleren` action is the
 only trigger for bounded GRB/orthophoto catalog reads. It presents official and
 local editions, layer-contract coverage and honest non-comparable version
 markers without starting an import or background poll.
+After that explicit check, the same surface shows a compact GRB refresh plan
+for buildings, roads, water and parcels. It states whether each local regional
+snapshot is current, updateable or needs review and shows the current object
+count. The UI cannot start the million-feature import: staging and checksum-
+confirmed application remain an operator action so a browser request cannot
+silently replace regional reference data. Existing snapshots remain visible
+as historical observations.

 The user-facing shell is task based: `Kaart`, `Bronnen`, `Kwaliteit`, `Beeldanalyse`, `Downloads`, `Status` and `Beheer`. Internal benchmark projects, raw dataset metadata, provider capabilities, model registry details and QA evidence remain accessible through labelled advanced disclosures instead of competing with the normal workflow.