Adding a locale
There is no locale bundle to write, extract, or ship. A language is a project setting: add it under Locales in the dashboard, and the SDK fetches its catalog the same way it fetches every other one.
A language is a project setting
The locale store takes any locale code. Set it to a language the project doesn't have yet and nothing breaks — every phrase falls back to its source text, because the source sentence is always the fallback. Add the language to the project and the next fetch brings the real catalog. No build, no deploy.
// Nothing in the app changes — the switcher just gains a pill.
locale.set('de-DE');
// Before German is a target locale of the project: every phrase falls back to
// its source text. After: the German catalog, fetched like any other locale.Adding a language to a live project
Pick the language under Locales and save. What happens to the phrases already in the catalog is the project's when a language is added policy — translate them right away, or ask first. When it asks, the dialog prices the existing catalog exactly, per word, before anything is spent. Say yes and the dashboard shows the new language at full coverage a moment later; the Manager holds one machine draft per phrase, each wearing the model's badge until a person edits it.
From then on the new language is like every other target locale: a phrase that registers tomorrow is machine-translated into it on arrival.
Catching up a language that fell behind
A locale can fall short of the catalog — auto-translate was off for a while, or a batch of phrases arrived faster than a translator worked through them. The dashboard shows how many phrases each language is missing, and the Manager's AI Translate Pending action fills the gap in one run: for the locale you have open, or for the entire project. The project-wide confirmation lists every target locale it will touch and warns that AI translation has a cost per word per locale.
What it costs. Machine translation is priced per word per locale, and every draw lands as a line on the project's credits. Usage & credits on the dashboard page covers the two meters and how a project gets funded.
Adding a language is the one thing in this track that happens in the dashboard rather than in code — which is the point. The people who own the copy decide which languages exist; the app just renders them.