Language and Terminology

MindMux has a few terms that need to stay consistent across product copy, docs, and implementation notes.

Preferred terms

Project

Use project as the main product-facing term. Although the implementation uses workspace in many places, project is clearer for users.

Brain

Use brain for the durable knowledge layer stored on disk.

Expert

Use expert for the in-app discussion role.

Agent

Use agent for execution contexts such as delegated task workers or review flows.

Runtime and profile

Use these terms for the model execution layer and its configuration.

Task

Use task for outbound execution work created from settled discussion.

Language governance

The product supports explicit language policy rather than leaving AI output language to chance. The codebase separates UI locale concerns from AI working-language behavior.

That matters because MindMux writes knowledge artifacts, not only ephemeral chat answers. The language of those artifacts needs to stay coherent.

Documentation implication

When writing documentation, prefer clear stable product language over leaking internal implementation vocabulary unless the distinction itself is architecturally important.