fix(ai): bind model scope to immutable geometry
This commit is contained in:
@@ -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.
|
||||
|
||||
Reference in New Issue
Block a user