← All speakers

Cornelia Davis is a principal technologist at Temporal, former chief technology officer of Weaveworks, and author of Cloud Native Patterns. She applies decades of experience in distributed systems to a central problem in AI engineering: keeping autonomous applications running when workers crash, networks fail, external services stall, or human approval takes days.

Davis earned computer science degrees at California State University, Northridge, and studied at Indiana University. She developed imaging systems at Hughes Aircraft, worked on web-based collaboration at eRoom Technology, and moved through Documentum into EMC’s corporate technology organization. After building Cloud Foundry service brokers and an early BOSH release, she joined the Cloud Foundry team in 2013 and later held platform-engineering and transformation leadership roles at Pivotal.

Her 2019 book, Cloud Native Patterns, distilled that experience into principles for change-tolerant software, including service discovery, retries, resilient routing, and independent deployments. As Weaveworks chief technology officer, she advanced GitOps and cloud-native operations, emphasizing repeatable infrastructure management and automated reconciliation across the Kubernetes ecosystem.

At Amazon Alexa, Davis led Structured Knowledge Skills, giving enterprise customers natural-language access to structured data through knowledge graphs and question-answering. She subsequently worked as a technology fellow and vice president of product at Spectro Cloud, focusing on Kubernetes management, edge deployment, and intermittent connectivity. At Temporal, she brings those platform, conversational-AI, and infrastructure disciplines together in work on production-ready agent systems.

  • Durable execution for AI agents: Davis uses workflows, activities, queues, and event-sourced execution to preserve completed model calls, tool results, and application state across failures. Her OpenAI Agents SDK demonstration shows a crashed worker resuming a multistep weather-query workflow without repeating successful inference. The integration exposes Temporal activities as agent tools through activity_as_tool.
  • Long-running human-in-the-loop workflows: Davis distinguishes a business process’s logical lifetime from any individual server process. Approvals can wait hours or days without keeping workers alive, then resume from recorded state. She also stresses idempotent activities because a retried external operation might already have succeeded before its response was lost.
  • Durable MCP Tasks: Her asynchronous Model Context Protocol implementation tracks purchase orders, ERP invoice processing, human approvals, and concurrent tasks across disconnected clients or servers. She favors explicit task updates and persisted client-side identifiers over stateful task discovery and long-lived response channels. At larger scale, she argues that targeted notifications can avoid polling every outstanding task.
  • Composable micro-agents: Davis applies microservices thinking to narrowly scoped agents orchestrated through code, parallel execution, or framework handoffs. She distinguishes separate agentic loops from handoffs that change the context within an existing loop—a practical difference when designing recovery, ownership, and state management.

Read the topics behind these talks

2 conference talks

Key ideas

Scroll to read ↓

A weather agent makes the durability problem concrete: Temporal preserves execution across worker failures, while the OpenAI Agents SDK supplies the agent loop.

  • Who controls the next step?
    1:28 ↗
  • Put execution history outside the process
    7:37 ↗
  • Activities do work; workflows coordinate it
    12:30 ↗
  • Build the loop explicitly
    20:05 ↗
  • Keep tool dispatch separate from the loop
    28:22 ↗
  • Ask for weather, then kill the worker
    35:46 ↗
  • Recovery still needs safe side effects
    42:23 ↗
  • Replace the manual loop with the Agents SDK
    45:16 ↗
  • Run the same failure test, then wait for a human
    55:07 ↗
  • Separate runs and handoffs have different boundaries
    1:00:35 ↗
  • Where the examples lead next
    1:06:03 ↗
  • Persistence, stopping, and operational ownership
    1:10:27 ↗
  • What the available examples do—and do not—cover
    1:15:26 ↗

Key ideas

Scroll to read ↓

A purchase-order workflow exposes the hard parts of asynchronous MCP: human approval, connection recovery, durable task handles, and the limits of polling.

  • Why isn’t an asynchronous tool enough?
    0:18 ↗
  • An invoice that cannot finish in one request
    2:23 ↗
  • Start the work, signal it later, preserve it through failure
    3:25 ↗
  • A submission survives the missing processes
    6:57 ↗
  • V1 separates lifecycle from result delivery
    11:12 ↗
  • Rediscovery and elicitation complicate recovery
    12:47 ↗
  • A stateless protocol with explicit input updates
    15:58 ↗
  • Stateless exchanges still need durable application state
    18:23 ↗
  • Multiple approvals expose the client workflow
    19:49 ↗
  • From a working client to efficient task tracking
    21:47 ↗

References