← All speakers

Bio, Work & Ideas

Frank Coyle

Conference affiliation: Lecturer, UCALBerkeley / Founder AI/Edge · UC Berkeley · 2026

Frank Coyle, known as drC, is a University of California, Berkeley lecturer and founder of The AI Edge who teaches developers how to build AI agents that behave reliably. His approach combines neuroscience, decades of computer-science instruction, and symbolic knowledge representation to keep probabilistic systems within explicit operational boundaries.

From neuroscience to agentic AI

Coyle studied psychology at Fordham and neuropsychology at Emory before computational models of neurons and a PDP-8 computer drew him toward computer science. He earned a master’s degree at Georgia Tech in 1974 and a doctorate at Southern Methodist University in 1992.

He spent more than three decades teaching computer science at SMU, helped establish graduate programs in software engineering and cybersecurity, and developed coursework for an online computer-science master’s program with an AI specialization. He also taught at Morehouse College. After retiring from SMU in 2025, he began teaching generative AI at Berkeley. He also mentors learners through Columbia University’s Justice Through Code initiative and founded The AI Edge to teach practical AI development.

His public projects range from machine-learning tutorials to KnowledgeGraphs, a repository of code and data for building structured knowledge sources for language models. An earlier XQuery web service reflects his longstanding interest in programmable access to structured information.

  • Neurosymbolic guardrails for AI agents. Coyle combines language models with ontologies, knowledge graphs, and explicit domain rules that test whether proposed actions make sense. His approach to agent ontologies uses established vocabularies and standards such as Schema.org, RDFS, and OWL to catch duplicate refunds, distinguish customers from support representatives, and reject invalid order statuses. Pydantic validates data structures; ontology-based reasoning validates business meaning.
  • Application-owned tool execution. Models propose tool calls, but application code executes them. That boundary allows developers to inspect stop reasons, detect exhausted token budgets, validate actions, and route uncertain decisions to people before side effects occur. Coyle treats these production controls as foundational agent-engineering knowledge.
  • Specialized agents and disciplined context. He favors narrowly scoped agents, limited tool access, independent contexts, and compact summaries. These constraints reduce token costs, prevent irrelevant information from overwhelming the model, and help preserve independent judgment between collaborating agents.

Coyle’s teaching emphasizes building working systems, debugging failures, and recognizing engineering anti-patterns. His reflections on biological and artificial intelligence also return to his neuroscience roots, contrasting the diversity of biological neural systems with the relative uniformity of contemporary model architectures.

Talks by Frank Coyle

2 talks

Key ideas

Scroll to read ↓

Frank Coyle explains how formal domain models, graph-based inference, and validation can constrain probabilistic agents before their proposed actions produce costly or incorrect outcomes.

  • Ontologies give agents an explicit domain model of entities, properties, and relationships instead of relying entirely on probabilistic language generation. 3:49 ↗ 5:23 ↗
  • Top-down and bottom-up modeling are complementary approaches: experts can define core business concepts, while observed customer interactions can reveal additional entities and relationships. 5:23 ↗ 6:38 ↗ 8:03 ↗
  • RDFS and OWL add inference and constraints, enabling systems to derive classifications, follow transitive relationships, and reason about relationships that permit only one value. 9:18 ↗ 10:29 ↗ 11:53 ↗
  • Validate tool results inside the agent loop before accepting them; inconsistent outcomes can be returned to the model or escalated to a human. 14:39 ↗ 16:15 ↗
  • Type checking and business-rule checking solve different problems: Pydantic validates parameter structure, while ontologies can identify duplicate refunds, misdirected payouts, and invalid status values. 17:43 ↗ 18:59 ↗
  • Delay side effects and control iteration because agent loops can drift, run indefinitely, increase token costs, or commit incorrect changes before domain validation occurs. 13:13 ↗ 17:43 ↗

Key ideas

Scroll to read ↓

Frank Coyle uses certification scenarios to explore the practical work of agent engineering: controlling tool loops, scoping instructions, isolating context, and running unattended workloads.

  • Preparing for agentic work by making things
    0:15 ↗
  • The exam’s engineering map
    2:44 ↗
  • Six scenarios, recurring design decisions
    4:13 ↗
  • Loops are an old source of new capability
    6:06 ↗
  • Customer support: inspect why the model stopped
    7:51 ↗
  • Code generation: put instructions at the right scope
    11:12 ↗
  • Research agents: specialize the work and limit the context
    11:59 ↗
  • Developer productivity: fork, summarize, compact
    15:12 ↗
  • CI and batch work: match execution to who is waiting
    18:07 ↗
  • There’s no exam, only make
    19:13 ↗

References