CMP42 // PRODUCT // CONTEXTMOVEMENT 01 OF 03
// 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.

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.

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.

get_context · response shapeIllustrative
# 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 →

// Questions on this

What people ask here

The same answers as in the CRM FAQ, next to the case they belong to.

BAS-05

What happens to activities such as calls, e-mails and meetings?

Activities and notes are records in the graph, linked to the contact, the company and the deal. This includes content that classic CRMs leave out: documents, call recordings, product briefings and playbooks.

In practice, Claude can write a note back after a call with the write_note tool. The note is validated, versioned and attributed to the agent that wrote it. In the next conversation the agent reads it again.

Prompts and sources for this question

Decided1
BAS-06

Why not just paste a CRM export into ChatGPT, or use Notion with Claude?

An export is a snapshot without structure, and Notion is a collection of documents. An agent answers questions from them as it would in a chat, and has to guess. In CMP42, asked “Who at Aspen owns the Q4 renewal?”, the agent follows named edges (contact owns deal) and names the records it read. The answer can be checked instead of merely sounding plausible.

Prompts and sources for this question

MKT-05

How does CMP42 support customer retention?

Retention is often decided at the renewal. A typical use case for product-led B2B teams: an agent reads the real customer history and drafts the renewal note, and a partner reviews and approves it. If a note points to a risk, such as a new budget holder, it is recorded on the company with its author.

Not to be confused: “retention” also means the retention period for data. CMP42 has an answer for that too, the project record after the close (see chapter 6).

Prompts and sources for this question

DAT-03

How does data quality stay high when agents write?

Data quality means complete, correct, current and consistent. Agents are both a risk and an opportunity here. CMP42 works on four points:

  • Validation on write: if a value does not fit the Model, the agent gets a clear error and corrects itself.
  • Lean standards: no contact with 200 fields. What is not in your ontology does not exist.
  • Attribution: every change names a person or an agent as its author.
  • Versioning: every record has a history with time and source.

Prompts and sources for this question

Decided1
DAT-06

Is CMP42 the "single source of truth"?

CMP42 is meant as the central context layer that every agent reads. It does not promise that contradictions disappear. When two sources disagree, for example two CRMs with different lifecycle stages for the same customer, the graph shows both values with their origin and timestamp.

The decision about which value applies is made by a person, and the Process records it with its author. So “single source of truth” here does not mean “one value”. It means “one place where you can see why a value applies”.

Prompts and sources for this question

Decided1

Decided and on the way. Say which one you need first:

  • Open - you decide1Documents, transcripts, playbooks
  • Open - you decide1Customer journey timeline

All 43 questions in the CRM FAQ

¹ Planned for a future release.