The receipt travels with the delivery

What changed and what stayed, item by item, kept and reopenable

Every translation arrives with its own comparison: what changed and what stayed, unit by unit. Slide 12's title, translated; the chart, intact; the speaker notes, translated; the image, intact; fonts and formatting, preserved. You do not need to believe that nothing broke: you see it, and whoever opens the file after you reopens it and sees the same thing. It is the same receipt that [every delivery](documents) carries, applied to translation.

Slide 12 · title	translated	✓ en → pt-BR
Slide 12 · chart	intact	= unchanged
Slide 12 · speaker notes	translated	✓ en → pt-BR
Slide 13 · image	intact	= unchanged
Layout · fonts · formatting	preserved	= unchanged

The receipt accompanies every translation: what changed and what stayed, item by item.

The receipt is not written afterward by someone who watched the operation. It is born from the operation itself, which is why it cannot disagree with it.

The translated version is a document, not an attachment

It enters the vault next to the original, with its own X-ray and measurement

In a folder, an original and its five translations are six files that only one person knows how to relate, and only until that person changes teams. Here the translation enters your vault next to the original as a complete document: read by the engine, measured, navigable on its own, and linked to the original by a lineage that survives the departure of whoever created it.

the originalread and measured on intake

the lineagerecorded, not remembered

the translationwhole document, not an attachment

An original with five declared derivatives, not six files in a folder.

The practical consequence shows up the day someone asks where the Portuguese version that went to the client came from. Comparing the two is one click, not two windows open side by side. What each document carries on intake is in [your documents](documents).

Your glossary

One spreadsheet goes up and holds for the whole delivery, in every language

Upload your glossary, a simple spreadsheet, and it holds for the whole delivery: product names, legal terms, and the jargon of your field come out the same from the first slide to the last, in every language. The glossary is yours, stays versioned in your vault, and is applied to every job that requests it. It is the cheapest differential to describe and the most expensive to go without. Without it, vocabulary consistency across a sixty-slide deck depends on the same person reviewing all sixty, and that holds only until the week the deadline tightens.

And the boundary is checked, not presumed

The model's text enters counted, and a difference fails the step

Translation is the only point in the product where a language model's text actually enters your file. That is why this boundary is the one that is checked rather than presumed: every segment goes out delimited by markers, and what comes back is counted against what went out. A model misbehaving here does not produce a silently damaged document; it produces an operation that did not complete, and you find out before the meeting. The count, what it measures, and what happens when it does not match are in [the conversation is with the AI](docs-by-spec), where the split between the two layers is the entire subject. Here it is a differential; there, it is the architecture.

And today's state, dated. Translation has been down since 2026-08-23 on provider credit, and the last successful run was on 2026-08-20 at 22:43 UTC. This page describes the capability and does not invite a live test until that returns.

Writing and script limits per language are in [languages](languages); what stays in place when the text changes is in [preserved layout](layout).