Japanese Product Localization

Establish the product context

1. Identify the surface, component, user goal, action, consequence, product voice, existing terminology, and available space. Treat enterprise and admin UI as product UI, not correspondence.
2. Inspect the source resource and its runtime contract before writing. Ask only when an unknown action, state, or term would change meaning or behavior.
3. Route marketing pages and campaign prose to natural-japanese-writing; route emails, proposals, and relationship-sensitive communication to japanese-business-writing.

Lock meaning and resource invariants

Create a compact ledger of visible meaning and protected structure. Preserve keys, nesting, order where meaningful, IDs, placeholders, plural/select branches, escapes, markup, links, variables, interpolation delimiters, access keys, and machine-readable syntax. Do not add, remove, rename, translate, or reorder them unless the resource contract explicitly permits it.

Keep eligibility, permissions, destructive consequences, amounts, dates, state names, error codes, and uncertainty intact. Do not infer a failure cause, retry behavior, payment policy, or product capability from generic patterns. Escalate a missing fact rather than inventing copy.

Read resource integrity and QA for any structured resource, placeholders, message syntax, or final delivery check.

Localize the interaction

Write the shortest clear Japanese that lets the user recognize the situation and act. Keep one task or decision prominent, use the product’s approved terms and exact control labels, and match tone to consequence. Make actions specific; make destructive or irreversible outcomes explicit.