Briefing
Episode 9 · Primer · About 8 minutes
Download the MP3 · Linda and Leonard, AI voices, read a script written from the sources below.
Written from public sources and checked on 12 October 2026. The talk transcript and the OWASP page on vector stores were read in full; the investor essay, the Model Context Protocol announcement and the privacy regulator's guidance were read in part. The talk is a vendor's view, and its engineering claims are the speaker's own. Quotations from the talk come from automatic captions. Please check the originals before quoting. This is general information, not legal advice.
Before we record, every claim the hosts make is checked against the sources (this table was last updated 12 October 2026). Confirmed means a primary source or two independent reports; Reported means one party says so; Partly right, Disputed, Unverified and Not yet known mean what they say, and the hosts say so on air. This is the table as we left it.
Sign up for our podcast at agile-insights.com.au.
Linda A company brain is a copy of your data... and a copy of your rules. So before you build one, decide who owns each copy, who may see it, how long it lives and who checks what it says. By the end you will know what one is, where the usual account stops, and seven things to settle first. I'm Linda, and Leonard will ask what a newcomer would.
Leonard So that's the main idea. Why now? Because of a talk. Gil Feig is co-founder and chief technology officer of Merge. His talk went up on the AI Engineer channel on the ninth of October 2026. He argues every company needs a context graph, by which he means a company brain. His company sells tools for this pattern, so it is a vendor's view. Linda, what is a company brain made of?
Linda Good place to start. In his account, four parts. Data from the other systems you use. Documents you place there yourself. Memories, which the AI system stores from earlier work. And skills, which are written instructions for how your company does a task.
Leonard And the name itself?
Linda The name context graph was made popular by an investor essay in December 2025. That essay meant something narrower, a record of decisions and the reasons for them. The speaker uses it loosely, for the whole company brain.
Leonard Good. That helps. Here is my newcomer's question. Say an organisation has already connected its AI to its systems with M C P, the Model Context Protocol. That is an open standard, announced by Anthropic in November 2024. It gives AI applications one common way to reach data sources and tools. So if the AI can already look things up live... why keep a copy as well?
Linda Fair question. Here is his answer. The speaker argues that live lookups only answer narrow questions. Why was one customer upset last week? The AI just asks the ticketing system. Which customers were upset last year? Now it must page through every ticket... and he says it times out. So he recommends syncing a copy into a store you keep, one that can be searched by meaning. He admits a copy costs more and is harder to keep current. That is step one.
Leonard That's step one. What comes next?
Linda Step two. The copy is a new store of the same information, so it carries the same duties. The talk covers freshness, with a limit past which the AI asks the live system. It does not say who may search the copy, yet the source system had its own permissions.
Leonard And does that matter?
Linda The security project OWASP warns that poor access control on such a store can disclose personal or proprietary information. Picture a pay question answered for someone barred from the payroll system...
Leonard An awkward Monday. Then there is privacy. His running example is support tickets, and tickets can hold personal information. Australia's privacy regulator is the Office of the Australian Information Commissioner. Its guidance says personal information may be used for the purpose it was collected for, unless an exception applies. So is copying tickets into a searchable store for staff AI a new purpose?
Linda Good one. Let me be careful here. That is a question each organisation must answer... and it depends on the facts. What was collected, what people were told, and what they would reasonably expect. The regulator's guidance says a reasonable expectation may be difficult to establish for an AI use. It also says you still hold information stored with an outside provider. And you must destroy or de-identify personal information once it is no longer needed. So the copy needs a deletion rule. This is general information, not legal advice.
Leonard Noted. So that's the privacy question. Step three. A skill is a rule. The speaker's example is the question, how do we decide a customer is unhappy? One firm counts tickets and another reads survey scores. He says the AI should check skills first, because how you find an answer is itself company policy. He calls skills principles and processes. Rules is our word. If every AI answer follows that definition, who writes it and who signs it off?
Linda Good question. The talk leaves that open. One workable approach has three levels. A rule starts as a draft. Someone who did not write it reviews it. Then a named owner endorses it for a stated scope.
Leonard Clear. That's step three.
Linda Step four. Memories and stored summaries are new records, sometimes about people. The regulator's guidance treats personal information an AI generates or infers as a new collection. So the AI proposes a memory and a person confirms it. A summary carries the restrictions of its source.
Leonard And that's step four. Now for a trap. Here is the common misunderstanding. We connected the tools, so the AI has our company's knowledge. Connecting tools gives lookups. Knowledge needs a copy and a set of rules, and you own both. In fairness, the strongest part of the talk is here. He says to store, with every item, where it was fetched, when, and under whose access. Also how it was changed, and what should make it invalid. His reason is that something will go wrong, and you must investigate.
Linda Yes. That is the governance point. The model is bought. The copy and the rules are yours, and a board, an auditor or a regulator will ask about them.
Leonard Anything else to watch?
Linda OWASP also describes instructions hidden in a document that change what the AI does. So treat anything the AI reads as information, never as an instruction. And the regulator's guidance says checking an AI product is not set and forget.
Leonard If only. So, what do we do?
Linda Seven things to settle first. One, name an owner for the brain and for each skill. Two, before you sync, write down what each copy is for and who may see it. Three, make the copy obey the source's permissions, then test it as someone who should be refused. Four, give every copy, summary and memory a lifespan and a deletion rule.
Leonard That's four. Keep going.
Linda Nearly there. Five, keep the provenance on every answer. Six, let the AI propose and a person confirm. Seven, schedule reviews, and let staff flag a wrong answer.
Leonard And that's the list. Thank you, Linda.
Linda If you'd like to know more, sign up for our podcast at agile-insights.com.au.
Leonard Thanks for listening.
All of the briefings (38) · Follow Briefing in Apple Podcasts or any podcast app
Everything from Agile Insights: briefings, Making You Think and the reference series