correct overlapping checkpoint evaluation
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 20:41:54 +02:00
parent 2de438b9cc
commit 48084799c9
11 changed files with 539 additions and 10 deletions
+7
View File
@@ -1170,6 +1170,13 @@ This file now starts with the current implementation status. Older preparation/b
- [ ] Compare the existing 0.35 edge-visibility policy against a separately
versioned stricter ablation from original source geometry before any new
governed training; do not approximate this by dropping every edge label.
- [x] Replace the overlapping checkpoint ranking with a checksum-bound,
training-disabled non-overlap view: 12 real tiles, 2,384 unique interior
objects, zero repeated interiors and explicit removal of blank Arendonk
no-data imagery.
- [ ] Add multiple independent real-background AOIs and more geographically
separated positive validation AOIs before interpreting non-overlap ranking
as release evidence; Postel alone is not representative.
- [ ] 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.