Skip to main content
Localization, under Documents in the sidebar, manages market variants of approved work — by language, region, jurisdiction, or market — and checks that each still carries what it is obliged to. Before any variant exists, the page explains the three steps (name the variant and paste its text, record what it must carry, run the check) and offers Create a variant. Counts of variants, locales, blocking results, and unchecked variants appear once there is something to count. A variant may change wording, structure, examples, length, and tone. It may not lose an approved claim or a required disclosure. That check is the reason this surface exists rather than translation happening off to the side.

Required items

Each variant records the claims and disclosures that must survive into it. An item can be typed in directly or attached from a verified claim.
An item’s text is copied in when it is attached, not resolved live from the claim registry. The obligation is fixed by what was approved for the source at the time — a claim later reworded upstream must not silently change what an already-reviewed variant was checked against.

The parity check

Parity is three-valued per item, and the middle value is the point: A text-presence test cannot verify a translation. A French variant will not contain the English claim string, and reporting that as “claim missing” would make the check noise reviewers learn to click past. Reporting it as present because the check was skipped would be far worse — a compliance surface returning green on documents it never examined. So unverifiable blocks nothing on its own and passes nothing either. It is a coverage gap, and it is settled by attestation: a named person, recorded with a timestamp, vouching that the item survived. An unknown locale on either side is treated as a different language, because assuming a match would produce preserved verdicts from a comparison nobody established was valid.

Figures

Numeric parity runs even across languages. Digits usually survive translation, and a figure that changed or vanished between a source and its variant is the highest-consequence localization defect there is. Separators are normalized, so 4.25% and 4,25 % compare equal — a variant that localized its decimal separator does not read as having changed the number. A required item that is outright missing, or a required figure that vanished, marks the variant blocking.

A report never describes text it was not computed from

Editing the variant’s text or either locale, and attaching or removing a required item, recompute the parity report in the same save. Leaving a green result attached to text it was not computed from is exactly the false assurance this feature exists to prevent, and a report that only exists when someone remembers to press Check blocks approvals that were never actually at risk. You can still run the check on demand at any time. A variant that has never been checked or saved is counted as unchecked, not as passing. Editing the text also withdraws every attestation on the variant, so approving or publishing in the same request as an edit is refused: the recomputed report has not been read, and the cross-language items it covers are no longer vouched for by anyone.

Verified Claims

The registry a variant’s required claims are attached from.

Policies

Rules that decide which disclosures a market needs.
Last modified on September 24, 2026