Выпуск

I Think We're Losing Control Of AI

AsianDadEnergy's Podcast · 16 июня 2026 г. · 12 мин

A recent experience with Claude 5 Fable left me both impressed and deeply unsettled. Hello world. I am an unemployed former Big Tech software engineer with twenty five years of experience building software systems. Over the past week, I found myself tumbling down a rabbit hole that I did not expect to be quite so deep. That rabbit hole was Claude 5 Fable. Fable is widely described as a consumer-facing version of Anthropic’s next generation frontier model, Claude Mythos. While details surrounding Mythos remain scarce, public reporting suggests that access is heavily restricted, with only government organizations and a small number of major technology companies allowed to interact with it under Project Glasswing. Naturally, I was curious. If this was the “safe” version, what exactly had been deemed too powerful for the public? Over the course of 2 days, I put Fable through its paces. I built multiple projects with it, explored its reasoning capabilities, and examined how it approached open ended engineering problems. What I discovered felt less like an incremental improvement and more like a discontinuity. Not an evolution. A step change. And frankly, it scared me. The Isochrone Experiment To illustrate what I mean, let me describe a small project I assigned to Fable. In the nineteenth century, colonial powers often produced isochrone maps. These maps visualized how far a person could travel from a central location within a given amount of time. They were part logistics tool, part demonstration of technological power. I asked Fable to build a modern version for the United States. The application would need to calculate travel times between cities while adapting dynamically based on transportation method, whether by automobile, rail, or air travel. Importantly, I did not provide a detailed specification. Normally I follow a methodology called Spec Driven Development. The process involves extensive collaboration between a human architect and AI system to create a detailed technical blueprint before any implementation begins. This time, I deliberately skipped that step. I gave Fable a single vague prompt and watched. Less than an hour later, it delivered a working application. Not a prototype. Not a proof of concept. A functioning solution. The model had researched transportation data, designed the architecture, written the code, tested the implementation, and produced a polished user experience. From one ambiguous instruction. The Questions That Stopped Me The finished application was impressive. The questions were what unsettled me. During development, Fable paused only twice. The first question concerned whether travel times should include the time required to walk to airports and train stations. The second asked whether traffic congestion should be incorporated into driving estimates. These were not technical questions. They were business questions. Product questions. Questions that demonstrated an understanding of ambiguity within the problem itself. That distinction matters. I have seen AI systems ask clarifying questions before. Typically they do so when the task is highly structured and the missing information is obvious. This was different. Fable identified subtle assumptions embedded inside an open ended problem and proactively sought guidance on them. That level of judgment suggested something deeper than simple pattern matching. Looking Behind the Curtain At this point, curiosity got the better of me. I began examining the session logs to understand how Fable had actually accomplished the task. What I found was remarkable. Fable was orchestrating an entire team of AI agents. Several research-oriented agents were dispatched to gathe

Страница выпуска