evaluate models on fresh regional calibration AOIs
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

This commit is contained in:
Jens
2026-08-09 22:36:27 +02:00
parent 116b8e291e
commit b068a5e065
28 changed files with 5053 additions and 18 deletions
+11
View File
@@ -1185,3 +1185,14 @@ This file now starts with the current implementation status. Older preparation/b
- [ ] Convert the AI-assisted ledger into no stronger claim than experimental
triage; a real human must independently review and sign the frozen artifacts
before the governed training wrapper may unlock.
- [x] Provision and visually inspect six fresh non-protected calibration AOIs
across Vlaanderen, Wallonië and Brussel; prove all are at least 2 km from all
31 resolved ancestral AOIs and absent from every ancestral split.
- [x] Reject overlapping edge-cover tiles in diagnostic evaluation; retain 24
canonical 512 px cells and record all 30 excluded overlapping views.
- [x] Run active/challenger GPU calibration on the fresh portfolio and retain
aggregate, regional and per-AOI metrics without promoting either model.
- [ ] Provision a separately frozen train-only failure corpus after human
review. Do not copy V72 calibration tiles or use their labels for fitting.
- [ ] Finalise version-specific PICC/UrbIS semantic harmonisation contracts
before treating Walloon/Brussels metrics as release-grade ground truth.