Language Boundary

Rule

Chat with the project owner in Chinese when requested. Commit repository content in English.

Prox OS is English-first for v0.1, not English-only forever. Do not add new user-visible language switchers, locale routes, translation overlays, or multi-language marketing promises during this phase unless the task explicitly reopens i18n work. Existing locale infrastructure may remain when it is safer than removing it.

Repository content includes:

• source code;
• comments;
• docs;
• mock data;
• UI copy;
• tests;
• Storybook copy;
• roadmap entries;
• AI workflow guidance.

Chinese user-facing copy must only live in the formal i18n locale files under apps/os-shell/src/i18n/**. If an app does not use i18n yet, write temporary copy in English and document future localization work.

Future i18n can return after privacy/legal copy, payment copy, support workflow, permission language, and regional rollout posture are stable enough to localize without drift.

Why

Prox OS is designed to be AI-readable. A single repository language keeps docs, search, generated architecture reports, and future agents easier to reason about. Chat can adapt to the maintainer. Git artifacts stay English unless they are locale assets.

Guard

Run:

pnpm check:cjk

The check allows the formal i18n tree and fails when CJK text appears in code, docs, mock data, app copy, or AI guidance outside that boundary.