7.6 Interface wording guide
Wording table
| Earlier engineering term | Wording now | Chinese wording | Where it is used |
|---|---|---|---|
| artifact | resource files / model files | 资源文件 / 模型文件 | Files shipped with a marketplace resource are resource files; weights and tokenizer files downloaded for a local model are model files |
| vendor artifact | the original vendor's files | 原厂发布的文件 | Distinguishes a community conversion from the vendor's own release |
| snapshot | saved copy; goal at that time; task content as captured at that time | 存档 / 当时的目标 / 任务当时的内容 | The copy kept when a file or business data was read (different from archiving a plan); old data on your computer is described as system backups |
| pinned | locked | 锁定 | A version, source or run input stays the same even when the source is updated. Permission and security actions avoid "lock" and say "choose the versions that can be read" or "targets set at approval", so it is not read as locking an account, a host or a permission |
| fixed content | saved content | 已保存的内容 | Content kept in your market directory for reuse |
| pinned knowledge (role) | assigned knowledge | 指定的知识 | Knowledge chosen for an employee to cite first |
| pinned output / pinned delivery | output finalized / finalized deliverable | 成果定稿 / 定稿的交付 | The output version delivered when a task is completed |
| declared / declaration | definition / required / listed / stated | 定义 / 所需 / 列出 / 注明 | Record types and views in a business package are definitions; skills a role needs are required skills; a missing license is "not stated" |
| fingerprint | checksum | 校验值 | The value on a confirmation card that shows files were not changed |
| upstream | original author / original source / the original | 原作者 / 原始来源 / 原版 | Where a marketplace resource was first published, and the changes made relative to it. The marketplace site uses one Chinese term for it |
| downstream | target system | 目标系统 | The external system that actually receives an action |
| receipt | response from the target system / operation record | 目标系统的答复 / 操作记录 | A message from the target system saying an action was accepted or took effect. It is not called a confirmation, which would be confused with your own confirmation. The history kept afterwards is an operation record |
| instance | loaded resource / identifiers of this installation | 已加载的资源 / 本机标识 | Connections, tools and data sources created when a team template is loaded; a shared package never carries identifiers of your computer |
| off-catalog | not in catalog / unlisted | 未收录 | A model that is not in the official catalog and has not been verified against it |
| manifest | resource list | 清单 / 资源清单 | The file that lists the resources in a package, such as teloa.json. Other languages no longer translate manifest literally; prompts sent to the model keep the machine name manifest in parentheses |
| hosted files | files kept by the marketplace | 市场保存的文件 | Resource files stored in the marketplace repository; "hosted service" describes operation and maintenance, without implying independent Pro cloud execution |
| content adapted | content only | 仅提供内容 | The resource contains instructions and methods but no program to run |
| stub / fixture | simulated test channel / simulated environment | 模拟通道 / 模拟环境 | Parts used only for acceptance testing that do not connect to a real service |
| host | the device running Teloa / the current Teloa / Teloa | 运行 Teloa 的设备 / 当前 Teloa / Teloa | Network, storage and memory belong to the device running Teloa (your computer in the personal edition, the server in a server deployment); where something is installed is the current Teloa; actions the program takes are simply Teloa's. Reason: "host" is the engineering word for the program that carries plugins, and readers cannot tell whether it means their computer or some service |
| credentials | keys | 密钥 | API keys, tokens, channel app secrets and other values Teloa stores encrypted; the settings page is Key storage; OAuth contexts say authorization; the file that encrypts key storage is the master key file, and "key" means only the stored values. The command name teloa credentials and the file name .credentials.meta.json stay as they are. Reason: the rest of the interface already says keys, and one thing should have one name |
| runtime | inference program / when it runs | 推理程序 / 执行时 | The separately downloaded program that runs a local model is the inference program; "at runtime" becomes "when it runs". Other languages drop runtime-style words too: the run environment becomes environment (Japanese 実行環境, Korean 실행 환경, German Ausführungsumgebung), a run configuration is a run configuration, and the Connections and runtime settings page is Connections and environment. Reason: runtime is a programming term and does not tell readers it is something to download |
| Harness | agent engine / employee | 智能体引擎 / AI 员工 | The underlying engine is the agent engine; the one doing the work is an employee. The product name DeepSeek Harness (DSH) and the product-layer name Agent Harness stay as they are. Reason: Harness is an English engineering word that should not appear in Chinese app text |
| release (ship) | shipped with the app | 随应用提供 | Official extensions that come with the installer. Reason: the Chinese publishing term reads as distribution jargon; "shipped with the app" is plainer |
| digest / hash | checksum | 校验值 | The value used to check that a file or content has not changed, the same word that replaced fingerprint. The Chinese word for digest stays only in its "summary" sense, for example "the source did not provide a summary". Reason: one Chinese word meant both a content summary and a hash value |
| SDK | SDK (not replaced) | SDK | A common industry term that the interface uses as is, for example "The Feishu/Lark SDK is missing or damaged"; it is not reworded, and the plain-language checks do not flag it |
Actions that place an item on screen, such as "Pin to sidebar", keep the word Pin. They describe a position in the interface, not a version.
Names of resource types
The marketplace is organized into AI employees and AI teams, with Apps (apps and skills) alongside (Chinese: AI 员工, AI 团队, 应用). Dashboards, materials, task templates and similar items appear as components or filters. A template with a single employee belongs under AI employees; team templates with several employees and business dashboards belong under AI teams. The app, session confirmation cards and the user documentation use these words for these resources; the older names in the left-hand column are no longer used.
| Earlier name | Wording now | Chinese wording | Where it is used |
|---|---|---|---|
| AI colleague / digital colleague / digital employee / sub-employee | AI employee | AI 员工 | A lasting role you create and manage. Use employee when the context is clear. Temporary task-team members are task assistants; your twin (My twin) keeps its separate name. |
| role (meaning the employee itself) | AI employee | AI 员工 | Employee status, employee memories, employee permissions, create an employee. "Role" still names a kind of job, such as the general role preset when hiring |
| plugin (a marketplace extension) | app | 应用 | Plugin-type entries in the marketplace and on the Apps page appear as apps. The engine's own settings page (the list under Settings > Connections and environment) keeps the upstream wording in Simplified Chinese and English |
| connector | connection | 连接 | The type is always "connection"; write "MCP connection" when the protocol matters |
| automatic plan | automation / continuous plan | 自动化 / 持续计划 | The navigation and business sections are called Automation; each item is a continuous plan |
| Skill in Chinese and other non-English interfaces | the local word for skill | 技能 | Every non-English interface uses its own word except German, which keeps "Skill" because "Fähigkeit" already translates "capability". SKILL.md, field names and placeholders such as {skills} stay unchanged |
What is not renamed
- Machine identifiers such as folder names, field names, APIs, error codes and rule IDs stay as they are, for example
artifacts/,deliveryandteloa/invalid-input. - Developer pages that describe internal implementation may keep engineering terms. Guidance for people who submit resources uses the wording above.
- Titles, summaries and compatibility notes of marketplace resources come from the marketplace repository and change only through its review.