Glossary¶
English equivalents and one-sentence definitions for terms used throughout the documentation. UI terminology follows this table.
Platform and Product Family¶
Term |
English |
Definition |
|---|---|---|
MOI |
MatrixOne Intelligence |
An intelligent platform for multimodal data: data processing, agents, and AI application delivery |
AI Studio |
AI Studio |
A workbench for data and agent development, with Data, Agent, App, and other modes |
Genesis |
Genesis |
Model gateway and model portal providing unified model APIs (formerly Nexus / internally TaaS; always use Genesis in documentation) |
MatrixOne |
MatrixOne |
The cloud database instance in the product family |
Unified Account |
Unified Account |
One shared account for AI Studio / Genesis / MatrixOne; register once for access to all |
Sub-product Switching |
— |
Switch among sub-products from the top bar without signing in again |
Workspace |
Workspace |
Top-level resource isolation unit; data is isolated between workspaces |
Data Mode |
Data Mode |
UI configuration mode for data engineers (shown as “Data” in navigation) |
Agent Mode |
Agent Mode |
Conversation-driven mode for building agents |
App Mode |
App Mode |
Delivery mode for packaging an agent as an interactive application |
MOMO Product Assistant |
MOMO |
Global product assistant that answers usage questions based on product documentation |
Data Dimension¶
Term |
English |
Definition |
|---|---|---|
Catalog |
Catalog |
Workspace data asset center for raw and processed data, models, operators, and more |
External Database Catalog |
— |
Registers only external database metadata; data remains in the source database and queries can be pushed down |
Knowledge Base |
Knowledge Base |
Logical wrapper for Catalog data, provided to agents as a data set |
Data Lineage |
Data Lineage |
Traces the data path from sources to agents and other destinations |
Connector |
Connector |
Channel for data movement: import (external → internal) and export (internal → external) |
Connector Type |
Connector Type |
Template that defines “what can be connected” in Data Mode |
Connector Tool |
Connector Tool |
Representation of a connector type in Agent Mode |
Connector Instance |
Connector Instance |
Ready-to-use connection with credentials configured |
Data Sharing |
Data Sharing |
Cross-workspace “publish → subscribe”; the subscriber usually receives a read-only subscription database |
Capability Dimension¶
Term |
English |
Definition |
|---|---|---|
Tool |
Tool |
Smallest capability unit; programmatic and deterministic |
Operator |
Operator |
Processing unit in Data Mode, such as parsing, chunking, or embedding; after snapshot import, it can appear as a tool |
Skill |
Skill |
Orchestration of tools; a natural-language workbook orchestrated by an LLM and therefore nondeterministic |
Workflow Template |
Workflow Template |
Operator DAG orchestration; after snapshot import, it can appear as a skill; versioned, without branches |
Workflow Instance |
Workflow Instance |
Runtime form of a skill, bound to knowledge bases and parameters; can have branches |
Workflow Branch |
Workflow Branch |
A variation of an instance with small parameter changes for comparing results |
Agent |
Agent |
Container for skills, tools, knowledge bases, and prompts |
AI App |
App |
Interactive application hosted by the platform with an embedded agent |
Summary |
desc |
One-sentence description of a skill’s purpose, used for routing and lists |
Execution Instruction |
Instruction |
Detailed steps followed when a skill is invoked |
System Prompt |
System Prompt |
Prompt at the agent level (do not confuse it with an execution instruction) |
Mechanisms and Runtime¶
Term |
English |
Definition |
|---|---|---|
Snapshot Mechanism |
Snapshot |
Records a version when importing an operator / template, binding to the snapshot instead of tracking live changes |
Task |
Task |
Agent execution path: the user provides a goal and the agent works autonomously (the UI consistently uses “Task,” not “Job” or “Ticket,” for this concept) |
Sandbox |
Sandbox |
Isolated execution environment for code / tools |
Compute Resource |
Compute Resource |
Resource for background jobs, including query resources (SQL) and task resources (non-SQL) |
MCP |
Model Context Protocol |
Model Context Protocol; an agent can act as an MCP Server |
Memoria |
Memoria |
Memory capability across Sessions |
Vibe Coding |
Vibe Coding |
Application-building method that generates an initial draft through conversation and fine-tunes it in the UI |
Billing¶
Term |
English |
Definition |
|---|---|---|
Credit |
Credit |
Unified billing currency of the platform |
AI Service |
AI Service |
Billing for system AI capabilities, including conversations, orchestration, knowledge bases, and system operators; underlying models are hidden and pricing is unified |
Genesis (Billing Item) |
Genesis |
Billing for externally offered model services, priced by model (input / output / cache, and others) |
Bring Your Own Model |
BYOM |
Connect your own model API; the platform charges a fixed service fee independent of model pricing |
Usage-based Billing |
Usage-based |
Credit is deducted based on usage of compute, AI services, storage, traffic, Genesis, BYOM, and more |
Monthly Fixed Billing |
Subscription |
Dedicated support, enterprise identity authentication, and similar services billed at a fixed monthly rate |
Terminology Conventions¶
Use Agent consistently in the UI; internal identifiers may use
agent.Use Task consistently; do not interchange “Job” or “Ticket” for the same concept.
“System Prompt” and “Execution Instruction” serve different purposes and must not be used interchangeably.
Always replace Nexus / TaaS in older materials with Genesis.