David Boyne has spent the last few years turning a side project for cataloging events into Event Catalog — an open source documentation tool that is quietly reshaping how teams bring discoverability to distributed and event-driven architectures. In this conversation we work through what Event Catalog actually is, why he treats messages, queries, commands, events, and services as the real primitives, and why supporting OpenAPI, AsyncAPI, and GraphQL side-by-side matters more than picking a winner. David walks through how Domain-Driven Design pulled him toward Event Studio, why business stakeholders are increasingly the unexpected champions, and how he turned an unsponsored project into a sustainable open-core business with license keys rather than a hosted SaaS. We close on what events and rich semantics could mean for AI agents needing context, and what David needs most from the community right now.