Files
geointel/docs/BUILD_STATUS.md
T
Codex 70c5e34ecf
GeoIntel release gates / Compile, test, contracts and builds (push) Canceled after 0s
GeoIntel release gates / Python and npm vulnerability policy (push) Canceled after 0s
GeoIntel release gates / GIS image, SBOM and container scan (push) Canceled after 0s
Add governed SPW bathymetry analysis
2026-07-19 04:07:01 +02:00

74 lines
3.2 KiB
Markdown

# GeoIntel Build Status
Updated: 2026-07-19
## Current state
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.
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.
## Release status
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.
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.
## Operational product loop
- 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.
## Explicit non-blocking boundaries
- 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.
## 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 \
--output storage/release-evidence/rc-current/baseline.json \
--release-id rc-belgium-north-sea \
--live-base-url http://192.168.10.150:1202
```