Context isn't the data sitting around a person. It's the weaving of that information together to create understanding of their situation. Co-Hosts Chris Heuer and Marius Ciortea discuss why community managers have always been context engineers, and why AI doesn't improve the relationship — it makes the context that does affordable.

Key takeaways

• Context is a weave, not just the data. Contexere: con, together; texere, to weave. The data was always in the building. What was missing was the weaving.
• AI doesn't improve the relationship. It makes the context that improves the relationship affordable. Thirty minutes of assembling it by hand becomes a brief that arrives before you reply.
• Community managers have always been context engineers. Naming groups, choosing categories, matching people by attribute — that is context engineering, twenty years before the term.
• Four records, one human. The goal is to see the member, not the four views of them through four systems.
• The job has four steps: aggregate, process, understand, act. Understand is where the human stays.
• It's a permission failure, not an information failure. You don't need a data lake or a golden record. You need read access — and MCP servers are how that access is becoming table stakes.
• The information we have about a member is held in trust. Members hand a community their history, expecting the company to receive it as one company.
• Start with what you can reach. Whiteboard the data by type, not by tool. Circle what you have access to today. Earn the second bucket by showing value.
• The cheapest win is telling the AI where the documentation lives. Ten recorded interviews with internal experts is the next one.
• Draft with the assistant, then don't hit the easy button. Read it, put it in your voice, and check that it isn't bloated, off, or wrong.

Time & Chapter

00:00 Cold open — four strangers who are the same person
00:50 Welcome, and the Anthropic "pace the frontier" news
04:39 The double-edged sword: $30,000 and 68 days, now three hours
06:28 Three C's, Sea-Doo, and why context is king
07:55 Situatedness, and the etymology of context
09:35 "I've been a context engineer for 20 years"
11:34 The assistant thesis: AI makes context affordable
12:15 Palm's three hats, and the weaving job
14:35 AI doesn't improve the relationship; context does
15:15 A word from Higher Logic
16:03 Marius's daily brief — what it knows before you reply
21:18 Systems thinking, MCP servers, and table stakes
24:11 Aggregate, process, understand, act
25:57 Ten interviews and the expertise knowledge graph
29:01 Access, not a data lake
30:33 Trust, disclosure, and nine hours with AT&T
32:00 Three ways to act: prepared, prompted, drafted — and the easy button
36:43 The whiteboard exercise: two buckets
39:13 Tell the AI where the documentation lives
40:35 Your own personal intelligence system, and next week's tease
42:37 Close