Context should explain the intended meaning

We choose context for the understanding it contributes, and treat its processing responsibilities as part of that choice.

An author can use a short term because the surrounding product makes its meaning clear. A translator receiving that term alone may have several reasonable interpretations. More fluent language cannot resolve missing product knowledge.

Context connects those two situations. A definition explains the concept; an instruction explains a requirement; an account of the audience explains why a particular tone is appropriate. We favor context selected for the understanding it contributes to the translation task.

Relevance makes shared knowledge useful #

Lingo.dev's localization engines link to terminology, instructions, and voice guidance that can be reused across requests. Retrieval selects applicable material for the content and locales involved. The context-retrieval reference explains those mechanisms and their different matching rules.

The purpose is to make the team's knowledge available when it changes the answer. A term definition can distinguish a product feature from an ordinary use of the same word. Audience guidance can explain a choice of formality. A relevant exception can prevent a general instruction from changing a name that must remain recognizable.

An unrelated document does not become useful merely because it contains more information. It can introduce a competing interpretation or make the important requirement harder to identify. Good context has a reason to be present, and the team should be able to explain that reason when inspecting an unexpected result.

This is also why guidance needs maintenance. A definition that once described the product correctly may become misleading after the product changes. The organization is preserving knowledge, not just accumulating text to send to a model.

The information and its recipients both matter #

Useful context can contain sensitive information. A glossary may name an unreleased product. An example may describe a customer's situation. Reviewer feedback may include details that explain why a translation was wrong. None becomes harmless because it sits beside the source instead of inside it.

We treat that context as part of the processing being considered. Using public product terminology for public documentation and using customer-specific details for support content raise different questions. Changing the model provider or involving an external reviewer can also change the recipients while the material stays the same.

The quality benefit and the processing responsibility need one coherent explanation. The customer decides which material its workflow should supply. We remain responsible for the service's own obligations and the commitments on which the customer relies. Careful input selection cannot substitute for that provider responsibility.

Make the provider's part understandable #

A customer considering a use needs to understand what information is involved, why it is needed, and which applicable commitments govern its processing. Translation examples, assurance evidence, and agreements contribute different parts of that understanding. A convincing demonstration of language quality does not answer every question about handling the source.

Our standard is to explain the service's contribution without asking the customer to infer it from a general claim of security. Current processing details and agreements supply the particulars. The customer's knowledge of its content and permitted use supplies another necessary part.

Purposeful context joins those responsibilities around a concrete benefit: giving translation the knowledge needed to preserve meaning. The team can then assess that benefit alongside an intelligible account of the information it entrusts to the workflow.