Glossary

This glossary collects the terms that matter most when reading or using MindMux.

Agent

An execution-oriented worker context, especially for dispatched tasks or review flows.

The local file-backed durable knowledge layer of a project.

The current best understanding stored on a page. Unlike timeline history, it can be rewritten as understanding improves.

An external integration surface, usually implemented through MCP.

The in-app discussion role used in sessions. This term is intentionally distinct from agent.

The lifecycle state of a page: draft, active, or archived. Ordinary reads default to active only.

A structured knowledge unit in brain/pages/ representing a decision, concept, person, reference, or project thread.

The model setup users choose in the app, including runtime, model, and required connection details.

The main product-facing unit of work. Some implementation details may still use the term workspace.

The six project-wide documents that define the overall shape of the project brain.

The model execution backend that powers sessions or tasks.

A line of discussion with its own context, runtime choice, expert, history, and origin relationship.

The execution handoff object created when discussion becomes actionable work.

The historical record on a page that preserves decisions, observations, sources, and reversals over time.

The origin relationship that tracks where a session or branch came from.