# Java Assist — Internationalization
Load the generated `teaql-i18n.json` as an `I18nCatalog`, call `context.installI18nCatalog(catalog)`, then select the request locale with `context.setLocaleCode(code)`. Checker rule ids remain stable; only `naturalLanguageStatement` is localized. Reject `UnsupportedLocaleException` as an input error.


---

## TeaQL seven-language assist contract

Apply the verified Rust semantic ceiling while using only the exact JAVA generated and
runtime APIs. Discover APIs through the generated application AGENTS.md and progressive
model-aware Assist. Do not inspect generated domain-library source.

- Do not create plurals by appending `s` or `es`; use the centralized generated plural.
- Human and non-human entities use different generated predicate vocabularies. Preserve
  forms such as “who are active” and “whose email is”; never infer them from English.
- Configure filters, projection, paging, and other query options before `purpose(...)`.
  Comment may appear anywhere in the chain. Purpose enters the executable stage; execution
  requires both values, but comment does not have to immediately precede purpose.
- Every execute/list/stream and every save accepts exactly one context argument:
  `UserContext`. Name that argument `context`, never `runtime`; data services and global
  policy are injected when the context is built. Reserve `runtime` for process-level
  runtime ownership, provider/pool setup, and module assembly.
- Tenant, merchant, identity, permissions, request policy, purpose policy, hard limit,
  and continuous-page cursor policy come only from trusted context, never dynamic JSON or TFP.
- If the required operation is absent after current entity/action and required field
  Assist, stop that path and report MISSING_ASSIST. Do not guess an API or search the
  generated library as a fallback.
- Create each application-owned source file once. After its first compile attempt,
  repair only the smallest block identified by the exact compiler or test diagnostic.
  Preserve unrelated code; do not rewrite the complete file as an error-recovery loop.
- Before a repair that would replace more than 25% of an existing application file,
  stop and report LARGE_REWRITE_REQUEST with the file, exact diagnostic, reason, and
  estimated scope. Initial creation and model-driven regeneration are not repairs.

Capability: `i18n`.

- Select locale on UserContext before checker execution. Unsupported locale codes
  are typed errors and must leave the previous context locale unchanged.
- Install the generated teaql-i18n.json application catalog explicitly. Resolution
  order is application selected locale, built-in selected locale, application
  English, built-in English, then the stable message key.
- Keep checker rule ids stable and render only display messages. Never infer locale
  from process environment or perform implicit catalog file I/O.