A policy update is incomplete while one supported language still presents the old rule. Track multilingual knowledge assets as dependencies of the canonical business policy and test their decisions after every consequential change.
Knowledge maintenance needs source authority
Multilingual business knowledge maintenance keeps translated explanations, retrieval sources, and response patterns aligned with approved policy. It must cover both the text and the execution rules that determine actual eligibility or commitment.
In a proposed registry, each policy has an identifier, effective date, authoritative owner, affected workflows, and language-specific review status. Source documents and fixtures point to that policy rather than relying on a filename that happens to sound current.
Do not publish an unreviewed translation merely because its source was approved. The translated meaning can still omit conditions or imply a stronger promise. Define a limited-support fallback for language assets awaiting review.
Update a fictional service-area rule
A business removes one district from coverage. The English policy changes immediately, but an older Arabic document remains searchable. A caller using Arabic should not receive an offer that the English caller would be denied.
The release process identifies the affected document, translated explanations, coverage decision, and fixtures. The review checks direct district questions and indirect neighbourhood references. It also confirms that unchanged areas continue to receive the correct answer.
| Asset affected | Required maintenance |
|---|---|
| Canonical policy | Approved rule and effective date |
| Translated source | Reviewed equivalent meaning |
| Retrieval index | Old guidance removed or clearly superseded |
| Tool decision | Current eligibility enforced |
| Evaluation fixture | Expected outcome versioned with the change |
Test conflicting-source cases deliberately. A fresh translation can coexist with an old indexed excerpt, leaving the model to select the wrong authority unless precedence is explicit.
Monitor unresolved language drift
Show which supported assets are current, awaiting review, or withdrawn. Assign an owner and follow-up condition to each gap. A green content deployment does not establish that every language’s operational meaning has been checked.
Centralising policy reduces duplication but requires a careful mapping from decisions to language explanations. Overly rigid shared wording can sound unnatural, while independent prose can drift. Use structured policy results plus reviewed language-specific expression.
This maintenance design is proposed. The voice platform case study describes retrieval and workflow work. Pair it with post-update agent evaluation.
Multilingual knowledge FAQ
Can translated knowledge be updated later than the source?
Only under a defined support policy that prevents stale guidance from being presented as current.
Should old policy documents remain searchable?
If retained, their status and authority must prevent them from overriding current approved guidance.
What proves the update worked?
Reviewed meaning, correct retrieval, consistent tool decisions, and passing fixtures for changed and unchanged cases provide complementary evidence.