# RightOS + RightFlow — Terminology Glossary

- date: 2026-07-13
- related: [Concept Guide](./RIGHTOS_RIGHTFLOW_CONCEPT_GUIDE.md)

**Product names `RightOS` and `RightFlow` stay in English in every locale.**

## Languages in this glossary

| Language | Code | Notes |
| --- | --- | --- |
| English | `en` | Canonical for architecture wording |
| Japanese | `ja` | Natural technical Japanese; primary UI for RightOS |
| Simplified Chinese | `zh-CN` | Mainland software / automation usage |
| Traditional Chinese | `zh-TW` | One Traditional set for TW/HK |

Traditional Chinese: prefer terms clear in both Taiwan and Hong Kong technical writing.

## Core questions (must stay aligned)

| Layer | English | Japanese | zh-CN | zh-TW |
| --- | --- | --- | --- | --- |
| RightOS | What may be done? | 何をしてよいか？ | 可以做什么？ | 可以做什麼？ |
| RightFlow | What should happen next? | 次に何が起きるべきか？ | 接下来应该发生什么？ | 接下來應該發生什麼？ |
| Execution | How is it done? | 実際にどう実行するか？ | 实际如何执行？ | 實際如何執行？ |

## Controlled terms

| English | Japanese | zh-CN | zh-TW | Notes |
| --- | --- | --- | --- | --- |
| Right | 権利 | 权利 | 權利 | Broader than login ACL / account permission |
| Rights Layer | 権利レイヤ | 权利层 | 權利層 | = RightOS role |
| Coordination | 協調 | 协调 | 協調 | Not “dispatch”, not “marketplace” |
| Coordination Layer | 協調レイヤ | 协调层 | 協調層 | = RightFlow role |
| Actor | アクター | 行动者 / Actor | 行動者 / Actor | Keep English “Actor” in API docs; UI may use 行动者/行動者 |
| Capability | 能力（Capability） | 能力（Capability） | 能力（Capability） | Keep English token in parentheses on first use |
| Task | タスク | 任务 | 任務 | FlowTask in API |
| Assignment | 割当 | 分配 | 指派 / 分配 | Prefer 割当 (JA); zh-TW: 指派 for assign-to-actor |
| Delegation | 委任 | 委派 | 委派 | Conceptual; v0.1 API approximates via reassignment |
| Reassignment | 再割当 | 重新分配 | 重新指派 | |
| Proposal | 提案 | 提案 | 提案 | Uncommitted coordination suggestion |
| Authority | 権威 / 権限主体 | 权威主体 | 權威主體 | Who may grant or revoke; not “admin login” alone |
| Authorization | 認可 / 権限付与の結果 | 授权（是否允许） | 授權（是否允許） | Outcome of “may” |
| Execution System | 実行系 | 执行系统 | 執行系統 | External to RightOS/RightFlow |
| Boundary Contract | 境界契約 | 边界契约 | 邊界契約 | Normative rename of research “leak” findings |
| Spatial Right | 空間的権利 | 空间权利 | 空間權利 | Place/time usage right; not ownership of space |
| Proof | 証明 | 证明 | 證明 | Machine-verifiable evidence of a right |
| Independent actors | 独立したアクター | 独立行动者 | 獨立行動者 | Different owners / stacks / authorities |
| Cross-authority coordination | 権威横断の協調 | 跨权威协调 | 跨權威協調 | |
| Rights-separated coordination | 権利分離型の協調 | 权利分离型协调 | 權利分離型協調 | Working architectural phrase |

## Forbidden implication checks

| Do not imply when translating… | Avoid |
| --- | --- |
| RightFlow | legal court authority, payment, marketplace, fleet ownership, physical control |
| RightOS | only user accounts, only login permissions, only software ACLs |
| Coordination | 配車 / ride-hailing / taxi dispatch |
| Assignment | automatic creation of a RightOS token |

## API identifiers (do not translate)

`FlowTask`, `Proposal`, `Actor`, `Capability`, `requiredRights`, `requiredCapabilities`, token IDs, OpenAPI path segments.