Content
What you produce
Documents, meeting recordings, product briefs, proposals. Each is an object with a typed identity, linked to the people who authored it and the accounts it is about.
// Movement 01 · Context · The graph
ONE GRAPH.
NOT FIVE SILOS.
Contacts, companies, deals — yes. But also documents, meeting recordings, product briefs, playbooks, the messy Notion pages. In CMP42 they are one connected object graph. Agents read the graph like a database, not like a chat history.
// The problem with chat history
CONTEXT IS NOT A PASTE.
Today, "giving an agent context" usually means pasting a transcript into ChatGPT or piping a HubSpot export through a Zapier hop. The agent treats all of it as text. It hallucinates the missing bits, invents fields that were never declared, fabricates a pipeline stage that does not exist. Not because the model is bad — because the source was not built for the reader.
CMP42 turns the same data into typed objects with typed edges. When an agent asks "who at Aspen owns the Q4 renewal and what was the last thing they published on this topic?", it walks the graph and answers with citations to source objects — not with vibes.
// What goes into the graph
PEOPLE. CONTENT. KNOWLEDGE.
People
Who you work with
Contacts, companies, deals, tasks, activities — the CRM primitives, with lean defaults. A contact knows a company, owns a deal. Relationships are first-class edges, not free-text fields.
Knowledge
What you know
Playbooks, frameworks, the messy Notion pages. The know-how your team keeps re-explaining becomes context an agent can use on the next engagement.
// How the graph is built
FOUR PROPERTIES AGENTS NEED.
01
Typed edges
Every edge is named: a contact knows a company, owns a deal, authored a doc. An agent never has to guess what a relationship means.
02
Addressable by URI
Every object and every field is addressable by URI. Agents cite exactly what they read — and humans can follow the citation.
03
Content-addressable IDs
Identities stay stable across schema evolution. A migration does not break the references an agent or an integration holds.
04
Versioned + attributable
Every object is versioned. Every write carries an audit trail recording the human or agent that produced it.
// What an agent sees
A GRAPH, NOT A BLOB.
The shape below illustrates the idea: objects with identities, edges with names, sources an agent can cite. The concrete wire format ships with the Alpha and is shaped together with the Design Partners.
# Q: who at Aspen owns the Q4 renewal?
contact: cmp42://contact/… # "Dana R."
knows → company: cmp42://company/… # "Aspen"
owns → deal: cmp42://deal/… # "Aspen · Q4 renewal"
authored→ doc: cmp42://doc/… # "Renewal plan v3"
sources: [cmp42://deal/…, cmp42://doc/…] # cited, versioned
written_by: agent:claude · approved_by: human:…// Out of the box
MCP TOOLS FOR THE GRAPH.
The Context graph ships with an MCP tool surface out of the box — get_context, list_related, write_note — so any MCP-compliant client can read and write against it from day one. How MCP tools work in CMP42 →
// Keep reading