fix(results): gate operational AI exports on QA
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 11:31:51 +02:00
parent b76cd1837b
commit 0209167cfd
10 changed files with 313 additions and 8 deletions
+26
View File
@@ -12472,3 +12472,29 @@ Open:
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.
## 2026-08-09 - Detection result trust and operational export gate
### Changed
- Detection GeoJSON is now explicitly a review/control layer by default. The
collection, every feature and the persisted Export metadata carry a stable
result-trust classification; AI confidence is never represented as truth.
- Added an explicit `operational` export intent that fails closed unless a
persisted authoritative building-reference QA proves exact tile coverage,
compatible time, supported geometry, zero warnings, zero false positives
and zero false negatives.
- Updated the Downloads copy so users no longer see an unqualified
"Gebouwdetecties" export label.
### Verified
- Focused export and detection-QA suite: 24 passed.
- Scoped Ruff check: passed.
- Frontend TypeScript check: passed.
### Remaining limitations
- The active model remains review-required and Kempen-scoped. The export gate
prevents overstated results; it does not replace the missing independent,
human-reviewed national accuracy corpus or improve model weights by itself.