▶ Watch ↗19:06
Conference affiliation: Director of AI Technical Product Marketing · Oracle · 2026
Wojtek Pluta is a director of technical product marketing at Oracle, where he helps developers build applications with Oracle AI Database. His work on agent memory addresses a specific problem: deciding which parts of a conversation should become instructions or information that an application can use again. A formatting preference, a customer record and an approval policy need different rules, even when they arrive through the same chat interface.
In 2022, Wojtek worked with Victor Martin, Bogdan Farca and Stuart Coggins on augmented- and virtual-reality experiences for a Raspberry Pi cluster. Their work formed part of a larger project led by Chris Bensen. The team connected interactive digital representations of the physical cluster to databases, streaming services and Kubernetes infrastructure; an iPad could become a window onto the installation’s operating data.
Wojtek also co-presented developer sessions on eSports analytics and machine-learning data extraction. His more recent writing examines how databases support AI applications that retain information across interactions. The central distinction is between preserving a conversation and deciding what the application should carry forward from it. A log records what someone said; memory requires decisions about what that statement means, whom it concerns and when it should be revised.
In his stateful AI architecture guide, Wojtek distinguishes policies, preferences, facts, completed experiences and execution traces. Each has different requirements for storage, retrieval and revision. A policy requires explicit authoring, a factual claim needs provenance, and a preference can follow a different acceptance rule. Before an observation becomes a reusable record, the application must classify it, establish who may use it and apply the appropriate verification. Each prompt is then assembled from selected records rather than an indefinitely growing transcript.
His mortgage-agent example makes the consequences concrete. An operator asks to see missing documents at the top of a brief. That preference survives a fresh session and applies to another applicant, while the document status still comes from the new applicant’s own file. A blanket instruction to approve applications is rejected. The example separates three things an agent might otherwise conflate: how the operator wants information presented, what is true of an individual case and who can change lending policy.
Wojtek’s collaborative tutorials explore different parts of this design problem:
▶ Watch ↗19:06
Loading more talks and highlights…