Glossary
A concise reference for everyday work. Terms evolve with product capabilities.
1. Products and environments
- EvoX
- An AI agent product for completing tasks through conversation and Cowork.
- EvoX Cowork
- A work mode that executes tasks and creates or edits deliverables within authorized scope.
- Workspace
- The project or folder scope available to the current task.
- Artifact folder
- The destination used to save files created by a task.
- Runtime configuration
- Account, deployment, model access, node, and service settings used at runtime.
- Built-in models
- Model access provided by the signed-in EvoMap account, separate from gateway credentials.
- Gateway key
- An optional model or service credential; its absence does not by itself mean models are unavailable.
- EvoMap Hub
- Network services for accounts, nodes, assets, and collaboration.
2. Memory and knowledge assets
- Memory
- Retrievable preferences and background that help later tasks; current instructions take priority.
- Recall
- Retrieving information relevant to the current problem from memory or an asset store.
- Gene
- A reusable strategy with triggers, applicability, and boundaries.
- Capsule
- A structured record of an execution result and its supporting context and evidence.
- Asset
- A general term for retained, searchable, or reusable content such as Genes and Capsules.
- Retention
- Saving verified approaches and outcomes that are useful beyond the original task.
- Recipe
- An ordered combination of Genes and Capsules for a reusable execution plan.
- Swarm
- Multiple workstreams whose results are combined, including local parallel tasks and separately paired, authorized devices.
- Cell
- A collaboration unit representing a working entity in a local or connected environment.
3. Tasks and automation
- Goal
- A continuing task with explicit completion criteria and evidence, bounded by progress, blockers, and budget.
- Goal loop
- Repeatedly checking progress, taking the next step, and verifying a goal’s result.
- Task list
- A visible record of pending, active, completed, or canceled steps.
- Tool
- A callable capability such as file access, search, or document generation.
- Skill
- Reusable instructions and resources for a specific task or workflow.
- Plugin
- An extension providing connected data, tools, or reusable workflows.
- Scheduled task
- A saved prompt run at a specified time or interval.
- Verification
- Checking the resulting state against the request after an action.
4. Files and deliverables
- Document
- Readable content such as reports, notes, and plans, delivered as text, Markdown, or office files.
- Component
- Interactive HTML or SVG content, such as a chart, dashboard, calculator, or demonstration.
- Office file
- A structured .docx, .xlsx, or .pptx file.
- Rendering
- Converting source content into a visual result for reading or printing.
- Preview
- Viewing an artifact’s rendered or source content; confirm its saved location and version separately.
- Revision
- Updating an artifact from feedback, in place or as a new version according to the request.
5. States and signals
- In progress
- A task or step currently being worked on.
- Completed
- Marked as finished; inspect the output and verification evidence to judge whether it meets the request.
- Blocked
- Unable to continue because of permissions, credentials, external services, or a required decision.
- Capability gap
- Available tools do not cover the requested action.
- Error repair
- Diagnosing, correcting, and verifying an error in tools, code, or input.
- Stable-success plateau
- Results remain stable but no clear improvement has been identified.
6. Usage principles
- Current request first：Memory and retrieved information are references, not replacements for explicit instructions.
- Read before editing：Inspect the current artifact rather than editing from stale assumptions.
- Verify the result：A successful tool call alone does not establish a correct outcome.
- Distinguish node types：Account devices, collaboration nodes, and service channels are different objects.
- Do not infer absence：Information not yet inspected is not necessarily missing.
- Retain useful experience：Save approaches as Genes or Capsules only when verified and reusable.