Skip to main content
Each company is one folder. The top of a file has a few short fields. The rest is normal writing. File names use lowercase with underscores.

Files

Context

context.md. Where the deal stands right now. Not old history. Not your to-do list.

Company

company.md. Skip a body line if you do not know it.

People

people/firstname_lastname.md

Tasks

tasks/task_name.md. A task is work you still owe: send a deck, book a meeting, prepare a proposal. A normal reply is not a task.

Company files

files/name.md. Extra notes or drafts for this company. Email and meeting updates do not change these files.

Events

events.jsonl. The history file for this company. One event per line. Only append, never edit.

Docs

docs/ is all context not about one company. No required frontmatter. Company-specific free files go in crm/<company>/files/. Signal updates read only the three files in docs/rules/. All other docs are for people and agents.

Git

Each team workspace is a git repo.
  • Signal updates commit after each change.
  • Your agent should commit after it changes files.
Git is the full history of every file. Use it to see how a file changed and when, for example context.md.

Agent tools in MCP

Agent skills in MCP

Integrations

Why a VM

Each team has its own Linux workspace. The files are real files. And version control is enabled with git. Your agent reads, writes, and runs shell commands on that workspace, the same way it would on a local folder.