Recover governed runtime provenance for legacy YOLO models
GeoIntel release gates / Compile, test, contracts and builds (push) Failing after 20s
GeoIntel release gates / Python and npm vulnerability policy (push) Failing after 22s
GeoIntel release gates / GIS image, SBOM and container scan (push) Failing after 2m31s

This commit is contained in:
Jens
2026-08-23 23:22:02 +02:00
parent 300fbba5c9
commit be2e092b33
8 changed files with 588 additions and 0 deletions
+12
View File
@@ -12935,3 +12935,15 @@ Open:
- Physical touch-device and screen-reader certification remain human QA. No
commit or deployment was performed because the active execution brief
explicitly forbids committing unless requested.
# 2026-08-23 — Active YOLO runtime provenance remediation
- Recovered the original Sprint 174 model run from persistent Tower storage.
- Confirmed that the active model and retained `best.pt` are byte-identical at
SHA-256 `a9088b8491dfae36694b53e9e9406cb4e3511d334a5712fa34f75078a47759c1`.
- Verified the surviving base-model, training-argument, results, training-summary,
dataset-YAML and dataset-summary checksums before allowing registration.
- Added a dry-run-first, atomic and idempotent runtime provenance migration that
binds exact model bytes to a governed Postgres source snapshot.
- Kept the historical evidence boundary explicit: this runtime receipt does not
invent human review, a historical training commit/container, protected-test
independence, national validity or a new promotion decision.