Decide which corrections become rules

Find the reusable reason behind a translation edit, define its limits, and test it before changing shared guidance.

A reviewer improves a sentence by correcting what is wrong in that sentence. Shared guidance has a wider job: it must help other translations without carrying a local preference into cases where it does not belong. The decision depends on the reason for the edit.

Keep the source, generated target, accepted edit, locale, context, and reviewer explanation together. “This sounds better” identifies a preference but may not explain a reusable requirement. Ask what meaning or reader need the correction serves before generalizing it.

Put the reason in the appropriate resource #

An incorrect product term can support a glossary change. A repeated mismatch in register can support a voice variation. A recurring loss of a condition can support a translation rule. An isolated awkward sentence may need only the local edit.

Suppose a translation uses the physical meaning of “workspace” where the source names the product's shared project area. The reusable lesson concerns that product concept. Replacing every occurrence of “workspace,” including physical uses, would generalize the edit incorrectly. Term boundaries explains how to preserve that distinction.

Write a requirement with a counterexample #

A useful instruction says what should happen and when. For statements about availability, an illustrative requirement could read:

Preserve whether availability is certain, conditional, or possible. Keep any approval requirement attached to the claim. Allow natural changes in wording when they preserve those relationships.

Test it against both a definite statement and a qualified possibility. An instruction to “always sound certain” would fail the second case, even if it improved the first. The counterexample makes the boundary visible before the change reaches other content.

Keep locale and content scope as narrow as the evidence supports. Several edits in one language do not establish a global rule, and a style preference cannot override a factual or legal requirement. Use conflict resolution when the competing instructions each have a legitimate purpose.

Inspect a generated suggestion as a proposal #

Localization-engine suggestions can draft a term, rule, or voice change from feedback. Read the cited evidence, target resource, current value, proposed replacement, and locale scope. A suggestion can duplicate existing guidance, refer to a deleted target, or infer more than the correction supports.

Inspect every localization engine sharing that resource. If other consumers need the existing behavior, choose a separate resource or narrower scope. The correction and the shared change need separate approval.

Automatic settings do not mean every human edit is immediately applied. Human-derived proposals remain pending under the documented suggestion policy. When an assistant performs the change, delegation should make the permitted writes explicit.

Compare cases that could expose a bad generalization #

Save earlier guidance and outputs. Apply only the approved change, verify it persisted, and request fresh translations for the original case, an independent similar case, and the counterexample. Applying a suggestion does not schedule this comparison itself.

Inspect both improvements and damage. If the change helps only the original sentence, keep it local. If it harms other content, narrow or reverse the guidance. If the examples support reuse, record the approved scope and reasons without treating a small comparison as a measured general improvement.

Preserve a useful reason when declining #

A dismissal can explain duplicate guidance, missing evidence, wrong locale, ambiguous source, or unsafe generalization. It need not discard the accepted sentence. It records why that local decision should not become a broader requirement.

The finished result can be a tested shared instruction or a deliberate local correction. Both preserve useful reviewer work; only one changes what later requests should do.