What Problem Does Air Testing Actually Solve? (Jason Earle)

AI Music, Stolen Songs, and the Problem Nobody Seems to Be Solving

AI companies have been accused of training music-generation models on copyrighted songs without permission. Lawsuits followed. Licensing deals emerged. The debate became about copyright and compensation. While investigating the issue, I found myself asking a different question: How did the music actually get into the training system? That question led me into datasets, metadata, YouTube links, and an under explored part of the public discussion—the pipeline between publicly available music and AI model training. In this episode, I explore why datasets are not the same as audio collections and why understanding how a system works is as important as deciding what should happen after the fact. This isn't an argument for or against AI companies or artists. It's an exploration of problem definition, assumptions, and why understanding the mechanism leads to better questions—and better solutions.

What Problem Does Air Testing Actually Solve? (Jason Earle)

Jason Earle left a career on Wall Street after discovering that mold in his childhood home may have contributed to years of allergies and asthma. He went on to perform thousands of building investigations and developed the Got Mold? Test Kit to make air sampling accessible and affordable. In this conversation, we explore: * What problem air sampling is intended to solve * The role of independent mold inspectors * The difference between testing, investigating, and remediation The discussion explores a recurring theme throughout this podcast: Before choosing a solution, it's worth asking what problem we're actually trying to solve.

Data Centers, AI in Space & How Narratives Shape Our Future

An exploration of how the questions we ask—and the models we build—can influence narratives that shape technology, investment, and public policy. A widely cited paper estimated the water footprint of AI models. The results spread rapidly through news stories, social media, and public debate. But what question was the researchers actually trying to answer? I explore the assumptions behind lifecycle water accounting and how assumptions are shaping conversations about AI, data centers, and proposals for space-based computing.

What Happens When We Put Principles on Walls?

Matthew McConaughey once asked a simple question: Why can't we put the Ten Commandments back in public schools? That seems reasonable. Many of the principles most people would agree with. That question led me somewhere unexpected. This episode isn't really about the Ten Commandments. It's about a broader pattern: Why do schools, companies, governments, and organizations put principles on walls? Mission statements. Core values. Slogans. Codes of conduct. The assumption seems to be that displaying principles changes behavior. Does it? Or are we confusing a principle with a mechanism? In this episode, I explore the difference between values and systems, why principles are often open to interpretation, and whether displaying them actually produces the outcomes people hope for. Before deciding what belongs on the wall, it may be worth asking: What problem are we trying to solve? And how would we know if the solution actually worked?

What Problem Does a State Believe It's Solving? Israel, Survival, and the Logic of the State

What if part of the Israel – Iran conflict is not about oil, politics, or ideology — rather about how states behave once survival and continuity become the organizing principle? In this episode, I explore the logic of the state: * why nations organize around preserving themselves * why some conflicts become inflexible * why support for opposing regional forces may be interpreted as existential threat rather than political disagreement. Using the American Indian analogy as a structural thought experiment, not a moral equivalence, we examine how states tend to think once continuity, territory, identity, and survival become central to decision making. This episode is not about taking sides. It's about asking better questions: What problem does the system believe it is solving? Solve the right problem.