fix(ai): bind model scope to immutable geometry
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 10:54:52 +02:00
parent f41392a415
commit b76cd1837b
19 changed files with 431 additions and 58 deletions
+28
View File
@@ -12444,3 +12444,31 @@ Open:
`not_evaluable` without governed evidence. Phase 4 remains **in progress**,
Phase 5 remains **not ready**, and promotion/training feedback from protected
data is not authorized.
## 2026-08-09 - Model accuracy boundary and truthful evidence labels
### Changed
- Replaced the configured-YOLO Area-name substring gate with a fail-closed,
checksum-bound validation-scope manifest. The exact model SHA-256 must match
and the immutable EPSG:4326 scope geometry must cover the complete persisted
Dataset AOI. Renaming an Area can no longer widen model applicability.
- Added an operator tool that builds the model-bound manifest from exact model
bytes and governed scope GeoJSON without overwriting prior evidence.
- Corrected the detection UI: legacy Mol/Kempen profile scores are now labelled
historical calibration context, spatial independence is explicitly unproven,
and no profile is marked approved or promotion-ready.
### Verified
- Targeted backend/UI contract selection: 34 passed.
- `git diff --check`: passed before the documentation update; final check is
part of the handoff verification.
### Remaining limitations
- The current active model is still not nationally validated. A new governed
corpus, independent spatial split, representative human review and immutable
product benchmark remain required before any production-accuracy claim.
- Every deployed model asset needs its own generated scope manifest and exact
configured manifest checksum before enforced inference is available.