Read against 0.10.1.
Problem
The provenance fingerprint is built from translatable text only — leafSourceText, which collects
localized text / textarea / richText fields that are not excluded. Everything else in the
document is merge-only and never contributes.
So a source change that is not text never marks its translations out of sync. Swap the hero image on
the English version of a page and every translated locale keeps showing the old image, with the
staleness signal saying everything is current. Same for attachments, and for any field a host has
marked exclude: true.
Why this matters
Localized uploads are common — ours include a required localized promoImage on the Hero block. These
are exactly the fields a human has to handle, because a model cannot translate an image, so they are
the ones most in need of a "the source moved, look at this again" signal.
We currently catch it with a review-time same-as-source comparison, which works but only fires when
someone happens to run another translation. Between runs, the staleness signal is quietly wrong.
Suggested shape
An option to include non-text localized fields in the fingerprint — uploads and relationships by id,
excluded fields by value. Opt-in would be fine; it changes what counts as a source change, so it should
not shift under existing installs silently.
Read against 0.10.1.
Problem
The provenance fingerprint is built from translatable text only —
leafSourceText, which collectslocalized
text/textarea/richTextfields that are not excluded. Everything else in thedocument is merge-only and never contributes.
So a source change that is not text never marks its translations out of sync. Swap the hero image on
the English version of a page and every translated locale keeps showing the old image, with the
staleness signal saying everything is current. Same for attachments, and for any field a host has
marked
exclude: true.Why this matters
Localized uploads are common — ours include a required localized
promoImageon the Hero block. Theseare exactly the fields a human has to handle, because a model cannot translate an image, so they are
the ones most in need of a "the source moved, look at this again" signal.
We currently catch it with a review-time same-as-source comparison, which works but only fires when
someone happens to run another translation. Between runs, the staleness signal is quietly wrong.
Suggested shape
An option to include non-text localized fields in the fingerprint — uploads and relationships by id,
excluded fields by value. Opt-in would be fine; it changes what counts as a source change, so it should
not shift under existing installs silently.