Terms

The terms explorer is the Concepts view of the Context hub: concept-oriented term management for maintaining consistent vocabulary across locales. Each concept represents a single meaning with terms in multiple languages, lifecycle statuses, and domain classification.

Terms and content memory are kept on the server, shared across every project: one governed source of the team's approved wording.

A concept is more than its terms. In the Context hub each concept also carries typed relations to other concepts (what replaced it, what to use instead, which competitor it stands against), per-market validity, observations, comments, and a story of how it came to be. This page covers the everyday term-management surface; see Context for the richer concept model with relations and governance around it.

Outdated wording

The narration uses terminology that has since been retired. The interface and the behaviour shown are unchanged.

Accessing the terms explorer

There are two ways to open the terms explorer:

1. From a project: click the Terms button in the project view header. This opens the explorer with the project name displayed and source/target locales available for filtering.
2. From the sidebar: click Context in the main sidebar, then Concepts, to reach the workspace-scoped explorer.

Browsing concepts

The explorer displays concepts in a paginated table with these columns:

Column	Description
Source Term	The term in the source language
Target Term	The term in the target language
Domain	Subject area classification (for example "legal", "medical", "UI")
Status	Lifecycle status badge
Updated	Date the concept was last modified

Clicking a concept opens its dashboard, the per-concept page that gathers its terms, geography, constraints, direct relations, and timeline. The concept count badge in the header shows the total number of concepts matching current filters.

Term lifecycle statuses

Each term carries a lifecycle status that communicates its approval level:

Status	Meaning
Preferred	The recommended term; use this one
Approved	Accepted for use
Admitted	Acceptable but not preferred
Deprecated	Was once approved but should no longer be used
Proposed	Under review, not yet approved
Forbidden	Must not be used

Searching

Type in the search box to filter concepts by source or target term text. Results update as you type.

Filtering

Use the filter controls to narrow the concept list:

• Source locale filter: show only concepts with a term in the specified source language
• Target locale filter: show only concepts with a term in the specified target language
• Status filter: show only concepts with a specific lifecycle status

Filters can be combined with text search. Changing a filter resets to page 1.

Adding concepts

Click Add Concept in the header to create a concept, the unit of meaning that terms attach to. A new concept starts with a first term and a proposed status. To round it out with terms in other languages, a domain, relations, and per-market constraints, open its dashboard and edit it there.

Editing concepts

Clicking a concept opens its dashboard: the per-concept page that gathers its terms, geography, constraints, a local relations widget, and a timeline. Terms and their metadata are edited on the dashboard rather than inline in the table.

How an edit applies depends on whether it is governed:

• Ordinary edits, such as adding or correcting a translation, adjusting a domain, or moving a term to a non-governed status, apply directly.
• Governed edits, such as setting or clearing a term's forbidden or preferred status, setting or clearing a concept's do-not-translate flag, recording a replaced_by relation, or deleting a concept, are bundled into a reviewable change-set whose blast radius is measured before anyone approves it.

A concept created with its do-not-translate flag set is governed too. Promoting an entity marked do-not-translate, approving a context-scan term marked that way, or adding such a term through the MCP term_add tool proposes the concept in a change-set of its own, and the concept appears once that change-set merges. Approving a term candidate marked do-not-translate in the review queue creates the concept with the flag, because that approval is the review.

Deleting concepts

Deleting a concept is a governed action. From the concept dashboard, the delete is added to a change-set and removes the concept only once that change-set is approved and merged, so a concept other content still references cannot disappear unreviewed.

Import and export

Import from CSV

Click Import CSV and select a CSV file. The expected format:

source_term,target_term,source_locale,target_locale,domain,status
login,connexion,en,fr,UI,approved
password,mot de passe,en,fr,UI,preferred

Import from JSON

Click Import JSON and select a JSON file containing an array of concept objects:

[
  {
    "source_term": "login",
    "target_term": "connexion",
    "source_locale": "en",
    "target_locale": "fr",
    "domain": "UI",
    "status": "approved"
  }
]

Export to JSON

Click Export JSON to download the whole terms store as a JSON file, for backup, sharing with other workspaces, or importing into external tools.

Pagination

When there are more than 50 concepts, pagination controls appear below the table:

• Previous / Next buttons to navigate pages
• Page X of Y indicator showing current position

Terms in the editor

Terms are also used within the editor:

• Context panel: shows per-block term matches with source terms, target suggestions, status badges, and domain labels
• Term checks: validate that a target uses the terms in force at its point

When a block is selected in the editor, the context panel looks up matching terms and displays them alongside memory matches. See The editor for details on the context panel.

Concept model

The terms system is concept-oriented, in the manner of the TBX (TermBase eXchange) standard:

• A concept represents a single meaning or notion
• Each concept has terms in one or more languages
• Terms have metadata: lifecycle status, domain, and notes
• Concepts are scoped to the workspace and shared across all projects

The framework owns this concept and term model; for its architecture, see the framework terms reference.

On the platform, the same concepts are the nodes of the context graph, with typed relations, per-market validity, observations, comments, and governed change-sets layered on top. When you are ready to model how concepts relate rather than just curate terms, start at Context.