> ## Documentation Index
> Fetch the complete documentation index at: https://docs.writerzroom.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Localization
> Adapt approved work for another language, region, or jurisdiction while verifying the claims and disclosures it must carry survived.
**Localization**, under Intelligence 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.
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:
| Verdict | Meaning |
| -------------- | ----------------------------------------------------------------------- |
| `preserved` | The text was found in the variant |
| `missing` | Same-language variant, and the text is not there |
| `unverifiable` | The variant is in another language; text matching cannot establish this |
| `attested` | A reviewer who reads both languages vouched for it |
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**.
### Reports go stale deliberately
Editing the variant's text or either locale clears the stored parity report. Leaving a green result attached to text it was not computed from is exactly the false assurance this feature exists to prevent. A variant that has never been checked is counted as unchecked, not as passing.
The registry a variant's required claims are attached from.
Rules that decide which disclosures a market needs.