No Memory, No Harness: Why the Database Is the Last Line of Defense — Kay Malcolm, Oracle

Read the talk

Why Agent Memory Must Carry Team Context

Kay Malcolm connects a distributed development team’s missing decision history to agent harness design, multiple memory representations, and a shared database-backed memory broker.

From a talk by Kay Malcolm

At a glance

Ideas worth remembering

  • AI-assisted code generation can move the bottleneck to collaboration. Malcolm’s remedy preserves decision context and associates it with forks, branches, and commits so another team member can continue the work.

  • Memory and retrieval have separate jobs: retain useful information, then select the relevant information for the agent’s context. The harness also needs tools, security, and guardrails to turn that context into action.

  • Storage choices involve performance, administrative work, and authority. Malcolm’s SQL relationship query could take about 20 minutes; adding specialized stores increased maintenance meetings and raised the question of which store an agent should trust.

  • The proposed database-backed broker combines several memory representations with shared persistence and model choice. The recording describes that design and its intended benefits, but does not quantify productivity gains or validate reconciliation accuracy.

Faster coding leaves a slower handoff

Selected presentation frame from No Memory, No Harness: Why the Database Is the Last Line of Defense — Kay Malcolm, Oracle at 276 seconds
Faster coding leaves a slower handoff

Kay Malcolm opens with audience participation and introduces the practical setting for her argument: she leads outbound database product management at Oracle, where she has worked for 20 years. Her team spans platform development, content development for LiveLabs, QA, and front-end development. AI has accelerated work within this organization, but she reports that faster individuals have not translated into a more productive team.

Her concrete example is a time-zone handoff. Developers in the Netherlands check in code at 4:00 a.m. her time. When the United States team wakes up, it receives the code without the context from the AI-assisted session that produced it. The artifact survives the handoff; the reasoning behind it does not. The receiving team must reconstruct information that was available to the people doing the original work.

Malcolm describes diverging repositories and continued time spent on testing and validation despite spending on AI and tokens. Her distinction is between recording code and recording human intent: a code history alone does not preserve the decision context she needs. Once code creation becomes faster, collaboration becomes the bottleneck. The missing layer must track progress and next steps, explain agent decisions, and help resolve questions and conflicts. These are observations from her team, without a quantified productivity comparison.

0:120:20
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

0:12 · section reference included

The harness connects reasoning to action

Selected presentation frame from No Memory, No Harness: Why the Database Is the Last Line of Defense — Kay Malcolm, Oracle at 412 seconds
The harness connects reasoning to action

Malcolm pauses the team example to define an enterprise agent. A model and workflow are only part of the system. Tools let it act; context supplies the information in its prompt and context window; memory preserves information for later use. Retrieval then selects the right information to bring back rather than returning everything. Security and guardrails also belong in the harness. Her account distinguishes having information available from choosing which information an agent should use.

Her anatomical analogy makes the responsibilities easier to separate. The model is a brain floating in a glass jar, and the harness is the body that enables it to get things done. Memory is part of the central nervous system, carrying context between the brain and the rest of the body. In this framing, memory connects reasoning to continued action. It is the capability she identifies as missing from her code handoffs.

4:544:58
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

4:48 · section reference included

Five kinds of memory serve different purposes

Selected presentation frame from No Memory, No Harness: Why the Database Is the Last Line of Defense — Kay Malcolm, Oracle at 499 seconds
Five kinds of memory serve different purposes

Malcolm selects five common memory categories. Short-term memory belongs to a session, while long-term memory persists across sessions. Episodic memory records what happened during a previous interaction. Procedural memory records tools and the steps taken. These distinctions separate duration from content: remembering a prior encounter and remembering the procedure used during it answer different questions.

Semantic memory completes the list, although Malcolm does not develop its definition here. She briefly mentions her personal chief-of-staff agent, Sasha Fierce, before returning to enterprise agents. The taxonomy establishes that an enterprise memory system has several kinds of information to retain; it does not yet specify their schemas, retention policies, or retrieval methods.

7:247:27
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

7:24 · section reference included

Specialized stores bring operational costs

Selected presentation frame from No Memory, No Harness: Why the Database Is the Last Line of Defense — Kay Malcolm, Oracle at 754 seconds
Specialized stores bring operational costs

The next question is where memory should live. Malcolm approaches it through her earlier work at Southern Company, a power company, where she tuned SQL queries. The initial environment centered on rows and columns. When a developer requested unstructured storage, she promised to investigate but did not follow up; the developer installed a specialized database.

Each database system she managed required two meetings every week: one for security and one for patching. Adding the unstructured store therefore increased her weekly meeting count from two to four. The story gives database proliferation a concrete operational cost. A specialized store may satisfy a developer’s data requirement while adding another system that someone must secure and maintain.

A relationship-heavy application exposed another tradeoff. Workers restoring power depended on a system that sometimes produced false positives or false negatives. The team wanted to examine nearby infrastructure to reduce those errors. Malcolm implemented the relationship query in SQL using five nested UNION ALL statements. She remembers it as strong work, but says it might have taken about 20 minutes to run. The team installed Neo4j, bringing her meeting count to six. Her example shows that expressing a relationship in relational SQL did not necessarily deliver acceptable performance; the alternative added administrative work.

Malcolm says she left Southern Company for Oracle hoping to help solve this problem. She then extends the story to the addition of a vector database. The progression establishes her concern: new data requirements repeatedly introduce new storage systems, and each addition expands the environment that people—and eventually agents—must navigate.

8:508:51
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

8:50 · section reference included

Who decides which store holds the truth?

Selected presentation frame from No Memory, No Harness: Why the Database Is the Last Line of Defense — Kay Malcolm, Oracle at 792 seconds
Who decides which store holds the truth?

For an agent, the problem becomes one of authority as well as access. Malcolm asks where the single source of truth resides when information is spread across relational, JSON, graph, and vector databases. If the agent must work that out itself, she argues, it can choose incorrectly and consume tokens during reconciliation. She makes a strong claim about frequent errors but provides no measured error rate. She also names filesystem memory and a memory.md file as possible storage approaches, then turns to an exercise to illustrate coordination.

Four volunteers represent a relational database, an unstructured database, a graph database, and a vector database. Malcolm asks them to decide how to store a single sentence and who will hold the authoritative version. They must remain seated and whisper; speaking loudly carries a fictional penalty of five times the tokens. She gives them the sentence about a cow jumping over the moon and concludes that the arrangement does not work. This is an analogy for communication and ownership costs, rather than a test of database interoperability or an actual token-cost measurement.

12:4512:48
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

12:45 · section reference included

Keep multiple memory representations together

Selected presentation frame from No Memory, No Harness: Why the Database Is the Last Line of Defense — Kay Malcolm, Oracle at 993 seconds
Keep multiple memory representations together

Malcolm’s proposed answer is Oracle AI Database. She says Oracle can natively support JSON, graph, vector, and spatial data, describing storage together down to the same table and partition. She also names blockchain functionality for immutable memory. Her broader pitch emphasizes deployment choice across AWS, GCP, Azure, OCI, and on-premises environments. These are capability claims in the presentation; she does not demonstrate their configuration, performance, or immutability guarantees.

She then connects memory categories to storage representations. The broad proposal uses relational and JSON storage for retained context, graph representations for relationships and procedural steps, and vectors alongside text for episodic and semantic memory. The precise assignment of every memory category is not clear enough to establish a strict mapping. The useful architectural point is that different representations can serve different memory needs while living in one database. Her recommendation is to power the harness through that shared store, reducing the coordination burden she associates with four separate systems.

14:5915:06
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

14:59 · section reference included

A memory broker attaches context to code history

Selected presentation frame from No Memory, No Harness: Why the Database Is the Last Line of Defense — Kay Malcolm, Oracle at 1016 seconds
A memory broker attaches context to code history

Returning to her team, Malcolm describes a memory broker that preserves context alongside code and provides continuity. Procedural, episodic, and long-term information from one context window can be shared with other team members across forks. Developers retain control while the broker associates context with the relevant fork, branch, and commit. That association is the concrete mechanism in her example: the next collaborator receives context tied to the code history rather than an isolated recollection.

Malcolm calls this a simplified example before arguing that memory becomes essential in an enterprise harness. She cites an account of OpenAI’s in-house data agent in which memory helped it filter correctly instead of relying on string matching. She also attributes to Harrison Chase the view that control over the harness determines control over memory. These references support her emphasis on useful retained context and ownership, but she gives no implementation detail or experimental results from them.

She anticipates the question of using Claude’s existing memory and characterizes it as similar to filesystem memory: useful for one participant, but problematic when scaled beyond one in an enterprise. The concern is shared coordination. This passage does not explain a particular concurrency failure, access-control model, or conflict-resolution protocol, so it establishes her scaling concern without proving a universal limit on filesystem-based designs.

16:4716:49
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

16:47 · section reference included

The SDK, model choice, and paths to experimentation

Selected presentation frame from No Memory, No Harness: Why the Database Is the Last Line of Defense — Kay Malcolm, Oracle at 1136 seconds
The SDK, model choice, and paths to experimentation

Malcolm introduces Oracle’s agent memory package and SDK as the layer that holds live conversations, memories, and facts while deciding what is worth retaining. In her example, Kevin shares context through the memory broker using the Oracle agent memory SDK, with storage in an Oracle autonomous database. Linda can then work with that context. The described system combines context capture, retention, database persistence, and shared access; the talk does not specify the criteria used to decide what to keep.

The model remains a choice within this design. Malcolm says the team can use its preferred LLM or a local model through the Oracle private AI services container. She closes the technical argument by saying that shared memory makes teams faster, while also emphasizing choices between filesystem and database storage and between JSON and relational modeling. The example supplies an architecture for continuity, but no measured team-speed improvement, retrieval benchmark, or reconciliation-error comparison.

Her closing resources include the Oracle AI developer hub for coding materials and applications, and LiveLabs for hands-on workshops. She says she wrote LiveLabs about six years earlier and reports 40 million users. She invites attendees to experiment with Oracle technology using her OCI tenancy resources, mentioning sessions of six or 12 hours. This gives the architectural pitch a practical next step: try the technology in a workshop environment.

After joking about giving everyone a Mac Mini, Malcolm points to OCI Always Free. She describes an offering with a free Oracle database, free compute, 3,000 emails per month, and 200 gigabytes of storage. Those quantities are the offering she presents in the recording, without detailed eligibility or service conditions. She ends by asking attendees to tell her what they build, thanks the audience, and the recording closes with music.

18:4618:50
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

18:46 · section reference included

Read the complete timestamped transcript
  1. 0:12

    Everyone, are we having fun?

  2. 0:15

    >> Oh, you've got to give me way more than

  3. 0:18

    that. So, let me tell you, um, my name

  4. 0:20

    is Kay Malcolm. I am a retired hiphop

  5. 0:23

    instructor. So, if I don't get more

  6. 0:25

    energy than that, we will start. We'll

  7. 0:28

    start. Are you having fun? [cheering]

  8. 0:32

    >> Okay. All right. So, here's what we're

  9. 0:34

    going to talk about today. Now, you guys

  10. 0:36

    have heard a lot about two letters. Does

  11. 0:39

    anyone want to guess what those two

  12. 0:41

    letters are that I'm going to talk about

  13. 0:42

    today?

  14. 0:46

    >> Data. That was pretty good. DB. I'm

  15. 0:48

    going to talk about AI, but I'm

  16. 0:50

    specifically going to talk about agent

  17. 0:53

    harnesses. But before I do that, I want

  18. 0:56

    to introduce you all to a few people. Is

  19. 0:57

    that okay?

  20. 0:59

    Yes or yes. Is that okay?

  21. 1:02

    >> I gave choices. Yes. Anyway. All right.

  22. 1:05

    Okay. All right. This is my team.

  23. 1:09

    I run an outbound database product

  24. 1:12

    management team at Oracle. I've been at

  25. 1:14

    Oracle a really long time, 20 years.

  26. 1:18

    Funny story, I started when I was 12.

  27. 1:20

    So, don't do the math and don't start

  28. 1:22

    start adding in your head. Um, and we've

  29. 1:25

    got a problem. That problem is I've got

  30. 1:29

    one group

  31. 1:31

    that does platform development and then

  32. 1:34

    I have another group that does content

  33. 1:36

    development for live labs, a platform

  34. 1:38

    that I wrote myself. So yeah, I'm an

  35. 1:41

    engineer but I'm kind of a developer

  36. 1:43

    poser too. And then I've got another

  37. 1:45

    group who does QA

  38. 1:48

    and then I have another group who does

  39. 1:49

    my front-end development

  40. 1:52

    with AI. Here's what I found out as a

  41. 1:56

    leader. Because in the token maxing era

  42. 2:00

    of 2025, because you know, we're not

  43. 2:02

    token maxing anymore, right?

  44. 2:05

    We are responsible AI now. But in the

  45. 2:08

    token maxing era, the thing that I found

  46. 2:10

    out was while AI was making the

  47. 2:14

    individuals on my team faster, there was

  48. 2:18

    another problem it was creating.

  49. 2:23

    It wasn't making my team more

  50. 2:26

    productive.

  51. 2:28

    And the reason was when one team from

  52. 2:32

    the Netherlands checked in code at my

  53. 2:35

    4:00 a.m. in the morning because I've

  54. 2:37

    got half of my team that's in AMIA and I

  55. 2:39

    have half of my team who that are here

  56. 2:41

    in the United States. They checked in

  57. 2:44

    the code but they didn't check in their

  58. 2:47

    context from Codeex. We use Codeex at

  59. 2:50

    Oracle.

  60. 2:51

    So then when the US team woke up,

  61. 2:56

    they got the code but no information

  62. 2:59

    about the context. So we used AI to

  63. 3:03

    solve a problem that AI created. And

  64. 3:07

    here's what we did. Oh well, let me talk

  65. 3:09

    about this first. So some of the issues,

  66. 3:12

    the context, like I said, wasn't shared.

  67. 3:15

    GitHub wasn't tracking that. I had

  68. 3:19

    repositories that were diverging and I

  69. 3:21

    was asking the managers who work for me,

  70. 3:24

    what's happening to your teams? Why why

  71. 3:27

    are we not going faster? We're spending

  72. 3:30

    all of this money on tokens. We're

  73. 3:31

    spending all this money on AI, yet

  74. 3:33

    something is missing because we're still

  75. 3:36

    spending time doing testing and

  76. 3:39

    validation. So our netn net wasn't

  77. 3:41

    really wasn't really working for us

  78. 3:45

    because git records the code and not

  79. 3:47

    human intent.

  80. 3:49

    So it's a problem

  81. 3:52

    and

  82. 3:53

    even though code creation

  83. 3:58

    was no longer our problem

  84. 4:00

    still had a bottleneck.

  85. 4:03

    We needed a collaboration layer. Now, I

  86. 4:07

    do have members of my team in the

  87. 4:09

    audience, so don't judge me, and you

  88. 4:12

    know who you are. I'm not saying that

  89. 4:14

    you all didn't collaborate. But now,

  90. 4:18

    we've got a new team member, and that

  91. 4:20

    new team member is AI.

  92. 4:23

    So,

  93. 4:25

    we needed to figure out how to track our

  94. 4:27

    progress in our next steps. how to

  95. 4:31

    rationalize decisions

  96. 4:33

    that the

  97. 4:36

    agent was making.

  98. 4:39

    We needed to figure out how to resolve

  99. 4:43

    questions in conflicts.

  100. 4:45

    Okay,

  101. 4:48

    hold my problem. Will you all hold my

  102. 4:50

    problem for me right here? We're going

  103. 4:51

    to just tuck that in a little box. Let

  104. 4:54

    me define what a enterprise agent

  105. 4:58

    actually is. Now, most people think that

  106. 5:00

    an enterprise agent is the model and

  107. 5:04

    workflow. How many people agree with me?

  108. 5:08

    Man, this tough crowd you. Okay, one

  109. 5:11

    person. Okay, the rest of you think it's

  110. 5:14

    a little bit more. Okay, let's see what

  111. 5:18

    could it be that a real enterprise agent

  112. 5:24

    has tools.

  113. 5:26

    Tools are how it does things.

  114. 5:30

    Context.

  115. 5:33

    The context. That's a context window.

  116. 5:35

    That's what's in the actual prompt.

  117. 5:39

    Memory.

  118. 5:40

    Huh?

  119. 5:43

    And if you're thinking, "But wait, K,

  120. 5:46

    memory, you just said that the model is

  121. 5:48

    kind of like the brain of the

  122. 5:50

    operation." Hold tight. We're going to

  123. 5:52

    talk a little bit more about memory

  124. 5:56

    retrieval because you don't want to get

  125. 5:58

    everything back. So that's being able to

  126. 6:00

    to retrieve the right information back.

  127. 6:04

    And then I know that there are a lot of

  128. 6:06

    developers here and you all don't care

  129. 6:08

    about security.

  130. 6:11

    I care about security because I work for

  131. 6:14

    the most secure database company and I

  132. 6:17

    used to work for um agency that has no

  133. 6:21

    name. But guard rails is also important.

  134. 6:25

    This is the harness. I speak in

  135. 6:28

    analogies and I and I speak in stories

  136. 6:31

    because if I tell you this and Marvel,

  137. 6:35

    you know exactly what I'm talking about.

  138. 6:38

    So the agent, think of it as the model,

  139. 6:42

    little brain floating a in a glass jar

  140. 6:46

    plus this harness. This harness is the

  141. 6:50

    body.

  142. 6:52

    So it's how the agent can actually do

  143. 6:55

    things and get things done. That memory,

  144. 7:00

    that's the part of the central nervous

  145. 7:03

    system. And you remember the central

  146. 7:04

    nervous system connects the brain to the

  147. 7:07

    rest of the body, legs, arms. That's the

  148. 7:11

    part of the central nervous system that

  149. 7:14

    carries context. So you remember my

  150. 7:17

    problem with Git.

  151. 7:20

    What I needed was memory. Okay, so there

  152. 7:24

    are a number of memory types. I chose

  153. 7:27

    five, the five most common ones that

  154. 7:29

    people talk about and these are the ones

  155. 7:30

    that I want you to remember. The first

  156. 7:32

    one is short-term memory. That's the

  157. 7:34

    session, right? And so if you're storing

  158. 7:38

    memory of an AI uh process, that is the

  159. 7:42

    short-term memory is if you're with

  160. 7:45

    chat, cloud code, right? Codeex, pick

  161. 7:48

    your poison. The long-term memory is

  162. 7:51

    what persists across sessions.

  163. 7:55

    Episodic memory. Hm.

  164. 7:58

    What happened the last time

  165. 8:03

    I interacted with fill in the blank?

  166. 8:06

    That's your episodic memory. Procedural

  167. 8:09

    memory

  168. 8:11

    tools, steps that were taken.

  169. 8:15

    And then finally, semantic memory. And

  170. 8:18

    semantic memory because we're talking

  171. 8:19

    enterprise agents. We're not talking the

  172. 8:23

    agent that I built, Sasha Fierce,

  173. 8:25

    because remember I told you guys that I

  174. 8:26

    was a I'm a a dancer. So, of course, my

  175. 8:30

    my chief of staff is going to be called

  176. 8:32

    Sasha Fierce because that was Beyonce.

  177. 8:34

    Any Beyonce fans?

  178. 8:37

    Okay, I'm sorry. All right, we got to

  179. 8:39

    focus. Okay, so these are the memory

  180. 8:42

    types. Now, when you're defining this

  181. 8:45

    real enterprise agent in this memory,

  182. 8:50

    there's something you need to consider

  183. 8:51

    where to store it. And so, I'm going to

  184. 8:53

    tell you guys a story. But when I tell

  185. 8:56

    you the story, you have to promise me

  186. 8:58

    that you're not going to judge me. Do

  187. 9:00

    you promise?

  188. 9:06

    Do you promise

  189. 9:08

    >> you're not recording me, right? Because

  190. 9:10

    this doesn't paint me in a good light.

  191. 9:12

    Okay. All right. The world of data was

  192. 9:14

    one simple. I've been at Oracle a long

  193. 9:16

    time, but I came from a customer. That

  194. 9:18

    customer's name was Southern Company. It

  195. 9:19

    was a power company. I'm based out of

  196. 9:21

    Atlanta. And I was hired at Southern

  197. 9:24

    Company because I was a rockar

  198. 9:27

    performance tuner. You had a SQL query.

  199. 9:29

    I mean, I'm dating myself, but whatever.

  200. 9:31

    You had a SQL query. I knew all of the

  201. 9:33

    innit.org parameters. Even the ones when

  202. 9:35

    you called support and they said, "Don't

  203. 9:37

    remember these. Don't write them down."

  204. 9:38

    I wrote them down in my little notebook.

  205. 9:40

    I could tune a query within one inch of

  206. 9:42

    its life. Then one of you came to my

  207. 9:47

    desk because I mean the world the world

  208. 9:49

    was rows and columns. It was a great

  209. 9:51

    time back in my Albundy days um and said

  210. 9:56

    hey I need to store data unstructured.

  211. 10:01

    Why I need to do that?

  212. 10:04

    And so me being K the the diligent DBA,

  213. 10:08

    I was like, "Let me figure it out and

  214. 10:11

    get back to you."

  215. 10:14

    Did I get back to him?

  216. 10:16

    I didn't get back to him. Now, the thing

  217. 10:19

    you have to know about Southern Company

  218. 10:21

    was for every database system that a DBA

  219. 10:24

    managed, I had to attend two meetings.

  220. 10:26

    Today, when I hear Sarbain Oxley, I

  221. 10:29

    still throw up a little bit in the back

  222. 10:30

    of my throat. So I had to attend a

  223. 10:32

    security meeting and a patching meeting

  224. 10:34

    every week. Never failed. Now because

  225. 10:38

    this developer installed a database that

  226. 10:42

    was specialized for unstructured. Okay,

  227. 10:45

    there are really smart people in the

  228. 10:46

    room. How many meetings am I going to

  229. 10:48

    now?

  230. 10:54

    Four. Okay, I'm a little annoyed, but

  231. 10:56

    I'm like, okay, we can we can we can do

  232. 10:59

    this. Then they said, "Okay, since

  233. 11:01

    you're such a good tuner,

  234. 11:03

    I need you to figure out this

  235. 11:05

    relationship." Now, the way that

  236. 11:07

    Southern Company worked, there was this

  237. 11:09

    people could die application, um, and it

  238. 11:12

    was a it was like a Nokia phone that

  239. 11:16

    people who were climbing the towers,

  240. 11:18

    right? So, you guys have have been in a

  241. 11:20

    storm and the power goes out, right? And

  242. 11:23

    then you're pretty sure that within

  243. 11:25

    maybe an hour or two the power will go

  244. 11:27

    on. Well, that system that would tell

  245. 11:31

    the people who were climbing those trees

  246. 11:32

    and risking their lives to turn the

  247. 11:34

    power back on sometimes would have false

  248. 11:37

    positives or false negatives. So, they

  249. 11:39

    wanted to look at all of the other um uh

  250. 11:44

    polls in the area

  251. 11:46

    to try to get away from the false

  252. 11:48

    positive or the false negative. And so I

  253. 11:50

    did that in a SQL query and it was it

  254. 11:53

    was amazing. It was a five nested union

  255. 11:57

    all statement. It was some of my best

  256. 11:59

    work. Now it might have taken like 20

  257. 12:01

    minutes to work but it was like a

  258. 12:03

    predecessor to graph.

  259. 12:06

    Yeah, they they install Neo4j.

  260. 12:10

    So now how many meetings am I going to?

  261. 12:13

    Six. That's a problem.

  262. 12:17

    So I um Oh, let me I got ahead of

  263. 12:19

    myself. So you know what I did? I quit.

  264. 12:23

    I left and I came to Oracle because I

  265. 12:24

    was like this is a problem and maybe I

  266. 12:26

    can go to Oracle to help solve it. So

  267. 12:27

    then Joe Mundy called me and he said hey

  268. 12:30

    um we are installing Reddus. Oracle is

  269. 12:34

    late to the game. We've got a vector

  270. 12:36

    database.

  271. 12:38

    Okay.

  272. 12:40

    But here's your problem, Joe.

  273. 12:45

    Agents now need access to all of this

  274. 12:48

    data. So if data is in an Oracle

  275. 12:51

    database, if then it's also in an

  276. 12:53

    unstructured JSON database, if it's in a

  277. 12:55

    graph database and it's in a vector

  278. 12:58

    database, where is your single source of

  279. 13:01

    the truth?

  280. 13:03

    The agent has to figure that out.

  281. 13:05

    Sometimes it'll get it right.

  282. 13:08

    Most times it'll get it wrong and it's

  283. 13:10

    going to burn up a whole bunch of

  284. 13:11

    tokens. And so now if you want to store

  285. 13:15

    your memory somewhere, you can store it

  286. 13:17

    in a file system.

  287. 13:20

    You can store it in

  288. 13:23

    clawed or chatgpt because we all know

  289. 13:25

    about the memory.md file.

  290. 13:29

    But that's going to be a problem. Now I

  291. 13:31

    want to illustrate this. I need four

  292. 13:32

    volunteers. I can see you raise your

  293. 13:34

    hand. One, two. Okay, I can't. Maybe I

  294. 13:38

    can. Three.

  295. 13:40

    I need a fourth. Ah, fourth in the back.

  296. 13:43

    Okay. Fourth in the back. You are going

  297. 13:45

    to be our old reliable. You're going to

  298. 13:47

    be a relational database. Yes or yes.

  299. 13:50

    You got your So, you have your

  300. 13:51

    assignment. Okay. And then there was

  301. 13:53

    someone here. You're going to be my

  302. 13:56

    unstructured database. Okay. And then

  303. 13:58

    where was my other? Ah, very good.

  304. 14:00

    You're going to be my graph database.

  305. 14:02

    You good? Relationship guy. You look

  306. 14:04

    like a relationship guy. All right. Very

  307. 14:06

    good. Fourth. Where was my fourth?

  308. 14:09

    Was it you? Yes. Yeah. You are my vector

  309. 14:14

    database. Okay. Now, everybody be

  310. 14:18

    really, really quiet.

  311. 14:20

    For my four volunteers, I need you all.

  312. 14:24

    I'm going to say something to you. And I

  313. 14:28

    need you all to decide how you're going

  314. 14:30

    to store it and who's going to have the

  315. 14:32

    single source of the truth. You can't

  316. 14:34

    get up from your seats and you have to

  317. 14:36

    whisper because if you talk loud that's

  318. 14:38

    5x the tokens for you. Yes.

  319. 14:41

    Okay. Are we ready? All right.

  320. 14:44

    The cow jumped over the moon.

  321. 14:49

    Go.

  322. 14:53

    Doesn't really work, does it? That's a

  323. 14:56

    problem. Okay,

  324. 14:59

    Oracle. And if you don't forget one, if

  325. 15:02

    you forget everything I say and you

  326. 15:04

    remember one thing,

  327. 15:06

    Oracle is not the Oracle that you think

  328. 15:09

    that is why I am here today. How many of

  329. 15:12

    you knew that Oracle could natively in

  330. 15:16

    the same table down to the same

  331. 15:18

    partition store JSON graph vector my

  332. 15:23

    vector friend over there my JSON friend

  333. 15:26

    spatial

  334. 15:28

    you want your memory to be immutable

  335. 15:30

    blockchain in the same database raise

  336. 15:33

    your hand yeah

  337. 15:36

    we have a marketing problem

  338. 15:39

    so any data type can be stored in a 26AI

  339. 15:44

    database any workload anywhere AWS GCP

  340. 15:49

    Azure OCI on prem choice and flexibility

  341. 15:54

    so now when we take this and we talk

  342. 15:56

    about the agent I want to be able to

  343. 15:58

    store my long-term and procedural memory

  344. 16:00

    in relational on in JSON I want to store

  345. 16:03

    my short-term and my long-term memory

  346. 16:05

    graph I want to store procedural because

  347. 16:07

    procedural that's how I figure out the

  348. 16:09

    relationships right the steps

  349. 16:11

    my episodic and semantic memory. I need

  350. 16:14

    to do some vector and then store it also

  351. 16:17

    as text. Now, if I have four different

  352. 16:22

    databases, you all saw they can't talk

  353. 16:24

    to each other. It's going to be a

  354. 16:26

    problem. And so, what I'm saying to you

  355. 16:29

    today is the Oracle AI database is the

  356. 16:33

    best place to store this agent memory

  357. 16:36

    that's going to power your harness.

  358. 16:38

    Remember your harness is your body

  359. 16:40

    [music] and that memory is your central

  360. 16:42

    nervous system. Okay, back to PY. So the

  361. 16:47

    problem that I had, we solved it with a

  362. 16:49

    memory broker named Py. We used agent

  363. 16:53

    memory. We got out of that automatic

  364. 16:56

    continuity.

  365. 16:58

    So with my team, they were able to share

  366. 17:01

    not just their code, but PY also kept

  367. 17:05

    track of the context. So if one context

  368. 17:09

    window was had procedural memory,

  369. 17:12

    episodic memory, information about the

  370. 17:14

    long-term memory, that was then shared

  371. 17:17

    with the other folks on the team. You

  372. 17:20

    could call them agents, if you will.

  373. 17:21

    They're just human agents shared across

  374. 17:24

    forks.

  375. 17:26

    The developers on the team remained in

  376. 17:28

    control while Polly was able to create

  377. 17:34

    the context, figure out which fork and

  378. 17:37

    branch it belonged to and which commit

  379. 17:40

    it belonged to. Now this is a very

  380. 17:42

    simplistic example but when you take

  381. 17:45

    this to the enterprise here's what

  382. 17:47

    happens.

  383. 17:49

    Memory is the thing that becomes

  384. 17:51

    non-negotiable in an agent's harness.

  385. 17:54

    Now these are three papers that that I

  386. 17:56

    read um on the airplane. This first one

  387. 18:00

    is from open AI and it's about its

  388. 18:01

    in-house data agent and the thing that

  389. 18:03

    it says is it is saying that its

  390. 18:07

    in-house data agent actually needs

  391. 18:10

    memory. Memory was crucially important

  392. 18:13

    to ensure that its agent was able to

  393. 18:16

    filter correctly instead of trying to

  394. 18:18

    string match.

  395. 18:20

    Harrison Chase said, "Your harness, your

  396. 18:23

    memory. And if you don't own your

  397. 18:24

    harness, you don't own your memory."

  398. 18:26

    Which is key. And then I'm sure you all

  399. 18:29

    are wondering, "Well, Claude has memory.

  400. 18:31

    Why can't I use that?" Well, it's kind

  401. 18:32

    of like file system memory and it works

  402. 18:35

    with one, but just like in my example,

  403. 18:38

    when you scale past one, and you're

  404. 18:41

    going to scale past one in the

  405. 18:43

    enterprise, it creates a problem. So

  406. 18:46

    Oracle has a Oracle agent memory pap

  407. 18:50

    package. PIP install Oracle agent

  408. 18:53

    memory. You get access to it. And this

  409. 18:56

    memory is this SDK that we have is the

  410. 19:01

    thing that will hold your live

  411. 19:02

    conversations, your memories, your facts

  412. 19:05

    and figure out what is worth keeping. So

  413. 19:08

    if we look at Py now, Kevin

  414. 19:12

    can share his context with Py, our

  415. 19:15

    memory broker. We use the Oracle agent

  416. 19:17

    memory SDK. It's stored in an Oracle

  417. 19:20

    autonomous database.

  418. 19:23

    We can use the LLM of our choice or we

  419. 19:25

    can use a local model through the Oracle

  420. 19:27

    private AI services container.

  421. 19:31

    And then Linda, who's actually sitting

  422. 19:33

    right here, can interact and work with

  423. 19:36

    Kevin, no issues.

  424. 19:38

    So yes, AI makes individuals faster.

  425. 19:42

    Shared memory on an Oracle AI database

  426. 19:44

    makes teams faster. So I don't want you

  427. 19:47

    all to compromise. In the age of AI,

  428. 19:50

    what 26AI does is you can choose

  429. 19:55

    and pick what's best for agent memory

  430. 19:58

    file system stored in a database file

  431. 20:00

    system or in the database. If you need

  432. 20:03

    to do data modeling, you've got JSON,

  433. 20:05

    you've got relational. We've got choice.

  434. 20:10

    Okay, I've got some goodies for you. The

  435. 20:12

    Oracle AI developer hub. That's where

  436. 20:15

    you can guys you guys can get coding

  437. 20:16

    materials, the applications, what I

  438. 20:18

    talked about today. Livelabs.oracle.com.

  439. 20:21

    If you've done any of our workshops

  440. 20:23

    today, that happens to be something that

  441. 20:25

    I wrote myself about six years ago and

  442. 20:27

    40 million users um ago. Spend my OCI

  443. 20:31

    tenency money.

  444. 20:33

    kick the tires on any Oracle technology

  445. 20:36

    um for six hours, 12 hours, however long

  446. 20:39

    you need. Um and then I'm giving you all

  447. 20:42

    all a Mac Mini. No, I'm just kidding.

  448. 20:45

    I'm giving you an OCI Mini. So, I don't

  449. 20:47

    know if you knew, but there is an always

  450. 20:49

    free OCI. It is the most generous of any

  451. 20:52

    of the hyperscalers where you can get a

  452. 20:54

    free Oracle database, free compute, you

  453. 20:57

    can send 3,000 emails a month, 200 gig

  454. 21:00

    in storage, and if you click on that,

  455. 21:03

    you can get access to it. Or just search

  456. 21:06

    Google for Oracle Cloud, always free.

  457. 21:10

    Connect with me. If you build something,

  458. 21:13

    will you all message me and let me know?

  459. 21:15

    Yes or yes?

  460. 21:18

    >> Thank you.

  461. 21:34

    >> [music]