Update Gemstone

AI-estimated geographic origin with confidence

AI-estimated clarity grade from photos

AI-estimated treatment status with species-aware defaults

AI-estimated physical dimensions from image proportions

Structured carat weight estimate from range.

Two producers write this column and they do NOT use the same key names (LNK-CARATRANGE, 2026-08-21). The legacy quick-scan path emits {low, high, best, confidence}; scan_v2 emits {length_mm, width_mm, depth_mm, best, range_min, range_max}. Because pydantic ignores unknown keys, every scan_v2 row deserialized here lost its range entirely and shipped low=0/high=0 — 100% of the last 500 scans audited 2026-08-21. best survived only because the key name happens to match.

Both spellings are now carried and kept in sync by normalize_carat_estimate, so GET /gems/{id}/details returns the same range the inline scan response did. confidence stays 0 when the producer did not emit one — scan_v2 has no carat confidence and inventing one would be worse than admitting we lack it.

Primary gemstone color profile

Jewelry mounting and design specifications

Educational content about the gemstone

Market-level insights

Additive market-drift block on saved-gem responses (LNK-DRIFT).

current_value = scan-time anchor (estimated_value.best) × variety index drift since the scan date. The whole block is null when the gem's variety isn't tracked by the price index; inside the block each field is independently nullable (current_value is null when the gem has no anchor). index_confidence: "high" | "medium" | "low".

Additive per-gem "investment" block (LNK-MKT2). The whole block is null when the user never set a purchase price. unrealized_gain_usd is null when the gem has no usable est value; unrealized_gain_pct additionally when the purchase price is 0.

Additive per-gem "records" block — facts the OWNER stated about their own piece. Null block when they have recorded nothing. Deliberately separate from the *_estimate fields: these are never AI output and a rescan never overwrites them.

The piece title is not part of this block — PUT /gems/{id} (LNK-GEMRENAME) owns renaming and writes main_heading.

Additive per-gem "identification" block (LNK-IDFIX). Null unless the owner has overruled the scan's species, so a client that does not know this block sees exactly what it sees today.

ai_species / ai_estimated_value are what WE said before the correction, kept so the app can show the owner what they changed and so a correction never erases the evidence of the miss.