Your daily import can embed years of history again while your evaluation gets suspiciously easy. The culprit can be sitting inside rateTrend , wearing yesterday's observations as today's dataset row.

Lab note 072: can we keep mortgage-history retrieval incremental without sending the same observations through the embedding queue again?

The catch comes early: an observation date doesn't tell us when a revised value became available. Removing duplicate history helps, but it doesn't automatically make an evaluation prospective.

The row is a shipping container

A dataset row containing historical observations is an export unit, not a reliable retrieval identity.

Our mortgage-rate Actor makes the distinction concrete. A 4,000-day daily history request returns 4,001 points beginning on 2015-11-08; monthly history returns 132 points beginning on 2015-11-01.

Scheduled windows can therefore overlap extensively. Giving each import a fresh document ID preserves that overlap beautifully.…