product-recognition-demo/recognization/docs
kiyo9w 7736465bee docs(decision): correct the record against the re-measured evidence
The audit's own numbers were right; several claims built on them were not, and
the advisors found each one:

- 'wins both axes at both resolutions' - false at live, where the lane trades
  59% coverage for 93% precision against Van's 66% at 39%. Stated as the trade
  it is.
- G1's bootstrap now exists: the local lane's correct set is a strict superset
  of Van's on the stream, so the 95% lower bound is a hard +0.0 pp - a floor of
  that pairing, not a margin. tracks_final.json is level with Van and does not
  clear it.
- The far-unknown rate is 0.066% on 4580 crops at the shipped configuration,
  not 0.30% on 2650 at the old one.
- The E-3 ablation compared text-presence *and* a different argmax; both arms
  now go through the same DecisionPolicy ordering. Text adds 9-10 pp of
  coverage at full resolution while raising precision.
- The sweep table swept one axis while pinning the other; replaced with the
  joint sweep.
- The two Re-measured tables are dated snapshots, labeled as such.
2026-09-29 09:28:19 +09:00
..
research/2026-09-28-recognition-architecture docs(decision): correct the record against the re-measured evidence 2026-09-29 09:28:19 +09:00
API.md fix(catalog): re-source sku_l09 and enforce the pyramid floor 2026-09-29 09:28:16 +09:00
DATA.md docs: require explicit backend for legacy walks 2026-09-28 14:42:12 +09:00
design-price-tags-and-compliance.md docs: design for price-tag OCR, reconciliation, compliance, and mobile scan 2026-09-24 13:45:54 +09:00
EXTERNAL-EVAL.md feat: a store's fine-tuned head, and the two-stage gate it needs 2026-09-25 03:21:22 +09:00