Skip to main content
Canonical terminology for English docs and Chinese (zh/) translations. Translators should follow _docs-guide/doc-trans.md and _docs-guide/terminology.md.

1. Core Concepts

TermDefinition
WorkspaceThe HeavenBase container that holds schema, backends, routes, and data
EntityA logical schema class with typed fields; extends hb.Entity
BackendA physical storage provider (SQLite, Postgres, Milvus, in-memory, …)
RoutingField-level mapping from entity fields to backend instances and strategies
HandlerAn operation-specific execution unit compiled for a specific backend
StrategyA storage strategy within a backend (e.g., InlineColumn, SideTable, VectorIndex)
CatalogThe user-facing directory of concrete entity instances in a workspace
MetaSchemaThe internal workspace, entity, field, route, backend, and capability metadata catalog
Gateway (for LLMs)The transport adapter that sends LLM requests after preset, model, and provider resolution
EndpointA provider base URL or API surface HeavenBase calls through a gateway
ProviderThe service that hosts a model (OpenRouter, OpenAI, Anthropic, …)
PresetA named LLM configuration bundle (model, gateway, default args)
ModelA canonical model key or alias resolved through the LLM catalog
AgentAn autonomous actor that uses workspace APIs, tools, and LLM presets
ProxyHTTP or environment proxy settings applied to outbound LLM or DB requests
RouterRequest routing layer (distinct from field-level storage routing)
PromptA callable prompt entity backed by Capsule manifests and system prompt rows
SpecA structured operation descriptor such as QuerySpec or FieldSpec
QueryA typed data retrieval operation compiled from Python or JSON filters
EmbeddingA vector representation produced by an embedding model
VectorA numeric array stored and searched by vector backends
SessionA persisted multi-turn LLM conversation record
ToolkitAn MCP tool collection generated from a workspace
CapsuleA serialized Python callable stored as a HeavenBase entity
ConfigManagerThe HeavenBase-native configuration manager

2. Chinese Translation Reference

EnglishChineseKeep English
Gateway (for LLMs)入口No
Endpoint端点No
Preset预设 / 预置Identifier in code
Provider提供商Identifier in code
Model模型Identifier in code
Agent智能体 / AgentEither; capitalize Agent when emphasizing
Proxy代理No
Router路由No
Prompt提示 / 提示词Identifier in code
Workspace工作区No
Entity实体No
Spec规范Type names stay English
Query查询No
Embedding嵌入No
Vector向量No
Session会话No
Toolkit工具集Product name Toolkit in nav
Backend后端No
Handler处理器No
Routing路由No
Catalog目录No
Caching缓存No
HeavenBaseHeavenBaseYes
HarnessHarnessYes
MCPMCPYes
SkillSkillYes
HookHookYes
LLMLLMYes
CapsuleCapsuleYes
MintlifyMintlifyYes

3. Formatting Rules for Chinese Docs

  • Use corner brackets 「」 for quoted phrases in Chinese prose.
  • On first mention, in headings, emphasis, or when paired with code identifiers, append the English original in parentheses: 入口 (Gateway), 端点 (Endpoint), 预设 (Preset).
  • Avoid casual “runtime” wording; prefer concrete terms. Use 执行 only when execution context is the intended meaning.
  • Do not translate executable code, config keys, CLI flags, package names, file paths, or URLs inside code fences.