Add governed SPW bathymetry analysis

docs/BUILD_STATUS.md

@@ -1,53 +1,69 @@
 # GeoIntel Build Status
 
-Updated: 2026-07-17
+Updated: 2026-07-19
 
 ## Current state
 
-GeoIntel is an implemented map-first GeoAI workbench running as an all-in-one
-Unraid container with embedded PostGIS, FastAPI, React/MapLibre, local
-Ollama integration and optional local YOLO/PyTorch inference.
+GeoIntel `v1.0.0-rc.1` is an accepted map-first GeoAI workbench for Belgium
+and the legally distinct Belgian maritime scopes. It runs as an immutable
+all-in-one Unraid image with PostGIS, FastAPI, React/MapLibre, local Ollama
+integration and optional local YOLO/PyTorch inference.
 
-The active release program is
-`docs/RC_ROADMAP_BELGIUM_NORTH_SEA.md`.
+Mol and the Kempen are deep regression areas, not the product boundary. The
+national workbench also has deterministic golden journeys for Wallonia,
+Brussels, a language-boundary selection, the coast and the Belgian North Sea.
 
-## Product scope
+## Release status
 
-- Target: all Belgian land and the separately labelled Belgian territorial
-  sea, EEZ and continental shelf.
-- Existing deep regression references: Mol and the Kempen transport region.
-- Required new golden areas: Wallonia, Brussels, a cross-region area, coast
-  and Belgian North Sea.
-- Architecture: federated authoritative providers with one coverage matrix;
-  no assumption that GRB, PICC, UrbIS and NGI are semantically identical.
+There are no open release blockers for the signed `v1.0.0-rc.1` evidence set.
+RC-0 through RC-11 are complete. Backup/restore, fresh install, upgrade,
+rollback, fail-closed readiness, one Alembic head, API contracts, supply-chain
+policy, responsive browser journeys and live PostGIS acceptance are proven.
 
-## Implemented foundation
+The active post-RC candidate extends real source coverage. Its repository gate
+passes 1,052 backend tests, 22 frontend tests, frontend typecheck/build,
+one Alembic head and the complete readiness script. Its remaining acceptance
+step is live SPW bathymetry persistence and browser verification before a new
+immutable image is called releasable.
 
-- Projects, Areas, Datasets, versions, PostGIS vector features and raster
-  artifacts.
-- Map selection, semantic metrics, historical comparison and exports.
-- Governed Flemish sources for buildings, context, orthophotos, terrain,
-  flooding, soil, nature, agriculture, population and policy rasters.
-- Detection persistence, local configured YOLO/PyTorch path, QA/QC and review
-  evidence.
-- Segmentation persistence foundation without fake production inference.
-- Local Ollama assistant grounded in persisted evidence.
-- Single-container Unraid deployment on port 1202.
+## Operational product loop
 
-## Release blockers
+- Open one national map without selecting a technical project.
+- Select an understandable theme and draw or reuse a bounded Area.
+- Resolve governed coverage per Belgian jurisdiction.
+- Analyse persisted PostGIS vectors or bounded raster artifacts.
+- Show source-appropriate metrics, provenance, time and limitations.
+- Compare compatible Statbel 2021-2025 and other governed historical series.
+- Export persisted evidence or question it through the local Ollama assistant.
+- Run configured local YOLO detection with persisted QA and explicit human
+  review limitations.
 
-- Current production backup and isolated restore proof.
-- Fail-closed readiness and truthful runtime capability reporting.
-- Stale job/run reconciliation and correlated exception logging.
-- Temporal compatibility guard for detection QA.
-- Production secret/configuration parity, immutable images and rollback.
-- Full CI, reproducible dependencies and supply-chain evidence.
-- Critical response-model typing and real frontend/browser E2E coverage.
-- National and maritime scope/providers/golden areas.
+## Explicit non-blocking boundaries
 
-## Latest evidence
+- MDK analytical North Sea bathymetry remains `not_configured`: the public
+  endpoint fails strict hostname validation and the official low-resolution
+  product is currently request-based. TLS and source-integrity checks are not
+  bypassed.
+- SPW supplies governed Walloon waterbed elevation in mDNG, not current water
+  depth. Water volume remains unsupported until a compatible water-surface,
+  time, vertical-datum and uncertainty contract exists.
+- Building detection is an assisted review workflow. The retained benchmark
+  still requires independent false-negative review before any claim of
+  autonomous production accuracy or another training pass.
+- Real SAM/YOLO-seg inference, a training studio, LiDAR, production
+  multi-user authentication and real-time monitoring remain post-V1 scope.
+- Additional official datasets may improve coverage, but they are not V1
+  completion blockers when the coverage matrix reports absence honestly.
 
-Run:
+## Reproduce current repository evidence
+
+```bash
+bash scripts/run_readiness_check.sh
+cd backend && python -m alembic upgrade head --sql
+bash -n scripts/live_migration_smoke.sh
+```
+
+Live release evidence:
 
 ```bash
 python scripts/capture_release_evidence.py \
@@ -55,8 +71,3 @@ python scripts/capture_release_evidence.py \
   --release-id rc-belgium-north-sea \
   --live-base-url http://192.168.10.150:1202
 ```
-
-The evidence manifest is runtime output and is deliberately ignored by Git.
-The first captured baseline reported one Alembic head (`202607160001`) and
-reachable live health/capability routes. Health truthfulness is an open RC-2
-blocker until readiness becomes fail-closed.