Separate stable result keys from changeable display labels — what should the operator record?
A title or handle can change while a returned source identifier stays the same. Conversely, two unrelated items can share a display label. Store labels as observations attached to a key, not as the key itself, and review any apparent rename using authorized original references before updating a current table.
Keep renamed titles and handles from becoming accidental new records or false merges.
Use source_key, label_value and label_observed_at instead of placing a handle directly into the primary join column. Keeping label_observed_at avoids describing an old label as the current one when the table is reopened long after its original authorized response was received.
Change the current display label only in a new table revision while preserving the stable identity contract and applicable retention boundaries. A current-label update should not reorder frozen selection ranks or rewrite the exact wording of a quotation that was legitimately recorded under a different permitted observation.Split the fields
Use source_key, label_value and label_observed_at instead of placing a handle directly into the primary join column. Keeping label_observed_at avoids describing an old label as the current one when the table is reopened long after its original authorized response was received.
Keep observed label history
Append a later label observation when permitted, preserving its receipt reference without asserting the exact time of the publisher's rename. Where retention permits only the current label, preserve a nonidentifying revision reference instead of maintaining an unnecessary public history of prior handles or names.
Test duplicate labels
Use two fixture records with the same title but different qualified keys; confirm grouping by label does not merge their evidence. Also test one stable key with two successive label observations; the table should represent one object with changed descriptive data, not two unrelated evidence records.
Review rename assumptions
Require identity continuity through actual returned keys or inspectable references, marking uncertain associations unresolved rather than asserting a renamed account. If the key itself changes, investigate the source's documented semantics or explicit evidence rather than using a familiar title to assert continuity across identities.
Update presentation safely
Change the current display label only in a new table revision while preserving the stable identity contract and applicable retention boundaries. A current-label update should not reorder frozen selection ranks or rewrite the exact wording of a quotation that was legitimately recorded under a different permitted observation.
Keep the boundaries clear.
- Keep renamed titles and handles from becoming accidental new records or false merges.
- Operational record: Split the fields. Context badges do not certify access.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.