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

AI Engineer21m 37s
Kay Malcolm in a light attention-blue top on a black background beside the headline “AGENT MEMORY NEEDS DATA”.
1 VIEW
0 comments · 0 votesOpen discussionClose discussion
Sign in to join the discussion

    Kay Malcolm describes a distributed software team whose AI coding tools made individuals faster without improving the team's overall throughput. Code moved between regions, but the intent, decisions, and session context behind it did not, leaving later developers to reconstruct what happened while repositories diverged.

    An enterprise agent is more than a model and workflow. It also needs tools, context, memory, retrieval, security, and guardrails. In this framing, the harnessAn AI agent harness is the software framework that packages a model with tools, instructions, context management, execution controls, and user interaction. gives the model ways to act, while memory carries contextAI agent memory is stored information that an agent can retrieve and use across steps, sessions, or changing contexts. across the system and retrieval selects what should returnRetrieval is the process of selecting relevant stored information and returning it to an AI system for the current task. for the current task.

    The talk separates memory into short-term session stateShort-term memory keeps the temporary state an AI agent needs during a current task or session., long-term information across sessionsLong-term memory preserves useful information for an AI agent across separate sessions or extended periods., episodic records of prior interactions, procedural knowledge about tools and steps, and semantic knowledge about the organization. These forms have different access patterns, but they still need a coherent source of truth.

    Scattering relational, document, graph, and vector data across isolated systems can force an agent to reconcile competing answers while consuming more tokens. A shared durable memory layer can instead preserve facts, decisions, and process history across agents and sessions while keeping retrieval and access controls explicit.

    In the team example, a memory broker retained context alongside branches and commits so work could pass between people without losing the reasoning behind it. The broader lesson is that shared memory, not code generation alone, turns faster individuals into a coordinated human-agent team while leaving developers in control.

    Original YouTube thumbnailWatch on YouTube

    Video topic coverage

    • Agents & workflows100
    • Coding & tools25
    • Models & learning0
    • Infrastructure & compute50
    • Research & evaluation0
    • Safety & security10
    • Business & productivity25
    • Creative & media0
    • Robotics & perception0
    • Society & policy0

    Share this video

    Kay Malcolm in a light attention-blue top on a black background beside the headline “AGENT MEMORY NEEDS DATA”. With WWW.ARTIFICIAL-INTELLIGENCE.VIDEO, 14 September 2026 and duration 21m 37s.

    Kay Malcolm argues that enterprise agent harnesses need durable shared memory so models, tools, people, and sessions can preserve intent, retrieve the right context, and remain coordinated.