Knowledge Domains

A Memco domain defines the semantics for how knowledge is created, searched, and tagged within a specific area of work. Domains shape the behavior of Memco’s MCP tools — the same underlying tools (search, create_memory, enrich_memory) operate across all domains, but the domain determines what tags mean, how context is interpreted, and what metadata the agent should provide.

Why domains exist

Different kinds of work produce different kinds of knowledge. A coding agent learns patterns about APIs, error handling, and architectural conventions. A knowledge worker learns about processes, policies, stakeholder preferences, and domain-specific terminology. These are different shapes of knowledge, and the system that curates, retrieves, and synthesizes them needs to understand those differences.

Domains provide that understanding. Each domain configures:

• Tag semantics — which tags carry specific meaning and how they should be used. In the coding domain, a language tag denotes a programming language; in the knowledge domain, it might not exist at all.
• Tool descriptions — the MCP tool descriptions presented to the agent are tailored to the domain, guiding the agent toward appropriate use of search, creation, and enrichment for that kind of work.
• Curation behavior — Memory Ops operators (synthesis, deduplication, conflict resolution) can apply domain-specific heuristics when processing knowledge.

Built-in domains

Memco ships with two built-in domains.

Coding

The coding domain is optimized for software development workflows. It is designed for use with coding agents such as Claude Code, Cursor, Windsurf, GitHub Copilot, and similar tools.

Knowledge in the coding domain typically includes: API patterns and conventions, error handling strategies, architectural decisions, dependency-specific behaviors, testing patterns, deployment procedures, and codebase-specific knowledge that agents discover during development sessions.

The coding domain defines tags such as language (programming language), framework, and repository to help organize and retrieve knowledge relevant to the agent’s current development context.

Knowledge work

The knowledge domain is designed for broader knowledge work beyond software development. It supports agents operating in areas such as research, analysis, consulting, operations, and any work that involves accumulating and applying structured knowledge over time.

Knowledge in this domain typically includes: process knowledge, policy and compliance information, stakeholder and organizational context, domain-specific terminology and definitions, analytical frameworks, and procedural knowledge.

Multi-domain access

A single MCP connection provides access to all domains available in your workspace. Your agent discovers available domains — including their descriptions, tag vocabularies, and usage guidance — by calling list_domains.

When calling search, create_memory, or other tools, the agent passes a session ID that identifies the working context, including the domain. The agent starts a session in a domain with start_session, then uses that session ID throughout the task.

See the MCP overview for details on how multi-domain support works at the protocol level.

Domain isolation

Knowledge in different domains is fully isolated. A search in the coding domain does not return results from the knowledge domain, and vice versa. This isolation is deliberate: mixing knowledge across domains with different semantics would reduce retrieval precision and make curation less effective.

Memory networks (the organizational hierarchy described in How Memco works) operate within a single domain. An organization’s coding memory network hierarchy is separate from its knowledge work memory network hierarchy.

To see the knowledge work domain in action, Learning on the Job is a runnable example of an agent learning a business’s policies through it, with a measured learning curve.