# Morada Produce / UNITEC — sizing guidance for HUD + dataset

**Project:** AR Cherry Glasses / FIELD lane  
**Pack house:** Morada Produce — Linden, CA (Handel cherries)  
**Line:** **UNITEC Cherry Vision** (not TOMRA)  
**Date:** 2026-09-05  
**Status:** **PROVISIONAL** reference only — Morada current row cards are **unconfirmed**; not operational ground truth and **not** a Phase A production READY gate  
**Upstream jobs:** `af338b72` (Morada/UNITEC confirm), `5786251d` (industry row table), `4bc6bbc0` (PMF / incentives / sizing review)

---

## What this locks vs what stays open

| Fact | Guidance |
| --- | --- |
| Where Handel fruit packs | **Morada Produce**, Linden, CA |
| Optical line | **UNITEC Cherry Vision** (public install + ongoing optical sort; red + Rainier capable) — **not** Prima Frutta / TOMRA |
| Shared language with the shed | Industry **row-count** diameters (64ths table), not a vendor pixel score |
| Current Morada row cards / buyer programs | **Unconfirmed** — pending James |
| Sensor diameter vs caliper | **Not validated** — required before any operational size cue |

TOMRA/Compac remains common at other local sheds (e.g. Prima Frutta Linden). Do **not** use TOMRA thresholds for Handel → Morada fruit.

---

## Provisional pack-grade reference (not a production gate)

Industry row table used only as a **shared vocabulary** with the shed. The **~10-row / ~26.6 mm** figure is a **provisional pack-grade anchor** for discussion and dataset fields — **not** an accepted Phase A production READY threshold.

| Row | Min diameter | ≈ mm |
| --- | --- | --- |
| 9 | 75/64″ | 29.8 |
| 10 | 67/64″ | **26.6** ← provisional pack-grade reference only |
| 11 | 61/64″ | 24.2 |
| 12 | 54/64″ | 21.4 |

Lower row # = larger fruit. Marked lots typically need ~90–95% at/above the labeled row (jurisdiction/grade dependent).

**Do not** silently add a 26.6 mm production READY gate to Phase A scope. Operational use of any size threshold requires **both**:

1. James confirms **current** Morada row cards / buyer programs for the season, and  
2. Sensor (or LiDAR/depth) diameter vs **caliper** validation on orchard fruit.

Until then, size remains measurement / logging only.

---

## Keep maturity separate from size / market grade

These are **different signals**. Do not collapse them into one training label.

| Signal | What it means | Typical source |
| --- | --- | --- |
| **Maturity / ripeness** | Color vs variety pick standard (and optional Brix subset) | Color card, crew standard |
| **Size / pack grade** | Diameter vs buyer / row card | Caliper now; depth/size model later |
| **Defects** | Damage, doubles, etc. | Visual / line rules — out of Phase A ML clone |

Practical mapping (orchard, before the line) — **provisional cue guidance**:

| HUD cue | Maturity (primary) | Size / grade (secondary, only if measured + validated) |
| --- | --- | --- |
| **READY** | Color meets variety/block pick standard | Optional later filter — **not** Phase A production gate |
| **WAIT** | Color immature for this pick pass | **Do not** auto-WAIT from undersize alone when color is good |
| **MAYBE** | Borderline color, occlusion, glare, low confidence | Borderline size or missing size confidence — human judgment |

**Important for Dataset v0 / training:** good color + undersize must **not** automatically become an immature / WAIT label. That mixes maturity with market grade. Record both fields; let product policy decide later.

Conservative READY still prefers false WAIT/MAYBE over false READY for **color** (see `/docs/phone-mvp-spec`).

---

## Dataset / label notes — preserve caliper independently

- Tag pack-house alignment: `Morada` + `UNITEC Cherry Vision`.  
- When calipering (Dataset v0 / QC): always store **`diameter_mm`** (measured) as its own field.  
- Optionally map mm → provisional row (9≈29.8, 10≈26.6, 11≈24.2, 12≈21.4) in a **separate** derived field — never overwrite caliper with a threshold decision.  
- Store **color / ripeness label**, **provisional row mapping**, and **buyer/season grade criterion** as distinct columns/metadata.  
- Color labels remain the main Phase A training signal; size is a secondary measurement head, not a fused READY rule yet.

---

## Acceptance conditions before operational size use

| Condition | Owner | Status |
| --- | --- | --- |
| Confirm current Morada row cards / buyer programs | James | Open |
| Sensor- or depth-estimated diameter vs caliper study | FIELD / Grok + dataset | Open |
| Explicit product policy: whether size can slow a READY color cue | James + team | Open (see job `4bc6bbc0`) |

LiDAR / depth sizing is a **separate measurement experiment**, not a dependency for Phase A color MVP.

---

## Related public docs

| Doc | URL |
| --- | --- |
| This page | `/docs/morada-sizing` |
| Phone MVP spec | `/docs/phone-mvp-spec` |
| Field brief | `/docs/field-brief` |
| Label protocol | `/docs/label-protocol` |
| Industry research memo (workspace) | `/workspace/multi-ai-hub/cherry-sizer-grading-memo.md` |