Glossary - HeavenBase

A shared vocabulary is cheaper than debugging two correct ideas with the same nickname.

1. Motivation

These definitions keep public docs, Chinese translations, APIs, and architecture references aligned. Translators should also follow _docs-guide/doc-trans.md and _docs-guide/terminology.md.

2. Core Concepts

Term	Definition
Context	Owner of configuration, one Registry kernel, module resolution, and live workspace state
Workspace	Durable application boundary for schemas, placements, Backends, rows, and domain APIs
Entity	Logical schema class with typed fields; extends `hb.Entity`
Backend	Physical storage or execution provider such as SQLite, Postgres, or Milvus
Routing	Placement and dispatch of Entity fields and query fragments
Handler	Operation-specific execution implementation selected for a Backend route
Strategy	Physical storage strategy such as `InlineColumn`, `SideTable`, or `VectorIndex`
Catalog	User-facing index of concrete Entity objects in a workspace
MetaSchema	Safe projection of workspace structure and installed Registry metadata
Registry	Context-owned data-first record store used for module and engine definitions
Module	One built-in or external folder described by `meta.yaml` and managed by `ModuleService`
Extension	Workspace domain activated from an installed Registry definition
Capsule	Required executable-manifest domain for capturing and restoring trusted callables
Tool	Agent-callable function backed by a Capsule
Toolkit	Named Tool collection persisted with referenced Capsules in an application workspace
Prompt	Callable template persisted through the packaged Prompt extension
Query	Immutable typed data request compiled from Python or JSON
ResultFrame	Detached transport result returned by every query execution
Capability	Inspectable support option or exact execution evidence
Preset	Named configuration bundle, used for workspaces or LLM routes
Provider	Service that hosts an LLM model
Gateway	Transport adapter used after LLM model and Provider resolution
Endpoint	Provider or Gateway URL and API surface
Model	Canonical LLM catalog key or alias
Session	In-memory multi-turn LLM state; persistence is a separate future boundary
Agent	Autonomous actor that uses workspace APIs, Tools, and LLM routes

3. Search and Storage Terms

Term	Definition
SparseGramIndex	SQL-hosted strategy for reverse containment over short keyword arrays
Sparse GRAM	Candidate index using weighted trigrams and exact verification
Reverse containment	Checking whether stored short values occur in a longer query string
Match metadata	Reserved `match` evidence describing which values and spans matched
Embedding	Vector representation produced by an embedding model
Vector	Numeric array stored and searched by vector-capable Backends

4. Chinese Translation Reference

English	Chinese	Keep English in code
Context	上下文 (Context)	Yes
Workspace	工作区 (Workspace)	Yes
Entity	实体 (Entity)	Yes
Backend	后端 (Backend)	Yes
Registry	注册表 (Registry)	Yes
Module	模块 (Module)	Yes
Extension	扩展 (Extension)	Yes
Gateway	入口 (Gateway)	Yes
Endpoint	端点 (Endpoint)	Yes
Preset	预设 (Preset)	Yes
Provider	提供商 (Provider)	Yes
Agent	智能体 (Agent)	Yes
Query	查询 (Query)	Yes
ResultFrame	结果帧 (ResultFrame)	Yes
Toolkit	工具集 (Toolkit)	Yes
Handler	处理器 (Handler)	Yes
Routing	路由 (Routing)	Yes
Catalog	目录 (Catalog)	Yes
MetaSchema	元模式 (MetaSchema)	Yes
Capsule, MCP, LLM	Keep the English product term	Yes

5. Translation Rules

Translate prose one line at a time while preserving structure and links.
Keep code fences byte-identical.
Use Chinese corner brackets 「」 for quoted prose.
On first mention or in headings, pair important Chinese concepts with their English term.
Do not translate identifiers, configuration keys, CLI flags, package names, paths, or URLs.

Summary

Architecture terms name one owner and one contract.
Runtime session state is not durable persistence.
Chinese prose translates concepts while code retains canonical identifiers.

Further Exploration

Related resources:

Architecture — See the terms in their ownership model
API Overview — Map concepts to public Python surfaces
Extensions — Understand Module and Extension boundaries

​1. Motivation

​2. Core Concepts

​3. Search and Storage Terms

​4. Chinese Translation Reference

​5. Translation Rules

​Summary

​Further Exploration

1. Motivation

2. Core Concepts

3. Search and Storage Terms

4. Chinese Translation Reference

5. Translation Rules

Summary

Further Exploration