No Memory, No Harness: Why the Database Is the Last Line of Defense — Kay Malcolm, Oracle
Oracle’s team used a shared memory broker to carry agent context across people and sessions. The useful pattern is durable, queryable team memory; the database choice is vendor-framed.
Oracle’s distributed team found that code crossed time zones without the reasoning that produced it. Its Py memory broker uses the **Oracle Agent Memory SDK** and an autonomous database to share conversations and retained context across team members.
For team coding agents, persist more than final diffs: retain selected facts, decisions and procedures with retrieval suited to the task. Distinguish **five memory types**—short-term, long-term, episodic, procedural and semantic—rather than treating every transcript as one undifferentiated store.
Oracle’s distributed team found that code crossed time zones without the reasoning that produced it. Its Py memory broker uses the **Oracle Agent Memory SDK** and an autonomous database to share conversations and retained context across team members. For team coding agents, persist more than final diffs: retain selected facts, decisions and procedures with retrieval suited to the task. Distinguish **five memory types**—short-term, long-term, episodic, procedural and semantic—rather than treating every transcript as one undifferentiated store. The talk argues for placing relational, JSON, graph, vector and text data in one **26AI database**, but it presents no comparative evaluation against filesystem memory or separate stores. Retention policy, access control, retrieval quality and deletion behavior remain unspecified.
This reframes team memory as shared infrastructure and usefully separates five kinds of retained context, but the candidates expose the missing operating policy. A unified database does not by itself decide what deserves retention, suppress harmful combinations, survive model migrations or satisfy access and deletion requirements. The durable contribution is the memory taxonomy and cross-team continuity problem, not evidence that one storage architecture solves them.