7.6 Interface wording guide
Teloa is built for people who lead an AI team, not for software engineers. The app, the marketplace site and the user documentation use the wording in the right-hand columns below. Each idea uses one word everywhere, and every interface language uses its own everyday phrasing instead of translating engineering terms literally.
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 a colleague 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 solution 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" for Cloud remains a normal business term |
| 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 |
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.
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.
How regressions are prevented
The app's ten interface languages, session confirmation cards and refusal reasons, client fallback text and marketplace page text share one forbidden-word list. If new or changed text brings back a term from the left-hand column, the test fails. The list is narrowed by context: it blocks version-locking uses of "pinned" and engineering uses of "declared", but not everyday phrases such as a payment receipt; interface-position uses such as Pin to sidebar sit in an exemption table with a reason for each entry. A second check makes sure text that means "lock" in English is never translated as "correct" in other languages. These checks read text only, not field names or identifiers.