block checkpoint evaluation on ancestral exposure
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:10:50 +02:00
parent fd45f37a38
commit 116b8e291e
8 changed files with 390 additions and 61 deletions
@@ -237,3 +237,29 @@ mode, fails before PyTorch import, model loading or GPU inference when any
evaluation AOI overlaps any supplied train split. The reproduced gate blocked
on `postel_bos` for both checkpoints. Its immutable machine-readable record is
`artifacts/evidence/accuracy/model-training/20260809-v70-evaluation-independence-gate.json`.
## Full model-lineage correction
The preceding correction still considered only the final fine-tune corpus of
each checkpoint. Exact retained Ultralytics arguments establish a longer
ancestry: the active checkpoint was initialized from
`geointel-building-yolov8s-aoi1024expandedminpx4vis035e50`, which was initialized
from the generic `yolov8s.pt`; the challenger was then initialized from the
active checkpoint. The copied model assets and retained `best.pt` files match
byte-for-byte at each building-model stage.
The ancestral expanded corpus exposes all three evaluation AOIs: `postel_bos`
as train, and `turnhout` plus `westerlo` as validation. Therefore none of the
v69 AOIs is independent of the complete model family. Turnhout/Westerlo can
still be used as familiar regression diagnostics, but their metrics are not a
fresh candidate-ranking result and must not support accuracy, uncertainty,
generalisation or release claims.
The gate now requires every ancestral corpus summary and checks every recorded
split, including validation and calibration. A reproduced Tower run blocked on
all three AOIs before PyTorch import, model loading or GPU inference. Evidence:
`artifacts/evidence/accuracy/model-training/20260809-v71-full-lineage-independence-gate.json`.
The byte-matching parent/output chain is retained separately in
`artifacts/evidence/accuracy/model-training/20260809-v71-model-lineage-receipt.json`.
Fresh geographically separated AOIs with complete spatial and lineage checks
are required for the next meaningful evaluation.