feat(corpus): require retrievable visual review evidence

This commit is contained in:
AzuTear
2026-07-11 16:13:02 +02:00
parent 8b9f948c6b
commit 3e2ab61c97
14 changed files with 325 additions and 73 deletions
+16 -8
View File
@@ -282,7 +282,10 @@ confirmation probes. That is not an elevated packaged-executable claim. The
current elevated development 50-artifact native smoke now passes with complete
timing evidence and zero writes; its `28,022 ms` end-to-end result does not
prove the separate 3/s target. The remaining Review corpus continues to grow
only from visually confirmed labels.
only from visually confirmed labels. The review exporter now prioritizes
retrievable retained crops and serializes only safe capture/run references; its
confirmation preparer refuses OCR-only candidates so parser guesses cannot be
promoted without visual evidence.
## Product Direction
@@ -531,18 +534,23 @@ Status:
reconciliation, zero Review/errors/writes, and
`requestToResultsReconciledMs=28,022`. This is a functional/safety gate;
it does not claim 3 Artifacts/s.
4. Clean generated workspace output, commit the coherent checkpoint, and push
the intended branch. A package-runtime/UAC test is required only for that
separate claim.
5. Continue review-corpus growth only from visually confirmed crops. Keep
4. Completed on 2026-07-11: generated workspace output was cleaned and the
coherent checkpoint was committed and pushed as `8b9f948`. A
package-runtime/UAC test is required only for that separate claim.
5. The visual-evidence review exporter/preparer passed focused checks plus
`npm run lint`, `npm test` (72 files / 446 tests), and `npm run build`.
Its read-only export of the current 177-record local queue found three
retrievable crops, all already-confirmed `native-review-approved` cases;
no new corpus label was promoted.
6. Continue review-corpus growth only from new visually confirmed crops. Keep
explicit 14★ evidence excluded, ambiguous evidence in `Review`, and reject
aliases that cannot be justified by independent field evidence.
6. Refresh source-bound profiles before expiry and add Golden plus
7. Refresh source-bound profiles before expiry and add Golden plus
Review/low-confidence adversarial fixtures for each additional profile.
7. Keep the bounded wheel reset as the production baseline. Benchmark a `B`
8. Keep the bounded wheel reset as the production baseline. Benchmark a `B`
plus Artifact-tab reopen only as a separate guarded experiment before any
reset strategy change.
8. Keep Build-Fit profile suggestions read-only and Artifact-only until an
9. Keep Build-Fit profile suggestions read-only and Artifact-only until an
explicit product decision adds owned-character, weapon, team, and rotation
inputs with their own sources.