record explicit AI-assisted AOI review ledger
This commit is contained in:
@@ -12528,3 +12528,24 @@ Open:
|
||||
representative human review, freeze a new independent corpus and only then
|
||||
train a pre-registered GPU candidate with provenance captured from process
|
||||
start. The legacy checkpoint cannot be made compliant retroactively.
|
||||
|
||||
## 2026-08-09 - Explicit AI-assisted reviewedexp6 AOI ledger
|
||||
|
||||
### Reviewed
|
||||
|
||||
- Inspected the existing checksum-bound 64-tile contact sheet at original
|
||||
resolution. It covers 28 AOIs, 21,611 rendered labels, dense urban, sparse
|
||||
building context and pure-background examples.
|
||||
- Recorded a per-AOI machine-readable decision ledger with reviewer type
|
||||
`ai_assistant`, `human=false`, the contact-sheet hash, sampled tile/label
|
||||
counts, split roles and explicit roof-versus-GRB limitations.
|
||||
- Classified 26 represented training AOIs as experimental-training eligible;
|
||||
kept Grobbendonk and Vosselaar validation-only. No AOI was represented as
|
||||
human accepted or production release eligible.
|
||||
|
||||
### Gate behavior
|
||||
|
||||
- Confirmed that the governed training wrapper still requires accepted human
|
||||
review and therefore does not accept this AI ledger as release evidence.
|
||||
- Did not add an override, fixture claim or synthetic reviewer identity. No
|
||||
model training, activation or production redeploy followed from this review.
|
||||
|
||||
Reference in New Issue
Block a user