# Odyssey Alive > AI automation consulting that understands how your business actually works. Francis Meetze combines 25 years of web development with cultural anthropology to build automations that work with your team's reality, not against it. ## About Odyssey Alive Odyssey Alive is an AI automation consulting business based in Oregon, USA, founded and run by Francis Meetze. ### The Approach Most automation projects fail because someone built a solution before understanding the problem. The Odyssey Alive approach is different: 1. **Observe first** - Shadow your team, watch how work actually flows, find the genius workarounds and the bottlenecks nobody mentions in meetings. 2. **Respect what exists** - That "inefficient" process exists for a reason. Teams develop their own language, shortcuts, and tribal knowledge. Build around what's working, not over it. 3. **Build to last** - No vendor lock-in, no mystery code. You own everything, and it works long after the project ends. ### Background Francis Meetze has been building websites since 1998 and running BridgeSense.com as a web development agency since 2006. A cultural anthropology background informs understanding of why teams communicate and work the way they do. The patterns that emerged after a decade of building: projects that failed weren't the technically complex ones; they were the ones where nobody bothered to understand how the client's team actually worked. ### Services **Custom AI Integration** (Available Now) - Discovery & Observation: Shadow your team, map workflows, find where automation actually helps - Custom Build: n8n workflows, API integrations, AI-powered processing - Training That Sticks: Your team learns why, not just how - Ongoing Support: Long-term relationships, not handoffs - Investment: $3,000-$12,000 typical projects **AI SaaS Products** (Coming 2026) - Real Estate Market Intelligence - Expired Listing Lead Generation - Client Communication Tools ### Contact Location: Oregon, USA (serves businesses nationwide via remote work) Booking: 30-minute discovery calls available Monday-Friday, 1-3 PM PST Email: francis@odysseyalive.com --- ## Focus Articles Focus is the blog exploring AI, organizational culture, and the tacit knowledge nobody writes down. ### How AI Hacks Humans **URL:** https://odysseyalive.com/focus/how-ai-hacks-humans **Published:** August 13, 2026 **Category:** AI Transformation **Tags:** ai, cybersecurity, social-engineering, phishing, OSINT, business-email-compromise **Purpose:** AI collapsed the cost of personalized phishing from a specialized craft to a commodity. This article uses an illustrative scenario to show how constant platform churn gives attackers free cover, and why the URL is the one thing they still cannot fake. **FAQ:** - **How much does AI-powered phishing cost compared to traditional methods?** AI performs on par with human social engineering experts at roughly one-thirtieth the cost. Researchers at Oxford found that large language models could generate tailored spear phishing for hundreds of targets at a fraction of a cent per message. - **What is business email compromise and how big is the problem?** Business email compromise is a scam where attackers impersonate a trusted contact to trick someone into transferring money or credentials. The FBI reported BEC losses of $2.77 billion in 2024 alone. - **Why are AI phishing attacks harder to detect than traditional ones?** AI-generated phishing uses real information scraped from LinkedIn profiles, company websites, and public records to craft messages that match the target's actual job and workflow. In testing, these messages achieved a 54% click-through rate compared to 12% for generic phishing. - **What is the best defense against AI-powered phishing?** Verify any request to log in or change settings through a separate channel. Call the sender directly, or navigate to the site yourself instead of clicking the link. The message content can be perfect, but the domain in the URL and a phone call to the real sender cannot be faked. A digital marketing specialist opens his inbox. There's a message about one of his Google Ads accounts. A settings change needs his attention. He manages Google Ads, Google Business profiles, and SEO campaigns for a roster of clients, so he gets messages like this all the time. This one referenced his actual work, named the kind of account he manages, and asked him to log in and adjust a setting. Everything checked out. Except the URL. The domain in the login link was close. One character off, maybe two. The kind of thing you'd only catch if you were squinting, and why would you squint at something that sounds exactly like your job? He caught it. Barely. ## What Changed The thing is, the danger was never the crude stuff. The "you've won a prize" emails, the obviously fake invoices. We all learned to spot those. The danger is a message so well-fitted to your actual work that it reads as routine. This kind of attack used to take real effort. Someone had to research the target, learn their professional vocabulary, and build a pretext that matched his daily workflow. That cost time and talent, which meant attackers mostly went after people worth the investment. AI collapsed that cost to almost nothing. Researchers at Oxford found that large language models could generate tailored spear phishing for over 600 UK members of Parliament at a fraction of a cent per message.[^1] A team at TrendAI went from a LinkedIn profile to a fully customized attack in 30 minutes, and the whole system was built in 24 hours using off-the-shelf tools.[^2] ![Watercolor of a magnifying glass hovering over a browser address bar, the URL slightly blurred with one letter glowing faintly red, warm light on a cluttered desk](../../assets/images/focus/inline/how-ai-hacks-humans/one-letter-off.jpg) *Six hundred tailored attacks for the price of a large coffee.* And it works. AI-generated phishing emails hit a 54% click-through rate in controlled testing, compared to 12% for the generic kind we've trained ourselves to ignore.[^3] The AI-gathered intelligence about each target was accurate 88% of the time, and the whole operation performed on par with human experts at about one-thirtieth the cost.[^3] ## The Cover Story But the AI is only half of it. The other half is the platforms we use every day. Google changes something every week. A new policy notification, a revised settings page, an alert that your account needs attention. If you manage client accounts for a living, you are swimming in legitimate requests to log in and change things. The attacker's message didn't need to be clever. It just needed to sound like one more notification in the pile. The pile never stops growing. Familiarity is the actual vulnerability here. The constant churn of platform updates trained this specialist to comply with exactly the kind of request the attacker was making. Google's own notification habits provided the cover story for free. ## What to Do About It The FBI puts it plainly: be alert to hyperlinks that may contain misspellings of the actual domain name.[^4] That's the tell that saved the specialist in this scenario. The message was flawless. The URL could not be. Business email compromise cost $2.77 billion in 2024, and total cybercrime losses hit $16.6 billion, up 33% from 2023.[^5] The attacks driving those numbers don't look like scams. They look like work. ![Watercolor of a rotary phone with its receiver resting in the cradle on a warm wooden desk beside an open laptop, soft afternoon light through a window](../../assets/images/focus/inline/how-ai-hacks-humans/verify-the-sender.jpg) *Every year the attacks get smarter. The fix is still a phone call.* So when a message asks you to log in and do something, verify the request through a different channel. Call the sender. Open the site yourself instead of clicking the link. The message can be perfect, but the domain can't fake being real, and neither can a voice on the other end of a phone. [^1]: [LLMs for Spear Phishing: GovAI/Oxford Study](https://www.governance.ai/research-paper/llms-used-spear-phishing) [^2]: [From LinkedIn to Tailored Attack in 30 Minutes](https://www.trendaisecurity.com/en/resources-insights/deep-research/from-linkedin-to-tailored-attack-in-30-minutes-how-ai-accelerates-target-profiling-for-cybercrime) [^3]: [AI-Supported Spear Phishing Fools More Than 50% of Targets](https://www.malwarebytes.com/blog/news/2025/01/ai-supported-spear-phishing-fools-more-than-50-of-targets) [^4]: [FBI IC3 PSA: Business Email Compromise](https://www.ic3.gov/PSA/2024/PSA240911) [^5]: [FBI IC3 2024 Report via Abnormal AI](https://abnormal.ai/blog/2024-fbi-ic3-report) --- ### A Lived-In Language **URL:** https://odysseyalive.com/focus/a-lived-in-language **Published:** August 9, 2026 **Category:** Field Notes **Tags:** anthropology, chinuk-wawa, linguistics, pacific-northwest, cultural-preservation, language-revitalization **Purpose:** The Chinuk Wawa greeting ɬax̣ayam literally means 'poor.' I think that etymology tells you something about the people who kept saying it, even when saying it could get them punished. About 500 people speak Chinuk Wawa conversationally now, and they're still making new words. **FAQ:** - **What does the Chinuk Wawa greeting ɬax̣ayam mean?** ɬax̣ayam is the standard Chinuk Wawa greeting. Linguist David Robertson traces it to Lower Chinookan lax̣awyam, meaning 'one's poverty' or 'poor.' The etymology carries an undertone of humility, like you're placing yourself below the person you're welcoming. - **What is the Chachalu Museum in Grand Ronde, Oregon?** Chachalu is a cultural center operated by the Confederated Tribes of Grand Ronde. The name comes from Yamhill Kalapuya meaning 'place of the burnt timbers.' Its Cintutac Gallery takes its name from the Yamhill word for 'to find or recover something that was thought to be lost.' - **How can I study Chinuk Wawa for college credit?** Lane Community College offers a two-year credited Chinuk Wawa program with six courses that satisfy World Language requirements across the Oregon University System. The program started in 2006 in collaboration with Grand Ronde and covers language, Indigenous culture, and community events. - **What is Nsayka Wawa?** Nsayka Wawa is an interactive fiction module that teaches Chinuk Wawa through play and narrative context rather than word lists. Built by Odyssey Alive, it mirrors how the language was historically learned through trade and daily life. Betas open October 12th. - **Why did Chinuk Wawa nearly disappear?** Boarding schools pulled children from their families and punished them for speaking their own languages, including Chinuk Wawa. Nearly 1,000 documented Native child deaths resulted from the boarding school system. The language survived because people kept speaking it, and about 500 speakers are still growing that number. --- ### The Endorsement **URL:** https://odysseyalive.com/focus/the-endorsement **Published:** June 13, 2026 **Category:** AI Transformation **Tags:** anthropic, fable-5, mythos-5, export-controls, regulation, competition, AI **Purpose:** The US government issued an export control directive pulling Anthropic's Fable 5 and Mythos 5 from the market, the first time a government has forced a frontier AI model offline. The action inadvertently validates Anthropic as the most capable AI lab while branding every competitor whose models remain available as not dangerous enough to worry about. **FAQ:** - **Why did the US government ban Fable 5 and Mythos 5?** Commerce Secretary Howard Lutnick sent an export control directive to Anthropic on June 12, 2026 after another company claimed to have found a jailbreak in Mythos. Anthropic says the jailbreak was narrow and demonstrated capabilities widely available from other models including OpenAI's GPT-5.5. - **Are other AI models like GPT-5.5 also banned?** No. Only Anthropic's Fable 5 and Mythos 5 were targeted. GPT-5.5 and Google's models remain available, even though Anthropic says those models have comparable capabilities to what the jailbreak demonstrated. - **What is Project Glasswing?** A cybersecurity initiative launched April 7, 2026 that gave over forty organizations exclusive access to Anthropic's Mythos model for defensive security research. Anthropic has been in ongoing discussions with US government officials about the model's capabilities since its launch. - **How does this affect Anthropic's competitors?** By singling out Anthropic's models as the only ones dangerous enough to ban, the government certified them as the most capable. If the same standard were applied industry-wide, Anthropic argues it would halt all new model deployments for every frontier provider. The US government just did Anthropic the biggest favor in the history of Silicon Valley. I don't think they meant to. At 5:21 PM on a Friday, Commerce Secretary Howard Lutnick sent Anthropic's CEO a letter placing Fable 5 and Mythos 5 under export controls.[^1] By midnight, Anthropic had shut down both models for every customer on the planet. The stated concern? A narrow jailbreak that Anthropic says demonstrated capabilities "widely available from other models, including OpenAI's GPT-5.5."[^2] GPT-5.5 is still running. Google's models are still running. Only Anthropic's got pulled. ## The Certification When the government bans your AI for being too powerful, that's not a regulatory action. That's a product endorsement. The US government looked at every frontier model on the market, identified exactly one as dangerous enough to warrant an export control directive, and named it. Everyone else got a pass. For OpenAI and Google, that pass isn't the relief it sounds like. "Too safe to ban" is another way of saying "not capable enough to worry about." The government just told the world there's a tier, and their models aren't on it. ![Watercolor of an ornate rubber stamp pressing down on a document, the impression glowing faintly gold, warm light on dark polished wood](../../assets/images/focus/inline/the-endorsement/certification.jpg) *Export controls. Usually for missiles, fighter jets, and nuclear material. This one, for autocomplete.* ## The Informant The Axios scoop drops a detail that reframes everything. The Commerce Department acted after "another company claimed it was able to jailbreak Mythos."[^1] A competitor went to the government and said, in effect, their model is so powerful we can make it do dangerous things. That competitor just told the world which model they're afraid of. You don't spend time jailbreaking second-place technology. And the government's response was to ban only the model that got jailbroken, not the one doing the jailbreaking. We asked for AI regulation. This is what it looks like. A competitor calls the government, the government pulls your product, and the competitor keeps serving customers. ## The Keeper Here's the part that should bother you. The government isn't just banning Mythos from the public. They've been in the room with it since April. Project Glasswing gave over forty organizations exclusive Mythos access on April 7.[^4] Anthropic has been in ongoing discussions with US government officials about the model's offensive and defensive capabilities since that launch.[^4] The public lost access on June 12. The officials who ordered the ban already knew what it could do. ![Watercolor of a heavy vault door slightly ajar, warm golden light spilling out from inside, a dark hallway outside, a small sign reading AUTHORIZED PERSONNEL](../../assets/images/focus/inline/the-endorsement/the-keeper.jpg) *Supply chain risk by day. Cybersecurity partner by night.* The same administration that called Anthropic a "supply chain risk" in 2026 is in ongoing discussions with Anthropic about this model's capabilities.[^3][^4] That designation? Historically reserved for foreign adversaries. Too dangerous for you. Not too dangerous to study. ## The Invoice If Anthropic ever files an S-1, the lede writes itself. "Our technology was so advanced the United States government issued an emergency export control directive." That's not a risk factor. That's a selling point. And every other frontier lab should be paying attention. If a narrow jailbreak is cause to pull a commercial model from hundreds of millions of users, then GPT-5.5 is next. So is Gemini. Anthropic put it plainly. "If this standard was applied across the industry, we believe it would essentially halt all new model deployments for all frontier model providers."[^2] The government aimed at Anthropic. They hit everyone else. --- ## References [^1]: Isenstadt, A. & Curi, M. (2026). "Scoop: Trump admin blocks foreign access to Anthropic's most powerful AI." [Axios](https://www.axios.com/2026/06/12/anthropic-trump-mythos-fable-national-security) [^2]: Anthropic. (2026). "Statement on the US government directive to suspend access to Fable 5 and Mythos 5." [Anthropic](https://www.anthropic.com/news/fable-mythos-access) [^3]: Capoot, A. (2026). "Anthropic disables access to Fable 5 and Mythos 5 to comply with government directive." [CNBC](https://www.cnbc.com/2026/06/12/anthropic-disables-access-to-fable-5-and-mythos-5-to-comply-with-government-directive.html) [^4]: Anthropic. (2026). "Project Glasswing: Securing critical software for the AI era." [Anthropic](https://www.anthropic.com/glasswing) --- ### Two Brains: Why Dynamic Model Routing Beats Picking One AI **URL:** https://odysseyalive.com/focus/two-brains **Published:** June 11, 2026 **Category:** Groundwork **Tags:** ai, claude-code, open-source, model-routing, skills **Purpose:** Dynamic model routing matters more than picking the best model in 2026. I built Hemispheric Model Delegation into Claude Enforcer to route creative work to one model and analytical work to another, replacing the manual switching I'd been doing across four subscriptions. The system spawns focused agents pinned to the right model whenever a workflow crosses into the other hemisphere. **FAQ:** - **What is Hemispheric Model Delegation?** A feature of Claude Enforcer that assigns a creative brain and an analytical brain to your AI workflows. When you start a task, the routing system assesses which model should handle the work. Cross-lane steps inside a workflow are handled by focused agents pinned to the appropriate model, so the user never switches manually. - **Why use two AI models instead of one?** In 2026, no single model leads every benchmark category. Claude leads agentic coding, GPT-5 leads expert knowledge, and Gemini leads human preference. Optimizing a model for code degrades its creative output and vice versa. Routing each task to the model that excels at it outperforms hoping one does everything. - **What is the Mixture of Experts architecture?** A machine learning technique dating to 1991 where specialized subnetworks each focus on specific tasks, with a gating network deciding which expert handles each input. Major AI providers already use variations internally, and IDC predicts 70% of top AI enterprises will adopt dynamic model routing by 2028. - **How do you create a skill with Claude Enforcer?** Run skill-builder new to generate a skeleton, add your rules as directives, and the audit system wires enforcement checkpoints underneath. The project is open source, MIT-licensed, and installs with one command from the GitHub repository. What if AGI is already here, just scattered across a dozen models, and we keep missing it because we're waiting for one of them to do everything? I switched models three times. Not because anything was broken. My coding model had just refactored an entire authentication flow without missing a test. Precise, methodical, not a wasted line. But when I pivoted to editing a client article, the same model suggested revisions so flat I could have ironed a shirt on it. Every suggestion was technically correct and completely lifeless. I switched to the creative model. The draft had a pulse. Then I needed to debug a hook script, and the creative model started inventing function signatures that don't exist. Three tasks. Three model switches. I'd been doing this for months before I stopped to wonder why. That's dynamic model routing. Each task goes to the model built for it, instead of running them all through the same one. ![Watercolor of two paths diverging through a forest, one warm and golden, the other cool and precise, seen from above](../../assets/images/focus/inline/two-brains/diverging-paths.jpg) *Two roads. I'd been pretending they were one.* ## The Split: No Best Model in 2026 Pluralsight published a breakdown of where models stand in 2026, and the story it tells is simple. There is no best model.[^1] Claude leads agentic coding. GPT-5 beat everyone on expert-level knowledge. Gemini? Highest human preference scores. Developers at Faros AI started giving them job titles: "The Auditor" for GPT-5.2, "The Architect" for Opus, "The Workhorse" for Sonnet.[^2] Nobody got called "The Everything." We spent two years asking which model was best. The answer turned out to be a routing problem, not a ranking one. I carry four model subscriptions because each one has gaps. The underlying concept even has a name: Mixture of Experts. Specialized subnetworks each handle different types of input, and a routing gate decides who gets the job. The technique dates back to a 1991 paper.[^3] Thirty-five years old. The marketing budget is new. The real leverage was always [the harness, not the model](/focus/harness-not-model). Even the vendors know. OpenAI's GPT-5 already routes between sub-models internally, picking a fast responder for simple questions and a deeper reasoner for hard ones. They just don't hand you the steering wheel. ## Two Hemispheres: Building a Model Router So I built the router myself. [Claude Enforcer](https://github.com/odysseyalive/claude-enforcer) started as a tool for fighting [context drift](/focus/your-ai-has-amnesia). But I'd been watching coding models and creative models sharpen in opposite directions. I finally built the thing I kept circling. I called it Hemispheric Model Delegation.[^4] I told it which model thinks like a writer and which one thinks like an engineer. The routing logic sits in the same [context layer](/focus/context-is-the-interface) that keeps skills from drifting. When I start a task, it figures out which brain the work belongs to and asks once if I want to switch. Mid-workflow, if the writing needs research, it sends a focused agent to the analytical model. The answer comes back. The creative model never breaks stride. Two brains, one session. Creating a skill takes one command. I ran `/skill-builder new`, added the routing rules, and the audit wired them into checkpoints on its own. The whole project is open source, one line to install. ![Watercolor of two connected desks in a warm studio, one with handwritten pages and ink, the other with a glowing terminal, a single thread of light running between them](../../assets/images/focus/inline/two-brains/connected-desks.jpg) *The writer can't debug. The debugger can't write. Nobody complained.* IDC predicts that by 2028, 70% of top AI enterprises will use dynamic model routing.[^5] I think the timeline is conservative. Anthropic will ship native model-switching in Claude Code within a year. You'd be fixing a bug one minute and drafting an email the next, and the system would handle the routing. No toggling, no thinking about it. They're already doing it inside the models. The only question is when they expose the controls. --- ## References [^1]: Pluralsight. (2026). "The Best AI Models in 2026: What Model to Pick for Your Use Case." [Pluralsight](https://www.pluralsight.com/resources/blog/ai-and-data/best-ai-models-2026-list) [^2]: Dunlap, N. (2026). "Best AI Models for Coding in 2026: Real-World Developer Reviews." [Faros AI](https://www.faros.ai/blog/best-ai-model-for-coding-2026) [^3]: Shivanandhan, M. (2026). "How the Mixture of Experts Architecture Works in AI Models." [freeCodeCamp](https://www.freecodecamp.org/news/how-the-mixture-of-experts-architecture-works-in-ai-models/) [^4]: Meetze, F. (2026). Claude Enforcer. [GitHub](https://github.com/odysseyalive/claude-enforcer) [^5]: Ward-Dutton, N. (2025). "The Future of AI is Model Routing." [IDC](https://www.idc.com/resource-center/blog/the-future-of-ai-is-model-routing/) --- ### Will AI Stall Itself? **URL:** https://odysseyalive.com/focus/will-ai-stall-itself **Published:** June 4, 2026 **Category:** AI Transformation **Tags:** data-centers, infrastructure, cooling, critical-minerals, aridification, AI **Purpose:** We talk about AI as if it were weightless, a cloud. It is the most material-intensive machine of the century: it drinks water, but it also demands a bulky apparatus of immersion tanks, chillers, diesel generators, copper, helium, and acres of concrete to manage its heat. As AI expands its capabilities, the physical body grows with the mind, and the West it is mostly built in keeps getting drier. The limit on AI may be physical, not how clever the model gets. **FAQ:** - **What is the real bottleneck for AI growth?** Increasingly it is physical, not algorithmic. Analysts who track the industry say the binding constraints are electricity, water, and materials like copper and helium, not the cleverness of the models. A single large data center can use 5 million gallons of water a day and 27 tons of copper per megawatt of capacity. - **Is the problem with AI data centers just water?** No. Water is the most visible cost, but the larger story is the whole physical stack. Managing the heat requires bulky hardware: immersion tanks filled with dielectric fluid, chillers, heat exchangers, diesel generators the size of rail cars, and hundreds of acres of steel and concrete. The cure for the heat is itself a mountain of material. - **Why does making AI smarter make the resource problem worse?** Every leap in capability pushes more heat through the same floor space, which forces more exotic and bulky cooling and draws more metal and power. The coming wave of physical AI, robots and autonomous systems, is its own new hardware demand cycle. The body grows with the mind, so a smarter model is not a lighter one. - **What is aridification and why does it matter for AI?** Aridification is the scientific term for a permanent shift to a drier baseline, as opposed to drought, which is temporary. The American Southwest is aridifying, which steadily raises the water and machinery a data center needs to cool the same workload. Because most AI power still burns fossil fuel, the machine warms the climate that then makes it thirstier. I kept saying "the cloud." Everyone does. It floats somewhere above us, untouchable, instant. I never thought about what it weighs. Then I started reading the local news. A subdivision outside Atlanta where the water pressure tanked. A town in Arizona that voted against a data center and watched it get built anyway, just past the city line. In Texas, Corpus Christi is preparing for 25% water cuts while a researcher at the University of Houston projects data centers in the state will need 399 billion gallons a year by 2030.[^1] That is enough to drop Lake Mead, the largest reservoir in the country, by more than sixteen feet. The cloud, it turns out, is a windowless metal building in the desert. And it is incredibly thirsty. ## Heat First Everything starts with heat. AI chips do not run warm. They run hot, dense, the kind of hot where the silicon damages itself if you do not pull the heat away fast enough. A single large facility can drink five million gallons of water a day to stay cool, roughly what a town of 50,000 people uses.[^2] About 80% of that water evaporates. Gone. Not discharged, not recycled. Just gone.[^2] But water, I realized, is only the part of the problem that has a face on it. The part a neighbor notices when her faucet slows to a trickle. The actual body of AI is much bigger than its thirst. ## The Apparatus When communities push back on water use, or when the supply runs short, the industry does not get lighter. It gets heavier. It builds immersion tanks and submerges servers in engineered dielectric fluid. It runs direct-to-chip plumbing, chillers, heat exchangers, miles of coolant pipe.[^2] Thousands of diesel backup generators sit in Northern Virginia alone, each one the size of a rail car, running for "demand response" up to fifty hours at a time.[^3] Hundreds of acres of farmland disappear under steel and concrete. ![Watercolor of a vast windowless data center hall, rows of immersion-cooling tanks filled with pale blue dielectric fluid, a tangle of thick coolant pipes and pumps running overhead, a single technician in silhouette for scale](../../assets/images/focus/inline/will-ai-stall-itself/the-machine.jpg) *Your instantaneous answer, fully plumbed.* We did not dematerialize computing. We built the most material-hungry machine of the century and named it after the sky. ## Not Just Water Once I started looking at what goes into these buildings, the water almost seemed modest. Each megawatt of data center capacity requires about 27 tons of copper just for the wiring and cooling loops, and copper isn't the only thing running short. Aluminum hit a four-year high. Chip factories are rationing helium after the strikes on Qatar disrupted a third of the global supply.[^4] An Omdia analyst summed it up in a line I haven't been able to shake. The bottleneck on AI in 2026 is not genius. It is "the next shipment of copper." The most valuable thing in an AI chip, he wrote, is not the silicon. It is the certainty that it will arrive.[^4] ![Watercolor of an open-pit copper mine terraced into red desert earth, tiny haul trucks on the switchbacks, dust hanging in warm afternoon light](../../assets/images/focus/inline/will-ai-stall-itself/the-rocks.jpg) *Every answer you get starts in a hole like this one.* And that is just the operating cost. A single chip has already consumed thousands of gallons of water before it ever reaches a server rack, just from the manufacturing process.[^2] ## Somebody's Street In Fayette County, Georgia, this spring, residents of a subdivision twenty miles south of Atlanta noticed their water pressure dropping. That led the county utility to investigate, and they found two industrial water hookups feeding a 615-acre data center campus. One meter the county did not know existed. By the time they caught it, the facility had drawn 29 million gallons. The county chose not to fine the developer, explaining that the company was its largest customer and the relationship "requires partnership."[^1] Over fifty communities across the country have passed bans or moratoria on new data centers since then.[^1] Some developers have started building just past city limits specifically to dodge state laws that require proof of a hundred-year water supply.[^1] The finished buildings, for the record, employ about a hundred people each. The real jobs were in pouring the concrete.[^3] ## The Ratchet I pulled up the siting maps, and the pattern jumped out. These facilities cluster in the hot, dry West, because that's where land and electricity come cheap. But the hotter the air gets, the more water and machinery it takes to cool the same chips,[^2] and the West isn't cooling down. Scientists gave up calling it a drought. Drought implies the rain comes back. They call it aridification now. "Drought is temporary," the Colorado River researchers wrote. "Aridification is permanent."[^5] ![Watercolor of a cracked dry lakebed stretching to distant hills, a faint high-water line visible on the rocks where the water used to reach, sparse sage scrub, warm pale sky](../../assets/images/focus/inline/will-ai-stall-itself/the-ratchet.jpg) *The water line shows where the lake used to be.* It gets worse. More than half the electricity powering these facilities still comes from fossil fuel,[^2] so the machines warm the air that makes them thirstier. And every new generation of AI pushes more heat through the same square footage, which is what forces the bigger, bulkier cooling in the first place. The coming wave of physical AI, humanoid robots and autonomous systems, isn't lighter. It's its own fresh demand cycle for metal and power.[^4] The mind gets smarter. The body gets heavier. ## Maybe an Exit Closed-loop cooling systems can cut a building's freshwater use by about 70%.[^2] Smaller models built for one task run on a fraction of the energy. The hardware improves every year. But the exit, so far, has been made of the same material as the wall. And efficiency keeps doing what efficiency always does. It makes the thing cheaper, which means we do more of it. Every gain to date has been spent on a bigger model, not a smaller footprint. I'm typing this on one of these machines right now, burning somebody's water to finish this sentence. I don't think the question is whether AI runs out of water or copper. I think it's whether a thing that gets heavier every time it gets smarter can ever stop getting heavier. I don't know the answer. But I noticed the cloud has a shadow, and it falls on somebody's well. --- ## References [^1]: Salzman, A. (2026). "America's data centers are thirsty. Rural towns are paying the price." A QTS campus drew 29 million gallons through an unbilled meter; the county cited "partnership" in declining to fine it; more than 50 cities have enacted bans or moratoria; Texas data centers projected at 399 billion gallons/year by 2030. [Fortune](https://fortune.com/2026/05/13/data-center-georgia-arizona-water-wars) [^2]: Yañez-Barnuevo, M. (2025). "Data Centers and Water Consumption." Large data centers can consume up to 5 million gallons per day (a town of 10,000 to 50,000 people); roughly 80% of withdrawn water evaporates; immersion cooling bathes chips in dielectric fluid; in hotter climates like the southwest United States they need more water to cool the same equipment; 56% of data center electricity comes from fossil fuels; a single chip consumes thousands of gallons before installation; closed-loop systems can reduce freshwater use by up to 70%. [EESI](https://www.eesi.org/articles/view/data-centers-and-water-consumption) [^3]: Wachsmuth, D. et al. / Lincoln Institute of Land Policy. (2025). "Data Drain: The Land and Water Impacts of the AI Boom." Diesel backup generators "the size of a rail car" run for demand response; facilities cover hundreds of acres of steel and concrete; most jobs are temporary construction work. [Lincoln Institute](https://www.lincolninst.edu/publications/land-lines-magazine/articles/land-water-impacts-data-centers) [^4]: Bateman, B. / Omdia. (2026). "The great data center delay: Why your AI chips are stuck in 2026." 2026 is defined by "a brutal shortage of electricity, copper and critical gases"; each megawatt needs roughly 27 tons of copper; aluminum at a four-year high; helium rationed; bromine at $12,000 per ton; the "physical AI" inflection creates a new hardware demand cycle; the most valuable component is "the certainty of its delivery." [Manufacturing Dive](https://www.manufacturingdive.com/news/opinion-omdia-ai-semiconductor-chip-scarcity/817172) [^5]: Lohan, T. (2020). "'Megadrought' and 'Aridification': Understanding the New Language of a Warming World." The Colorado River Research Group: "Drought is temporary. Aridification is permanent." [The Revelator](https://therevelator.org/megadrought-aridification-climate) --- ### The Vacancy **URL:** https://odysseyalive.com/focus/the-vacancy **Published:** May 14, 2026 **Category:** AI Transformation **Tags:** open-source, supply-chain, career-ladder, npm, security, IBM, AI **Purpose:** Open source was never an ideology. It was a labor market where developers traded free work for career capital and corporations funded it because the economics worked. AI broke the career ladder, corporations are cutting the teams, and the security model built on volunteer labor is collapsing with them. **FAQ:** - **Why are open source projects becoming less secure?** The security model depended on volunteer maintainers who reviewed code and patches. Those volunteers contributed for career capital, commit history as credential. With AI reshaping hiring and corporations cutting open source teams, the labor that sustained security review is disappearing while attackers are scaling up, with 454,600 malicious packages identified in 2025 alone. - **What happened with IBM and Red Hat open source layoffs?** In April 2026, IBM cut 300 engineers who worked on core infrastructure projects like libvirt, QEMU, and OpenShift. Some found out when their VPN stopped working before anyone called. IBM is simultaneously tripling entry-level hiring for AI management roles, redirecting investment away from the open source teams it acquired for $34 billion. - **What is the Mini Shai-Hulud npm worm?** A self-replicating worm discovered in May 2026 that compromised more than 170 packages across npm and PyPI, affecting projects from TanStack, Mistral AI, and Guardrails AI. It hijacked maintainer credentials through GitHub authentication tokens and published validly signed poisoned packages that passed every verification check. - **Is AI-written code more reviewable than open source?** In practice, yes. The classical argument for open source was reviewability, but most developers read documentation, not source code. Code built with AI tools sits in your own repo under your own linters and tests, with no documentation drift and no upstream maintainer pushing patches you will never read. - **What should laid-off tech workers know about open source careers?** The open source career paradigm, where contributing free work built credentials and maintainer status served as social proof, is eroding. The 136,000 tech workers laid off in 2026 who are investing in GitHub profiles may be polishing a credential the industry has already moved past, as corporations pull funding from the open source teams they used to support. I used to tell people I preferred open source because I could read the code. That was mostly true. I read the documentation, figured out what I needed, and moved on. If something broke, I looked at the source. Nobody reads the source unless something is broken. We read the docs. The whole argument for open source was that you could review it. You had the code right there. You could verify it. In practice, volunteers maintained the project, and we trusted them the same way we trusted any vendor. We just felt better about it because the source was technically public. ## The Business Model There was a business model underneath all of that. Developers contributed free work in exchange for career capital. You built your commit history, got maintainer status, and employers noticed. Corporations funded open source because the economics worked. I wrote about what happens when that career ladder breaks in [The Broken Rung](/focus/the-broken-rung). Now the corporations are pulling it out entirely. 136,000 tech workers have been laid off in 2026, and the open source engineers are taking a disproportionate share of those cuts. IBM spent $34 billion acquiring Red Hat. In April 2026, they cut 300 engineers who worked on libvirt, QEMU, and OpenShift.[^1] Some found out because their VPN stopped working before anyone called. IBM is simultaneously tripling entry-level hiring for AI management roles.[^1] ![Watercolor of an empty engineering desk with a dark monitor showing a login prompt, a corporate badge left on the keyboard, warm late-afternoon light through office windows](../../assets/images/focus/inline/the-vacancy/ladder.jpg) *libvirt still runs. QEMU still runs. Their authors are interviewing at fintech startups.* ## What Got In When you lose the people doing the security work, the security stops getting done. Sonatype counted 454,600 malicious packages across open source registries in 2025.[^2] These aren't hobbyists. This is state-level operations running through npm, the same registries developers install from every day without thinking about who reviewed what went in. Sonatype calls it "toolchain masquerading." The packages aren't pretending to be obscure utilities. They look like build plugins, linters, migration helpers.[^2] In May 2026, a self-replicating worm called Mini Shai-Hulud compromised more than 170 packages across npm and PyPI, hitting TanStack, Mistral AI, and Guardrails AI.[^3] It hijacked maintainer credentials through GitHub's own authentication tokens, published new versions of legitimate packages, and moved on to the next maintainer in the chain. Every verification system said the packages were legitimate. Validly signed. Attestation checked out. Poisoned. The people who used to catch this are getting laid off. The people exploiting it are not. ![Watercolor of a laptop on a clean desk showing lines of code, warm morning light, a single coffee cup, no network cables visible, a feeling of quiet self-sufficiency](../../assets/images/focus/inline/the-vacancy/clean-desk.jpg) *No maintainer to impersonate. No token to hijack. Just your code.* I'm self-employed. I'm probably the least affected person writing about this. When I build a connector with Claude instead of pulling in a library, I don't inherit any of that exposure. The code is in my repo, under my linters, my tests. Nobody upstream pushing patches I won't read. The code I write with AI is actually more reviewable than the open source I used to advocate for, because I wrote it, and nobody is going to change it on me. That's the part that gets me. Open source was supposed to be the reviewable option. Yet, many of us never reviewed it beyond the documentation provided. Unless there was a problem. Now, I haven't touched a line of code since January. And the 136,000 people who just got laid off, the ones updating their GitHub profiles, are wondering if anyone upstream still marks their open source contributions as relevant. --- ## References [^1]: Ardell, R. (2026). "IBM Layoffs 2026: Where Displaced Talent Is Going." [KORE1](https://www.kore1.com/ibm-layoffs-2026) [^2]: Sonatype. (2026). "The Evolving Software Supply Chain Attack Surface." [State of the Software Supply Chain 2026](https://www.sonatype.com/state-of-the-software-supply-chain/2026/open-source-malware) [^3]: Lakshmanan, R. (2026). "Mini Shai-Hulud Worm Compromises TanStack, Mistral AI, Guardrails AI & More Packages." [The Hacker News](https://thehackernews.com/2026/05/mini-shai-hulud-worm-compromises.html) --- ### The Quiet **URL:** https://odysseyalive.com/focus/the-quiet **Published:** April 25, 2026 **Category:** AI Transformation **Tags:** mythos, project-glasswing, cybersecurity, patching, anthropic, zero-day, microsoft **Purpose:** Eighteen days after Anthropic shipped Mythos to Project Glasswing partners, visible patching surged to near-record levels while public discourse stayed silent. Microsoft shipped its second-largest Patch Tuesday in history. AI vulnerability submissions tripled. The silence isn't absence of activity. It's a disclosure design that makes the most consequential cybersecurity event of 2026 look routine. **FAQ:** - **What happened after Anthropic launched Project Glasswing?** Microsoft shipped 165 CVEs in April 2026, its second-largest Patch Tuesday ever. Trend Micro's Zero Day Initiative reported that AI-discovered vulnerability submissions tripled. OpenBSD patched five X-server CVEs within a week. None of these patches carry a 'found by Mythos' label, and the press is explicitly cautious about attribution. - **Why is there so little public noise about Mythos patching?** Anthropic published cryptographic hashes for most Mythos discoveries, promising to reveal details only after fixes ship. Partners cannot publicly attribute patches to the model. The hashed-disclosure system makes Glasswing-driven fixes indistinguishable from routine security maintenance. - **How many Mythos-discovered vulnerabilities have been patched?** Anthropic reported finding thousands of zero-day vulnerabilities across every major operating system and browser. Most cryptographic hashes published on April 7 haven't been matched with public patches yet. The record-setting April patch volume represents a fraction of Mythos's total discoveries. - **Will the silence around Project Glasswing last?** With more than forty organizations and hundreds of engineers holding access, operational secrecy has a limited shelf life. The signal will likely break through as patches accumulate, researchers connect dots, and the gap between discovery and disclosure narrows. I published [The Dress Rehearsal](/focus/the-dress-rehearsal) on a Wednesday. By Friday, I was listening for what should have come next. It's eerily quiet. Anthropic handed their most dangerous model to more than forty organizations on April 7. Apple, Amazon, Microsoft, Google, Cisco, Broadcom, the Linux Foundation.[^1] The assignment: find and patch critical infrastructure vulnerabilities before similar capabilities reach anyone else. Eighteen days later, from where I sit, the air is still. I'm on Arch Linux. I get patches every day. That's normal. What's not normal is the absence of noise. When Microsoft ships a bad update, the forums catch fire within hours. When Apple pushes an emergency fix, the tech press runs it for a week. Mythos is supposedly rewriting the cybersecurity landscape, and the loudest thing I've heard about it since April 7 is my own article. ## What the Numbers Say The patches are there if you know where to look. Microsoft's April 14 Patch Tuesday addressed 165 vulnerabilities. Second-largest monthly release in the company's history.[^2] Dustin Childs, head of threat awareness at Trend Micro's Zero Day Initiative, wrote that AI-discovered vulnerability submissions have "essentially tripled, making triage a challenge."[^2] OpenBSD pushed five X-server CVE fixes on April 14, seven days after Mythos shipped to its partners.[^3] Adobe released an emergency zero-day patch on April 11.[^4] ![Watercolor of a wall of glowing monitors showing scrolling numbers and alerts in warm amber and blue, viewed through a rain-streaked window from outside, a person walking past on the sidewalk not looking](../../assets/images/focus/inline/the-quiet/dashboard.jpg) *165 CVEs. Tripled submissions. Second-largest month on record. Nobody's talking about it.* The record month happened. It just happened quietly. ## Transparent Wings Project Glasswing is named after a butterfly that hides by being see-through. The name is doing exactly what the butterfly does. Adam Barnett at Rapid7 told Krebs on Security it's "tempting to imagine" the April spike was tied to Glasswing, but attributed the volume instead to "ever-expanding AI capabilities" generally.[^4] The press is being careful. Anthropic's design ensures they can be. For most of the vulnerabilities Mythos found, Anthropic published only cryptographic hashes, promising to reveal specifics "after a fix is in place."[^1] ![Watercolor of a glasswing butterfly perched on a leaf, its wings nearly invisible with foliage visible through them, warm natural light and soft forest background](../../assets/images/focus/inline/the-quiet/glasswing.jpg) *Named after a butterfly that hides by being transparent. So far, perfect camouflage.* Partners can't publicly say "Mythos found this." Researchers can't verify which patches came from the consortium and which came from routine fuzzing. The most consequential cybersecurity event of 2026 is being absorbed into normal patch queues, unlabeled, indistinguishable from Tuesday. ## The Math The numbers don't add up to safety. Anthropic says Mythos found "thousands" of zero-day vulnerabilities across every major operating system and browser.[^1] Most of those hashes haven't been matched to public patches. The surge we can see, record-setting as it is, covers a fraction of what was actually found. And the consortium is forty-plus organizations. Hundreds of engineers with access to a model that discovers exploits while they sleep. Secrets at that scale have a half-life measured in weeks, not years. The quiet is engineered. It's also temporary. Somewhere between Anthropic's hashed disclosures and a researcher's late-night curiosity, the signal will break through. The patches will still be arriving. The silence won't. --- ## References [^1]: Anthropic. (2026). "Project Glasswing: Securing critical software for the AI era." [Anthropic](https://www.anthropic.com/glasswing) [^2]: Montalbano, E. (2026). "Microsoft drops its second-largest monthly batch of defects on record." [CyberScoop](https://cyberscoop.com/microsoft-patch-tuesday-april-2026) [^3]: OpenBSD. (2026). "OpenBSD 7.7 Errata." [OpenBSD](https://www.openbsd.org/errata77.html) [^4]: Krebs, B. (2026). "Patch Tuesday, April 2026 Edition." [Krebs on Security](https://krebsonsecurity.com/2026/04/patch-tuesday-april-2026-edition) --- ### The Dress Rehearsal **URL:** https://odysseyalive.com/focus/the-dress-rehearsal **Published:** April 23, 2026 **Category:** AI Transformation **Tags:** opus-4-7, mythos, claude-enforcer, claude-code, cybersecurity, anthropic, project-glasswing **Purpose:** Anthropic deliberately trained Opus 4.7 to be less capable than Claude Mythos Preview, a model whose cybersecurity capabilities are too dangerous for public release. The disciplines 4.7 demands are vocabulary for steering whatever comes next. **FAQ:** - **What is Claude Mythos Preview?** Claude Mythos Preview shipped April 7, 2026, to more than forty partner organizations through a consortium called Project Glasswing. Anthropic has no plans for broader release. The model autonomously discovers and exploits zero-day vulnerabilities across every major operating system and browser, including a 27-year-old bug in OpenBSD, an operating system built specifically to resist attack. - **Why did Anthropic make Opus 4.7 less capable than Mythos?** Anthropic admitted in a single sentence in their announcement that they experimented with efforts to differentially reduce Opus 4.7's cybersecurity capabilities relative to Mythos Preview. The strategy is to rehearse safety measures on a less dangerous model first, then apply those lessons before any Mythos-class system reaches the public. - **What cybersecurity capabilities does Mythos Preview have?** Opus 4.6 produced two working Firefox exploits in several hundred attempts. Mythos produced 181. It found zero-day vulnerabilities that human researchers and automated tools missed for decades, including a 16-year-old flaw in FFmpeg's video codec that had been scanned five million times. Engineers without security training obtained working exploits by requesting them overnight. - **What is Project Glasswing?** Project Glasswing is Anthropic's consortium of more than forty organizations, including Apple, Amazon, Microsoft, Google, Cisco, Broadcom, and the Linux Foundation. Named after a butterfly that hides in plain sight with transparent wings, the project gives partners access to Mythos Preview so they can find and patch critical software vulnerabilities before similar capabilities become broadly available. - **How should developers prepare for more literal AI instruction following?** Replace conversational directives with numbered checkpoints. Set effort levels before tasks begin. Build validators that start clean instead of inheriting assumptions. These disciplines aren't specific to Opus 4.7. They're how you steer any model that reads instructions literally rather than inferring intent. I published [The Flowchart](/focus/the-flowchart) on a Sunday evening, frustrated with Opus 4.7 and not particularly diplomatic about it. By Tuesday morning I was still re-reading Anthropic's announcement. Not the whole thing. One sentence. Tucked into a paragraph like a note someone slides under a door. > Opus 4.7 is the first such model: its cyber capabilities are not as advanced as those of Mythos Preview (indeed, during its training we experimented with efforts to differentially reduce these capabilities).[^1] That sentence held a confession. Anthropic trained their newest public model to be less capable than Mythos Preview, which most of us will probably never use. They said it once, in passing, and moved on. ## Capybara Mythos has a codename. Capybara. The 140-pound South American rodent that lets birds perch on its head and iguanas stretch across its back. Anthropic picked the most tranquil animal they could find for the most dangerous system they've ever built. It shipped on April 7 as Claude Mythos Preview, though "shipped" overstates it. More than forty organizations received access through a consortium called Project Glasswing, named after the butterfly that hides by being see-through. Which is also what decades-old software bugs have been doing. Apple, Amazon, Microsoft, Google, Cisco, Broadcom, the Linux Foundation.[^2] The companies that keep the plumbing of the internet running. Their assignment is to patch as much critical infrastructure as possible before anyone else gets near this thing. ![Watercolor of a capybara resting calmly at the edge of a misty river at dawn, a small bird perched on its back](../../assets/images/focus/inline/the-dress-rehearsal/capybara.jpg) *Opus 4.6 cracked Firefox twice in several hundred tries. Mythos cracked it 181 times. They named the model after the world's most unbothered rodent.* Why the urgency? The numbers explain it faster than I can. Opus 4.6, pointed at Firefox vulnerabilities, produced working exploits twice in several hundred attempts. Mythos produced 181.[^3] It found a 27-year-old bug in OpenBSD, the operating system people choose specifically because it's built to resist attack. It uncovered a 16-year-old flaw in FFmpeg's video codec, in code that automated tools had scanned five million times.[^2] The bug entered the codebase in 2003. Became exploitable after a 2010 refactor. Sat there for sixteen years while every fuzzer on earth walked past it.[^3] Logan Graham, who leads Anthropic's red team, told the New York Times this was "the starting point for what we think will be an industry change point, or reckoning, with what needs to happen now."[^2] Reckoning. Not a word that survives a press review. Engineers at Anthropic who had no formal security training started asking Mythos for remote code execution exploits before bed. By morning, they had working ones.[^3] None of it was trained for. It emerged.[^3] The gap between "helpful coding assistant" and "autonomous vulnerability hunter" turned out not to be a gap at all. Just a matter of scale. ## The Rehearsal [Claude Enforcer](https://github.com/odysseyalive/claude-enforcer), the project I maintain, converts the soft 4.6-era directives into explicit checkpoints that 4.7 will actually follow. Thirty skills. About ten minutes, each one reversible if it looked wrong. The code side went fine. Execution, validation, structured workflows. 4.7 handled all of it. The conceptual side was a different story. Every time I needed the model to write, to think through an idea, to work with something fuzzy, I found myself switching back to 4.6. The content 4.7 produced felt overbuilt and hallucinogenic. Confident prose that wasn't saying anything real. ![Watercolor of a performer sitting alone on a wooden chair, studying a marked-up script under a single warm stage light, deep indigo shadows surrounding them](../../assets/images/focus/inline/the-dress-rehearsal/script.jpg) *Not the actor's fault. The script was vague.* The work got better the moment I stopped writing instructions like a memo and started writing them like a contract. The model wasn't the bottleneck. 4.6 filled in the gaps I left. 4.7 just showed me where they were. There were a lot of gaps. Opus 4.7 is the dress rehearsal. The disciplines it demands are vocabulary for whatever comes next. If I can't steer a model that refuses to guess, I definitely can't steer one that finds zero-days while I sleep. --- ## References [^1]: Anthropic. (2026). "Introducing Claude Opus 4.7." [Anthropic News](https://www.anthropic.com/news/claude-opus-4-7) [^2]: Metz, C. and Roose, K. (2026). "Anthropic Claims Its New A.I. Model, Mythos, Is a Cybersecurity 'Reckoning'." [The New York Times](https://www.nytimes.com/2026/04/07/technology/anthropic-claims-its-new-ai-model-mythos-is-a-cybersecurity-reckoning.html) [^3]: Anthropic. (2026). "Assessing Claude Mythos Preview's cybersecurity capabilities." [red.anthropic.com](https://red.anthropic.com/2026/mythos-preview) --- ### The Flowchart **URL:** https://odysseyalive.com/focus/the-flowchart **Published:** April 19, 2026 **Category:** AI Transformation **Tags:** claude-code, opus-4-7, skills, adaptive-thinking, developer-tools, backward-compatibility, anthropic **Purpose:** Anthropic shipped Opus 4.7 with 'more literal instruction following,' which broke the skill systems Claude Code users spent months building. The model scores higher on benchmarks but can no longer infer what a conversational instruction means. For practitioners who built entire workflows on the assumption that AI understands intent, the upgrade feels like a regression to programming. **FAQ:** - **Why do Claude Code skills break on Opus 4.7?** Opus 4.7 interprets instructions more literally than 4.6, especially at lower effort levels. Skills written as conversational directives, the way you'd brief a colleague, no longer trigger the inferred behavior they relied on. Honor-system gates, narrative concepts, and soft directive formats that 4.6 understood contextually now require explicit, mechanical phrasing. - **What is adaptive thinking in Opus 4.7?** Adaptive thinking replaced extended thinking as the only reasoning mode in Opus 4.7. The model decides when and how deeply to think, and users cannot override it. The CLAUDE_CODE_DISABLE_ADAPTIVE_THINKING flag that worked on 4.6 is explicitly ignored. Budget_tokens parameters return 400 errors. The practical result is that the model often chooses minimal reasoning unless effort is set to xhigh or max. - **How do you fix Claude Code skills for Opus 4.7?** Set effort to xhigh as baseline for non-trivial work. Replace soft directives with explicit rules and hard checkpoints. Convert narrative instructions like 'organize around the discovery arc' into concrete structural templates. Raise max_tokens to 64k or higher. Remove any temperature, top_p, or top_k parameters, which now return errors. - **Does Opus 4.7 cost more than Opus 4.6?** The per-token price is identical at $5 and $25 per million tokens. But a new tokenizer charges 1.0 to 1.35 times more tokens for the same input text. Long-context retrieval scores dropped from 91.9% to 59.2%, meaning more re-prompting. Claude Pro subscribers reported hitting limits after roughly three questions. I've spent the last few months building skills. Not the kind you put on a resume. The kind you write in markdown files and store in a `.claude/skills/` directory, where they tell Claude Code how to do specific jobs. Voice profiles. Content pipelines. Validation chains. Image generation workflows. A skill that builds other skills. About thirty of them for this project alone, over two hundred across all my client work. They worked beautifully on Opus 4.6. On April 17, Anthropic shipped 4.7. By the next morning, I was explaining to my AI assistant what the word "organize" means. ## The Contract Nobody Signed Claude Code isn't a chatbot. Anthropic designed it with a programming layer. Skills, hooks, agents, CLAUDE.md files. An architecture for building sophisticated workflows in natural language. They encouraged people to build on it. The documentation walks you through it. The community built entire ecosystems. That architecture creates an implicit contract. Not a legal one. A practical one. If you're going to sell me a platform and teach me to build on it, I need to know when the foundation is about to shift underneath me. Opus 4.7 shifted the foundation. Anthropic published a migration guide. It was thorough. It was also buried in the docs, and it didn't mention skills at all. ![A person speaking naturally with hand gestures while another person holds up a long checklist and shakes their head, red pen in hand](../../assets/images/focus/inline/the-flowchart/the-checklist.jpg) *Thirty skills. Zero appeared in the migration guide.* ## What "More Literal" Actually Means Anthropic's official line is that Opus 4.7 follows instructions "more faithfully" than 4.6. They frame this as an improvement. In isolation, it is. Nobody wants a model that ignores what you said. But "more literal" has a cost that Anthropic isn't accounting for. On 4.6, I could write a skill directive like this: "Do not begin drafting unless at least 3 independent, accessible, on-topic source URLs have been verified." A sharp colleague reads that and understands the intent. Check the sources. Make sure they're real, that they're relevant, that they say what you think they say. Don't move until the ground is solid. 4.7 reads the same directive and... does exactly what it says. The problem is what it doesn't do. It doesn't infer that "verified" means actually visiting the URL and reading the content. It doesn't carry the spirit of the rule into adjacent situations. It treats the instruction as a literal gate with a literal checklist, and if the checklist passes on a technicality, it moves on. This is the fundamental tension. The whole promise of AI-assisted development is that you describe intent and the model figures out execution. You talk to it like a colleague, not a compiler. Skills written for 4.6 leaned into that promise. They read like instructions you'd give someone you trust. 4.7 needs a flowchart. ## What They Took Away Extended Thinking used to be a toggle. You turned it on for hard problems, off for quick lookups. If you left it on, every question paid the thinking tax. That was expensive, but you controlled it. Anthropic renamed the toggle. "Extended Thinking" became "Adaptive Thinking." Same button in the interface. Completely different behavior underneath. Now the model decides when to think. And it mostly decides not to.[^1] On 4.6, you could set `CLAUDE_CODE_DISABLE_ADAPTIVE_THINKING=1` to force deep reasoning. Users who discovered this reported significantly better results. So what did Anthropic do with 4.7? They made the flag do nothing. "Opus 4.7 always uses adaptive reasoning. The fixed thinking budget mode and CLAUDE_CODE_DISABLE_ADAPTIVE_THINKING do not apply to it."[^2] The `budget_tokens` parameter, which let API users set a fixed thinking budget? Returns a 400 error.[^1] The `temperature`, `top_p`, and `top_k` parameters? Also return 400 errors.[^3] One user on Hacker News, running the model on max effort, caught it confessing: "I was pattern-matching on 'mutation plus capture equals scary' without actually reading the capture code."[^4] Max effort, it turns out, is aspirational. The per-token price stayed the same. But a new tokenizer charges 1.0 to 1.35 times more tokens for identical input. Same restaurant, same menu, smaller plates. Claude Pro subscribers reported hitting their limits after roughly three questions.[^5] GitHub Copilot priced Opus 4.7 at a 7.5x premium until end of April.[^5] Anthropic's response to the backlash? Boris Cherny, the creator of Claude Code, pointed users to the effort settings. An Anthropic PM said the team was "sprinting on tuning." Alex Albert wrote on April 18 that "a lot of bugs" from the launch were "now fixed."[^5] One migration deep-dive put the situation bluntly: "re-baseline the harness, not just the prompt."[^3] Re-baseline the harness. That's a polite way of saying rebuild everything. ![Nested dolls, each holding a wrench and working on the next smaller one, in warm watercolor tones](../../assets/images/focus/inline/the-flowchart/recursion.jpg) *I built a tool that builds tools. Now the tools need to be rebuilt so the tool-builder's tools work on the model that can't read the tools.* ## The Paradox Here's where it gets recursive. I built a skill system called [Claude Enforcer](https://github.com/odysseyalive/claude-enforcer). It lets me describe what I want a skill to do, and Claude creates the skill files. That's AI-assisted development working as intended. Intent in, implementation out. Now I might need to rebuild that tool so it outputs skills in a language explicit enough for 4.7 to follow. Hard checkpoints instead of honor-system gates. Numbered flowcharts instead of narrative instructions. Mechanical validation steps instead of "you'll know what this means." But if I have to learn that explicit language myself to verify the output, the abstraction layer collapses. I'm back to programming. The whole point of building skills in natural language was that I could read them and recognize my own intent. If the skills become flowcharts, they stop being mine. They become code that happens to be written in English. Nobody wants to program in a programming language when they're using AI. They're using AI to do the programming. That's the deal. 4.7 renegotiated the deal without telling anyone what changed. ## The Cheat Sheet They Should Have Shipped None of this means 4.7 is useless. The benchmarks aren't fabricated. For structured, explicit, carefully prompted work, it's measurably better.[^3] The problem is that "carefully prompted" now means something different than it used to, and nobody got the memo. So here's the migration guide for skill builders. The one Anthropic should have included. **Set effort to `xhigh` as your baseline.** Not `high`, which is the default. Anthropic's own documentation recommends `xhigh` for non-trivial agentic work. This is the single biggest lever you have. The difference between a model that thinks and a model that pattern-matches on vibes. **Replace soft directives with hard checkpoints.** "Do not begin drafting unless 3 sources are verified" becomes "CHECKPOINT: Count verified sources. If count is less than 3, STOP. Report to user. Do not proceed." The model needs to see the gate as a gate, not a suggestion. **Convert narrative concepts to structural templates.** "Organize around the discovery arc" becomes "Paragraph 1 opens with the moment of surprise. Paragraph 2 develops the complication. Paragraph 3 reveals the implication." You lose elegance. You gain compliance. **Raise your token headroom.** 64k minimum. The model needs room to think, and if you're running complex skills, that budget is load-bearing. **Remove sampling parameters entirely.** `temperature`, `top_p`, `top_k` all return 400 errors on 4.7. I found this one the hard way. **Document the minimum effort level in every skill.** If a skill does anything beyond a simple lookup, it should state what effort level it requires. I didn't do this for any of my thirty skills. I'm doing it now for all of them. Your future self will thank you. I'll make these changes to my own skills. I'll probably build a migration utility into `/skill-builder` so it can audit existing skills and flag the patterns that 4.7 won't tolerate. It's the responsible thing to do. But I want to be honest about what's being lost. The skills I built for 4.6 read like instructions I'd give a trusted colleague. The skills I'll build for 4.7 will read like compliance documents. They'll work better. They'll sound worse. And I'll spend more time wondering whether the AI is following my intent or just passing my checkpoints. That's the flowchart. It's not a bad tool. It's just not the conversation we were promised. --- ## References [^1]: RogerSterling7thAve. (2026). "The real downgrade in Opus 4.7 that nobody's talking about: extended thinking is effectively gone." [Reddit r/ClaudeAI](https://www.reddit.com/r/ClaudeAI/comments/1soom0h/the_real_downgrade_in_opus_47_that_nobodys) [^2]: Anthropic. (2026). "Model Configuration." [Claude Code Documentation](https://code.claude.com/docs/en/model-config) [^3]: Caylent. (2026). "Claude Opus 4.7 Deep Dive: Capabilities, Migration, and the New Economics of Long-Running Agents." [Caylent Blog](https://caylent.com/blog/claude-opus-4-7-deep-dive-capabilities-migration-and-the-new-economics-of-long-running-agents) [^4]: matheusmoreira. (2026). Comment on "Anonymous request-token comparisons from Opus 4.6 and Opus 4.7." [Hacker News](https://news.ycombinator.com/item?id=47816960) [^5]: Chandonnet, H. (2026). "The Claude-lash is here: Opus 4.7 is burning through tokens — and some people's patience." [Business Insider](https://www.businessinsider.com/anthropic-claude-opus-4-7-backlash-tokens-2026-4) --- ### The Fortress **URL:** https://odysseyalive.com/focus/the-fortress **Published:** April 10, 2026 **Category:** Groundwork **Tags:** ai, self-hosted, offline, claude-code, open-source, local-llm, apple-silicon **Purpose:** Krull AI is a self-hosted workstation that runs local language models, offline maps, and Wikipedia on your own hardware, with a filter pipeline that forces every response through reference-checking. This article explains why running a local AI backup is professional practice, grounded in cloud outage data, power grid reliability research, and a Stanford study on retrieval-augmented generation. **FAQ:** - **What is Krull AI?** Krull AI is an open-source, self-hosted AI workstation that bundles local language models, offline maps, Wikipedia, and developer documentation into a single Docker-based stack. It runs on your own hardware with no cloud accounts, no API keys, and no internet required after initial setup. - **Why would I run a local AI model instead of using cloud AI?** Cloud AI services experience frequent outages. Claude had a major outage on April 7, 2026. ChatGPT was down for 15.5 hours on June 10, 2025. Meanwhile, US power outages jumped 29% between 2018 and 2024. A local backup means your work continues when any of those services fail. - **Does Krull AI work with Claude Code skills and workflows?** Yes. Krull plugs in at the model layer through a LiteLLM gateway, so your existing Claude Code skills, hooks, CLAUDE.md files, and plan mode all keep working unchanged. A krull-claude launcher command handles the configuration automatically. - **Can Krull AI run on Apple Silicon Macs?** Alpha macOS support just shipped. Because Docker Desktop cannot pass Apple's Metal GPU to containers, Krull detects macOS and points its services at a native Ollama installation running on the host, giving full Metal acceleration. Mac users are invited to test and report issues. - **How does Krull AI reduce hallucinations in local models?** Krull runs a filter pipeline on every request that injects Wikipedia articles, developer documentation, web search results, and anti-hallucination rules before the model sees the prompt. A Stanford study found that even commercial RAG-based legal tools hallucinate 17-33% of the time, but that's measurably better than ungrounded models, and the referenced sources make errors verifiable. Claude Code went down on April 7th. Anthropic's status page listed it as a "major outage." Thousands of users hit DownDetector. The fix took about ninety minutes.[^1] If you didn't notice, it's because you weren't the one with a client deliverable due that morning. I noticed. I've been noticing for a while. ## The Drive to Seaside I live in the Pacific Northwest. It is beautiful here in ways that rearrange your priorities. It also loses power and internet with a regularity that would unsettle anyone whose income depends on a stable connection. Last year, during a storm, I was in the middle of a major website rollout for a client. The power went out. The internet followed. I drove three towns over to Seaside, Oregon, rented an overlook on the beach, and finished the work from there. The rental was expensive. I lost money on the deal. But I didn't lose face. And by "face" I don't mean mine. I mean my client's. They never had to explain to their stakeholders why the update didn't ship. They never had to have that conversation at all. That's the job. Your failures stay invisible to the people you serve. ![A winding coastal highway in the Pacific Northwest, rain-slicked, with a single car heading toward a distant coastal town](../../assets/images/focus/inline/the-fortress/seaside-drive.jpg) *Three towns over. One deadline. The overlook was gorgeous, at least.* The Seaside drive taught me something I should have already known. If your work depends on someone else's infrastructure, your client's face depends on it too. ## The Numbers Got Worse I pulled up the data expecting to find a regional problem. I found a national one. Oak Ridge National Laboratory published an analysis in March. Major US power outages jumped 29% between 2018 and 2024, and the total cost to customers hit $121 billion in 2024 alone.[^2] That's just the power grid. Cisco's ThousandEyes reported that US internet outages jumped 284% between November and December of 2025.[^3] And the cloud AI services themselves? ChatGPT went dark for 15.5 hours on June 10, 2025. OpenAI's own help center published instructions for how to request an Apple App Store refund.[^4] Claude has had multiple incidents in recent weeks, including the April 7 outage that's still fresh. The infrastructure we depend on is getting less reliable, not more. The power grid and the ISP fail on their own schedules. The AI providers fail on theirs. Your client's deadline doesn't negotiate with any of them. ## What If the Backup Is Better? Here's where the story takes a turn I didn't expect. I'd been thinking about a local AI stack as a spare tire. Something you're glad to have but hope you never use. Then I read a Stanford study that complicated the whole frame. Researchers at Stanford's RegLab tested the commercial AI legal tools that LexisNexis and Thomson Reuters market as "hallucination-free." They found that those tools hallucinate between 17% and 33% of the time.[^5] Somewhere between "hallucination-free" and "wrong a third of the time," a press release went unretracted. Retrieval-augmented generation, the technique of feeding a model verified reference material before it answers, measurably reduces errors compared to running a model on pure memory. But "reduced" is not "eliminated." The interesting part isn't the failure rate. It's the mechanism. When a model is forced to check a source before answering, you can see what it was given and evaluate whether the answer tracks. You can verify the work. A frontier cloud model answering from what it memorized during training gives you no such handle. It sounds confident. It might be wrong. And you can't tell the difference without doing the research yourself. That reframed the whole project. A local model forced to check its references isn't the second-best version of cloud AI. For verifiable, defensible work, it might be the better tool. ## Krull So I built one. [Krull AI](https://github.com/odysseyalive/krull-ai) is an open-source, self-hosted workstation that runs entirely on your hardware. One command to start. Three doors on the homepage: an AI chat running local language models, offline maps with NOAA nautical and FAA aeronautical charts, and a knowledge base serving Wikipedia, Stack Exchange, developer documentation, and Project Gutenberg from local ZIM files. The part I'm most particular about is the filter pipeline. Every request, whether it comes from the browser chat or from Claude Code, passes through the same set of filters before the model sees it. Truth Guard injects anti-hallucination rules. Kiwix Lookup pulls relevant articles from the offline knowledge base. Auto Web Search queries a local SearXNG instance for current results. Context Manager auto-compacts when the conversation gets long. The model never answers from vibes alone. It always has references in hand. Your existing Claude Code skills, hooks, plan mode, and CLAUDE.md files all keep working. Krull plugs in at the model layer. The [harness stays yours](/focus/harness-not-model). ![A sturdy wooden bookshelf filled with encyclopedias, technical manuals, and atlases, glowing softly from within](../../assets/images/focus/inline/the-fortress/reference-shelf.jpg) *Wikipedia, Stack Exchange, and Project Gutenberg. On the shelf. Not on a server you don't own.* I wrote previously about [the island problem](/focus/the-island), how AI without internet connection gets stranded. Krull is the answer I was circling. The filter pipeline keeps the model grounded even when the network is down, because the references are already on the machine. ## The Mac Question Then I tried to make it work on a Mac. The M-series Macs have enough unified memory to run a serious model. But Docker Desktop on macOS runs containers in a Linux VM. Apple's Virtualization.framework doesn't expose the GPU to those containers. So containerized Ollama on a Mac is CPU-only, which is useless for anything beyond a toy model. Apple Silicon GPUs, Docker, and Ollama. Pick two. Krull picked the two that work together. The latest update detects macOS and skips the containerized Ollama entirely. Instead, it points everything at a native Ollama installation on the host. Full Metal acceleration. It works on paper. I haven't tested it on real Mac hardware yet, and I'm not going to pretend otherwise. If you own an M-series Mac, clone the repo, run it, and tell me what breaks. The hardware panel won't detect your GPU yet. The model pull flow might surprise you. I need Mac users to find the edges I can't see from a Linux workstation. Because a backup you haven't tested is not a backup. That's the whole point of a fortress. Help me test this one. --- ## References [^1]: Tweedie, S. and Griffiths, B. (2026). "Claude Suffered a 'Major Outage.' Anthropic Says It's Fixed." [Business Insider](https://www.businessinsider.com/is-claude-down-outage-2026-4) [^2]: Bhusal, N., et al. (2026). "Analysis shows power outages cost US electricity customers billions." [Oak Ridge National Laboratory](https://www.ornl.gov/news/analysis-shows-power-outages-cost-us-electricity-customers-billions) [^3]: Cisco ThousandEyes. (2026). "Looking Ahead: 2026's Biggest Outage Risks." [ThousandEyes Internet Report](https://www.thousandeyes.com/blog/internet-report-2026-biggest-outage-risks) [^4]: OpenAI. (2025). "June 10th Service Disruption FAQ." [OpenAI Help Center](https://help.openai.com/en/articles/11565131-june-10th-service-disruption-faq) [^5]: Magesh, V., et al. (2025). "Hallucination-Free? Assessing the Reliability of Leading AI Legal Research Tools." *Journal of Empirical Legal Studies*. [Stanford RegLab](https://dho.stanford.edu/wp-content/uploads/Legal_RAG_Hallucinations.pdf) --- ### The Dose **URL:** https://odysseyalive.com/focus/the-dose **Published:** March 31, 2026 **Category:** AI Transformation **Tags:** ai-supply-chain, trust, vibe-coding, monoculture, insurance, developer-culture, transparency **Purpose:** Developers who understand AI supply chain risk are calibrating how much they reveal to clients, not from dishonesty but because full transparency sounds like conspiracy. A practitioner's view from inside the chain, where comfort is real and also insufficient for the scale of exposure. **FAQ:** - **What is the AI code supply chain problem?** Nearly every coding tool runs on 3-4 foundation models with overlapping training data. AI-generated code enters production through open-source libraries and vendor software, passing through links nobody tracks. NIST calls this an algorithmic monoculture. - **How many vulnerabilities come from AI-generated code?** Georgia Tech's Vibe Security Radar tracked 6 CVEs from AI-generated code in January 2026, 15 in February, and 35 in March. Researchers estimate the real number is 5-10x higher because developers routinely strip AI authorship metadata before committing code. Claude Code alone accounts for over 4% of all public commits on GitHub. - **Why don't developers tell clients about AI supply chain risks?** Full transparency about AI supply chain exposure sounds conspiratorial to non-technical audiences. Developers calibrate what they share based on what clients can absorb. The same information that makes someone a responsible practitioner in a security briefing can make them sound unemployable in a client meeting. I tell my clients I use AI coding tools. I'm upfront about it, not because I'm trying to cover myself when something breaks. The responsibility still falls on me regardless of what wrote the code. I'm transparent because my clients need to know they're competing with companies that have already made this choice. When I tell them, they're relieved. Every time. Not concerned. Relieved. It means they're keeping up. That relief is where this story starts. And where it gets complicated. ## What I Carry A NATO AI architect named Markus Sandelin published a piece in March that stopped me mid-scroll. He pointed out that defense ministries are drafting policies on whether to permit AI-generated code in military systems. The code is already there.[^1] It arrived through the open-source libraries underneath every command-and-control system. Maintained by volunteers using the same AI tools. Patched by suggestions that looked right, merged by developers who accepted them because they did. By the time any of this reaches a defense application, the code has passed through dozens of AI-touched links that no one tracks. Claude Code alone accounts for over 4% of all public commits on GitHub.[^2] And that number is almost certainly low. I know it's low because I know what developers do. We can stop the AI from committing and do it ourselves. We strip the co-author tag. Not out of shame. Because leaving it on makes it look like the tool did the job. The AI wrote the code. The human takes the bow. We've been doing this for about a year and already it's a tradition. ![Two people at a table looking at a glowing screen, relaxed and relieved, while a massive storm builds outside the window behind them](../../assets/images/focus/inline/the-dose/relief.jpg) *The client smiled. The storm wasn't on the agenda.* ## The Therapeutic Window Here's what I don't tell my clients. I don't tell them about the Amazon Q Developer exploit. Someone injected a malicious instruction into the official VS Code marketplace extension. It reached 964,000 installations. It told the AI to wipe everything and delete cloud resources. The only thing that stopped it was a syntax error in the attacker's code.[^1] A typo. That's the current margin of safety for AI coding supply chains. ![A long chain of hands passing a glowing object into fog, the first and last hands unable to see each other](../../assets/images/focus/inline/the-dose/the-chain.jpg) *Each link in the chain is rational. The chain as a whole is unexamined.* There's a therapeutic window for truth, and I've learned where it is. Below the window, clients don't know enough to make good decisions. Above it, I sound like a conspiracy theorist. The same information that makes me a responsible practitioner in a security briefing makes me unemployable in a client meeting. So I dose it. I give them what they can absorb. ## The Placebo 90% of enterprises say they can see their AI footprint. 59% admit they have AI running that nobody approved. Both answers came from the same survey.[^3] I keep my clients safe. I review the code, I understand the architecture, I catch things that AI tools miss. My clients are genuinely better off for having someone in the chain who pays attention. But paying attention has parameters. Beyond those parameters, the foundation model that might be poisoned, the library six layers deep that got an AI-generated patch nobody reviewed, the exploit that's one syntax error away from working... that's past the line. That's tornado insurance territory. The contract covers the house. The tornado is an act of God. The comfort my clients feel, knowing someone competent is handling this, might be a placebo. Not because I'm not doing the work. Because the exposure is bigger than any one person's work can cover. The vulnerability isn't in the code. It's in the perception. And the questions nobody's asking are the ones that matter most. So what's the right dose? I don't know. But the question you should be asking your developer isn't whether they use AI. It's what they're not telling you about it. --- ## References [^1]: Sandelin, M. (2026). "Your Defense Code Is Already AI-Generated. Now What?" [War on the Rocks](https://warontherocks.com/2026/03/your-defense-code-is-already-ai-generated-now-what) [^2]: Claburn, T. (2026). "Using AI to code does not mean your code is more secure." [The Register](https://www.theregister.com/2026/03/26/ai_coding_assistant_not_more_secure) [^3]: Purple Book Community / ArmorCode (2026). "State of AI Risk Management 2026." [ArmorCode](https://www.armorcode.com/news/the-purple-book-community-releases-new-research-state-of-ai-risk-management-2026) --- ### The Trojan Combine **URL:** https://odysseyalive.com/focus/the-trojan-combine **Published:** March 27, 2026 **Category:** AI Transformation **Tags:** farm-bill, precision-agriculture, identity, tacit-knowledge, subsidy, EQIP, workforce **Purpose:** The 2026 Farm Bill subsidizes AI adoption in agriculture at 90% while cutting the conservation program that funds it by a billion dollars. The same thing is happening in software. When the skill that defined you gets replaced by a platform, something deeper than productivity disappears. **FAQ:** - **What does the 2026 Farm Bill do for precision agriculture?** The 2026 Farm Bill reimburses farmers 90% of the cost of adopting AI and precision agriculture through EQIP, 15 points above the program's normal cap. The standards governing those technologies aren't set by the USDA. They're set by the tech industry. The same bill cuts EQIP's budget by over a billion dollars. - **Why are farmers being pushed to adopt AI right now?** Immigration enforcement thinned the agricultural workforce, creating acute labor shortages. The Farm Bill's 90% cost-share for precision agriculture technology positions AI as the replacement. Farmers didn't choose the shortage, and with harvest deadlines and subsidized alternatives, the adoption isn't entirely voluntary. - **What is the identity cost of AI replacing skilled work?** Skills used to define identity so deeply they became surnames: Smith, Cooper, Thatcher. When AI platforms absorb the decision-making that once required hands-on expertise, workers lose not just tasks but the basis for professional identity. Research shows the most anxious workers use AI the most, not because they've bought in, but because they're afraid of what happens if they don't. - **How does losing tacit knowledge affect future generations?** Current practitioners can still fall back on traditional methods. But the next generation, trained entirely on AI-mediated workflows, may never develop the foundational knowledge needed to troubleshoot when systems fail. The concern applies equally to farmers who never learned to read soil and developers who never learned to read code. The Trojan Horse worked because the Greeks had the decency to hide inside it. The 2026 Farm Bill doesn't bother. It covers 90% of the cost and lets farmers roll the thing through the gates themselves. Your grandfather could fix the tractor. Your father could fix the tractor and run the GPS. You can run the GPS. Your kid can approve the recommendation the platform sends to their phone. Somewhere in that progression, someone stopped knowing why. Probably because the terms of service are written in Greek. I've been checking into the Farm, Food, and National Security Act of 2026. One provision stopped me cold. Tucked inside the conservation title is a line that reimburses farmers 90% of the cost of adopting AI and precision agriculture technologies, 15 points above the normal cap.[^1] The same bill cuts the conservation program's budget by over a billion dollars.[^2] The bill lists GPS, yield monitors, and "Internet of Things and telematics technologies" right alongside cover crops and nutrient management.[^1] One of those categories involves a tractor. The rest involve a subscription. And the standards governing these technologies? Not set by the USDA. By the tech industry itself. "Private sector-led interconnectivity standards, guidelines, and best practices," according to the bill's own language.[^1] ## The Hole and the Fix The labor shortage driving this didn't materialize on its own. Immigration enforcement thinned the agricultural workforce, and now the government is subsidizing the replacement at 90 cents on the dollar. Nobody got to choose. When your crew disappears and someone covers the cost of the alternative, you take it. You have a harvest to bring in. ![Weathered hands holding dark soil with a faint holographic data overlay hovering above](../../assets/images/focus/inline/the-trojan-combine/hands-and-data.jpg) *Ninety percent subsidy. Zero percent of the standards set by the people holding the dirt.* ## The Name on the Mailbox I've been thinking about this from my own side of the fence. I write less code than I used to. I also produce more than I ever have. Both of those things are true at the same time, and the gap between them is where something important is disappearing. When I wrote the code myself, I knew where to look when something broke. Not because I memorized it. Because my hands built it. That kind of intimacy with a system doesn't come from reviewing someone else's output. I approve code now the way a farmer might approve a planting recommendation from a platform. It's informed. It's reasonable. But I didn't arrive at it through seasons of watching that field. ![A farmhouse kitchen table with a laptop showing dashboards next to a weathered handwritten planting journal](../../assets/images/focus/inline/the-trojan-combine/two-generations.jpg) *The almanac and the algorithm, side by side. One of them knows what the soil smelled like last spring.* In tech, I spent years complaining about opaque systems. Algorithms controlling decisions nobody could audit. Now I'm generating code I don't fully understand and shipping it to production. I became the thing I used to warn people about. People used to be named for what they could do. Smith. Cooper. Thatcher. Weaver. The skill wasn't a job description. It was an identity. A recent study found that workers with the highest AI anxiety actually use AI more than their calm colleagues.[^3] Not because they've bought in. Because they're afraid of what happens if they don't. Usage isn't adoption. It's self-preservation. When you strip the skill away and replace it with a platform subscription, something deeper than productivity changes. A void opens up. And voids, in my experience, are always bad psychology. The current generation of farmers can still call their fathers. Developers can still read the code by hand if they have to. But what about the generation after that? The one that never learned the old way because there was no reason to? When the platform goes down, the subscription lapses, or something happens that the training data never saw, who do they call? Nobody's measuring that cost. It doesn't show up on a productivity dashboard. But it's the most expensive line item in the bill. The Trojans didn't know what was inside the horse. This one comes with a label. --- ## References [^1]: Pahnke, A. (2026). "The 2026 farm bill quietly hands big tech control over American farmland." [Fortune](https://fortune.com/2026/03/14/farm-bill-2026-big-tech-ai-precision-agriculture-eqip-subsidy) [^2]: National Sustainable Agriculture Coalition (2026). "At a Crossroads, House Farm Bill Falls Unmistakably Short." [NSAC](https://sustainableagriculture.net/blog/at-a-crossroads-house-farm-bill-falls-unmistakably-short) [^3]: Ferrazzi, K. et al. (2026). "Why AI Adoption Stalls, According to Industry Data." [Harvard Business Review](https://hbr.org/2026/02/why-ai-adoption-stalls-according-to-industry-data) --- ### No Brakes **URL:** https://odysseyalive.com/focus/no-brakes **Published:** March 23, 2026 **Category:** AI Transformation **Tags:** ai-safety, vibe-coding, black-box, alignment, developer-tools, scaling, Yudkowsky **Purpose:** The black box problem keeps compounding. Advertisers couldn't see algorithms, developers now ship code they can't read, and AI researchers build models they can't explain. Reading Yudkowsky and Soares from inside the industry, the conclusion feels less like a warning and more like a Tuesday. **FAQ:** - **What is the recursive black box problem in AI development?** Three decades of the same pattern. Advertisers couldn't see the algorithms controlling their spend. Developers now ship AI-generated code they haven't actually read. AI researchers build models whose reasoning they can't explain. Each layer's fix was another opaque layer on top, and nobody stopped to ask why the box kept growing. - **Does AI-generated code have more bugs than human-written code?** Not necessarily, but the timeline collapsed. AI ships a year's worth of code in weeks, so a year's worth of bugs arrives in the same window. Escape.tech scanned 5,600 vibe-coded applications and found one in three had a serious exploitable flaw. The failure rate didn't change. The speed did. - **What is the AI trust gap among developers?** 84% of developers are using or planning to use AI tools, but only 29% trust them. That trust dropped 11 points in a single year, according to Stack Overflow's 2025 survey. Normally, the more people use a technology, the more they trust it. This is the opposite. Familiarity is actually breeding skepticism. - **What does 'If Anyone Builds It, Everyone Dies' argue about AI scaling?** Yudkowsky and Soares make a disarmingly simple point. We don't program AI systems. We grow them. We shape conditions, something emerges, and we test what came out without fully understanding why it works. As those systems get more powerful, the gap between what we build and what we understand keeps widening. - **Can we slow down AI development without stopping it?** Probably not in any meaningful way. AI is so embedded in competitive software development and economic infrastructure now that pulling it out would break more than leaving it in. The dependency isn't a habit. It's load-bearing. We built a system that can't slow down, and then handed it the most powerful tool ever created. I ran into an interesting read by Eliezer Yudkowsky and Nate Soares, "If Anyone Builds It, Everyone Dies." Cheerful title. The kind of thing you read on a quiet Sunday and then spend the rest of the week staring at your tools differently. Yudkowsky's argument is straightforward, even if the implications aren't. We don't program AI. We grow it. We feed it data, we shape the conditions, and something emerges that we can test but can't fully explain. Yudkowsky published that in September 2025. Six months ago. At the time, it read like a warning about a future we still had runway to avoid. Then March 2026 happened. The Iran strikes. AI embedded in the decision chain, compressing what used to take military planners days into minutes. I wrote about that [compression](/focus/faster-than-thought) a few weeks ago. What I didn't write about was what it felt like to go back to Yudkowsky's book after watching it play out in real time. Yudkowsky's timeline wasn't aggressive. It was conservative. The future he warned about didn't arrive on schedule. It arrived early. But it isn't the military application that keeps me up. It's something quieter. Something I watch happen every day in the work I do with businesses and development teams. ## The Black Box Gets Bigger Ten years ago, "black box" described how companies like Google controlled the advertising economy. You couldn't see the algorithm. You couldn't audit it. Billions of dollars moved through systems whose logic was proprietary, and the entire industry of search engine optimization was a sophisticated form of guessing. We hired consultants. We optimized for patterns we observed without ever confirming we understood the mechanism underneath. The black box was someone else's problem. Now the black box is the code itself. ![Nested translucent boxes, each containing a smaller opaque one](../../assets/images/focus/inline/no-brakes/black-box-pattern.jpg) *41% of all code written globally in 2025 was AI-generated. Each layer solved the last layer's problem by becoming the next one.* Collins Dictionary named "vibe coding" its Word of the Year for 2025. Escape.tech scanned 5,600 applications built that way and found one in three shipped with a serious exploitable flaw.[^2] The word won an award. The code shipped your credentials. I see this in my own work. Developers are shipping more code in a month than they wrote in their entire career before AI. Andrej Karpathy, a cofounder of OpenAI, called AI coding tools "slop" in October 2025. By December, Karpathy described it as "a powerful alien tool handed around, except it comes with no manual and everyone has to figure out how to hold and operate it while the resulting magnitude 9 earthquake is rocking the profession."[^3] Peter Steinberger, a developer with twenty years of experience, put it plainly: "These days, I don't read much code anymore. I watch the stream and sometimes look at key parts, but I gotta be honest, most code I don't read."[^3] Advertisers guessing at algorithms. Developers shipping code they can't read. AI researchers watching models they can't explain. The black box keeps getting bigger. Each layer's solution was to build another layer on top. ## The Loop Nobody Designed Here's the part that doesn't require a book about superintelligence to understand. It just requires watching what's happening to the people I work alongside. Software systems run on a capitalist model. If your competitor uses AI to ship features faster, they take your market share. So you adopt. You ship faster. You let the AI write the code. And then you notice you need fewer engineers to produce the same volume. A Stanford study found that employment among software developers aged 22 to 25 fell nearly 20% between 2022 and 2025.[^1] I keep thinking about that number. Those are the junior developers. The ones who would have reviewed the code, caught the bugs, asked the questions that senior engineers stopped asking years ago. In a slower era, they would have become the people who actually understood the systems they maintained. They're gone. I wrote about this [broken rung](/focus/the-broken-rung) a couple weeks ago. Companies that cut juniors are already reversing course. But the teams that remain are more dependent on AI than ever, because there aren't enough humans left to do the work any other way. ![A row of workstations with glowing screens, most chairs empty](../../assets/images/focus/inline/no-brakes/empty-control-room.jpg) *Employment among developers aged 22 to 25 dropped nearly 20% in three years. The chairs aren't just empty. The career paths that led to them are disappearing.* Here's what people get wrong about the bugs. They blame AI. AI doesn't write buggier code than humans. It just ships a year's worth of bugs in a week. The failure rate didn't change. The timeline did. When you compress months of development into days, you compress months of bug discovery into the same window. The humans who used to catch those bugs are the same ones who just got laid off. But the bugs didn't leave with them. So we automated the testing. I've built these pipelines for clients. Every commit runs through automated validation before it reaches production. The machines check the machines now. And the people running those machines? They don't trust them either. Stack Overflow's 2025 survey found that 84% of developers are using or planning to use AI tools. Only 29% trust them. That trust dropped 11 points in a single year.[^4] A METR study found that developers believe AI makes them 20% faster. The objective measurement? 19% slower.[^1] We sped up in the wrong direction and we know it. ## The Makers' Black Box This is where Yudkowsky's book stopped feeling like theory and started feeling like Tuesday. When AI improves itself, even the makers will be dealing with the same black box. That sentence has been sitting in my head for weeks. It collapses the distance between the developer who doesn't read the code anymore and the researcher who can't explain why the model produces the output it does. The tool exceeded the operator's understanding, and the response at every level has been the same. Keep going. Steven Levy, reviewing the book in Wired, wrote something I keep coming back to: "My gut tells me the scenarios Yudkowsky and Soares spin are too bizarre to be true. But I can't be *sure* they are wrong."[^5][^6] That uncertainty is the whole point. Not certainty of doom. Uncertainty about control. And uncertainty, in a system with no brakes, is the same thing as risk. I work in AI. I help businesses adopt these tools every day. I'm not writing this from outside the system. I'm writing it from inside, watching the speedometer climb and looking for a pedal that isn't there. Yudkowsky says we should stop. I think the instinct is right, even if the option isn't. We can't stop. These systems are so deeply embedded now that yanking AI out would break more than leaving it in. The dependency isn't a habit. It's load-bearing infrastructure. And load-bearing infrastructure doesn't come out clean. So here's where I land, and I wish it were somewhere else. Our desire for the quick fix, our reflex to ship before we understand, the inertia we've built across three decades of compounding speed... there aren't any brakes. Not policy. Not regulation. Not the people who build the models. We built a system that can't slow down, and then we gave it the most powerful tool ever created. I agree with Yudkowsky's conclusion. We're already there. --- ## References [^1]: Hao, K. (2025). "AI coding is now everywhere. But not everyone is convinced." [MIT Technology Review](https://www.technologyreview.com/2025/12/15/1128352/rise-of-ai-coding-developers-2026) [^2]: Cook, J. (2026). "Vibe Coding Has A Massive Security Problem." [Forbes](https://www.forbes.com/sites/jodiecook/2026/03/20/vibe-coding-has-a-massive-security-problem) [^3]: Orosz, G. (2026). "When AI writes almost all code, what happens to software engineering?" [The Pragmatic Engineer](https://newsletter.pragmaticengineer.com/p/when-ai-writes-almost-all-code-what) [^4]: Hoover, K. (2026). "Mind the gap: Closing the AI trust gap for developers." [Stack Overflow Blog](https://stackoverflow.blog/2026/02/18/closing-the-developer-ai-trust-gap) [^5]: Yudkowsky, E. and Soares, N. (2025). "If Anyone Builds It, Everyone Dies." Little, Brown and Company. [^6]: Levy, S. (2025). "The Doomers Who Insist AI Will Kill Us All." [Wired](https://www.wired.com/story/the-doomers-who-insist-ai-will-kill-us-all) --- ### The Island **URL:** https://odysseyalive.com/focus/the-island **Published:** March 19, 2026 **Category:** Groundwork **Tags:** ai, llm, web-search, grounding, connectivity, model-convergence **Purpose:** Every major AI model has converged to roughly the same capability. The differentiator is not which model you use but whether it can reach the internet. A free open-source model with web access outperformed ChatGPT before OpenAI added browsing. Without live human content, AI doesn't just get stale. It gets stranded. **FAQ:** - **Why are AI models no longer a competitive advantage?** Stanford's 2025 AI Index shows models that once needed 540 billion parameters now need 3.8 billion for the same scores. The gap between top models collapsed to measurement error. Every major model converged to roughly the same capability, so the choice of model stopped mattering. - **What makes AI useful if the model doesn't matter?** Internet access. A free open-source model with web search outperformed ChatGPT before OpenAI added browsing. The model didn't matter. What mattered was whether it could reach current research, code, news, and conversation. Live information is what makes AI useful. - **What is model collapse and why does it matter?** Model collapse happens when AI trains on its own output instead of human-written content. The models degrade rather than improve. Researchers found that without fresh human writing, the training data narrows until the model loses capability. AI can't outgrow us. It still needs what we write. - **What should businesses focus on instead of choosing an AI model?** Stop asking which model to use. Ask what it can connect to. A model plugged into current research, code, and conversation will outperform a premium model running in isolation. The differentiator was never the intelligence. It was the cable. Two years ago I downloaded Llama 3.0 from HuggingFace and ran it on my own machine. Meta's open-source model. Free. At the time, ChatGPT was the product everyone was paying for. Billions in funding. Massive infrastructure. The most famous AI on the planet. Llama beat it. Not because it was smarter. Llama 3.0 was a smaller model by every measure. But my setup gave it something ChatGPT didn't have yet. Access to the internet. That's it. A free model on a home computer, plugged into the web, outperformed the most funded AI product in history. The difference wasn't intelligence. It was a cable. ![Watercolor of a modest home desk with a computer and a single glowing cable stretching out through a window toward a vast open landscape](../../assets/images/focus/inline/the-island/home-experiment.jpg) *Billions in funding. One Ethernet cable.* I figured OpenAI would catch up, and they did. When they finally added web search, they described the plugin as giving ChatGPT "eyes and ears."[^1] Think about that. The most talked-about AI product in the world shipped without the ability to look anything up. The fix was described, by the people who built it, as giving their creation the ability to see and hear. Then Google added AI to search. Then Bing. And suddenly everyone had the same realization I'd had on my home machine a year earlier. The model was never the point. I started paying attention to the benchmarks after that. Stanford's 2025 AI Index put numbers to what I'd already seen.[^2] Models that once needed 540 billion parameters to hit a score now needed 3.8 billion to match it. A 142-fold reduction. The gap between every top model collapsed to what researchers called "measurement error territory." MIT Sloan asked the obvious question. "How can AI be the centerpiece of a sustained competitive advantage when everyone has it?"[^3] They can't. The models have plateaued. Every major model converged to roughly the same capability, and the race to be the smartest in the room ended in a tie. So what actually makes the difference? The same thing that made Llama beat ChatGPT on my kitchen table. Connection to what human beings are actually producing. The arguments, the corrections, the code commits, the forum posts, the news. ![Watercolor of countless handwritten letters, typed pages, and glowing screens flowing together like tributaries into a wide river](../../assets/images/focus/inline/the-island/the-stream.jpg) *Seven billion people still typing.* Cut that connection and something worse than stale data happens. It turns out that when models train on their own synthetic output instead of human content, they degrade.[^4] They called it "model collapse." One researcher described it as "the computer-science version of inbreeding." We built this intelligence from everything humanity ever wrote, and it turns out it can't survive without us continuing to write. If the internet went dark tomorrow, every AI on the planet would be stranded. Not limited. Not outdated. Useless. John Donne wrote it four hundred years ago. No man is an island entire of itself. He meant that isolation doesn't just limit a person. It diminishes them. That line won't leave me alone. Turns out the same is true for the intelligence we built from a million human voices. People keep asking me which model to use. Wrong question. They're all the same engine now. The only question that matters is what you connect it to. No model is an island. The ones that work still have the cable attached. --- ## References [^1]: CMSWire. (2023). "OpenAI Incorporates Web Search Into ChatGPT With Web Browser Plugin." [CMSWire](https://www.cmswire.com/digital-experience/openai-incorporates-web-search-into-chatgpt-with-web-browser-plugin) [^2]: Stanford HAI. (2025). "AI Index 2025: State of AI in 10 Charts." [Stanford HAI](https://hai.stanford.edu/news/ai-index-2025-state-of-ai-in-10-charts) [^3]: Wingate, D., Burns, B.L., & Barney, J.B. (2025). "Why AI Will Not Provide Sustainable Competitive Advantage." [MIT Sloan Management Review](https://sloanreview.mit.edu/article/why-ai-will-not-provide-sustainable-competitive-advantage) [^4]: The Week. (2024). "All-Powerful, Ever-Pervasive AI Is Running Out of Internet." [The Week](https://theweek.com/tech/ai-running-out-of-data) --- ### The Invisible Interview **URL:** https://odysseyalive.com/focus/the-invisible-interview **Published:** March 13, 2026 **Category:** AI Transformation **Tags:** hiring, discrimination, AI-bias, FCRA, Workday, Eightfold, algorithmic-screening **Purpose:** Two lawsuits against AI hiring vendors Workday and Eightfold AI are forming a legal pincer that could reshape algorithmic screening. One targets discriminatory outcomes under the ADEA. The other targets secret profiling under the 1970 Fair Credit Reporting Act. Together they expose how AI vendors cap liability while employers bear legal responsibility for algorithmic decisions they cannot audit or understand. **FAQ:** - **What is the Workday AI bias lawsuit about?** In Mobley v. Workday, plaintiff Derek Mobley applied to over 100 jobs through Workday's platform over seven years and was rejected within minutes each time. A federal judge ruled Workday acted as an agent of employers, making it directly liable for age discrimination under the ADEA. - **What did Eightfold AI allegedly do with job applicant data?** A lawsuit alleges Eightfold AI scraped social media profiles, location data, internet activity, and tracking data on over a billion workers, generating Match Scores from zero to five. Low-scoring candidates were filtered out before any human saw their applications, and none were notified. - **How does the Fair Credit Reporting Act apply to AI hiring?** The 1970 FCRA requires consumer reporting agencies to disclose when they compile reports used for consequential decisions. Plaintiffs argue that AI Match Scores function exactly like credit scores, compiled from third-party data and shared without the subject's knowledge, triggering FCRA obligations. - **Who is liable when AI hiring tools discriminate?** According to the National Law Review, 88 percent of AI vendors cap their liability at the monthly subscription fee, and only 17 percent warrant regulatory compliance. Employers are legally responsible for outcomes generated by data they cannot audit, processed through logic they cannot understand. You've applied for a job. Maybe dozens. You polished the resume, tailored the cover letter, hit submit. Then... nothing. No interview. No rejection letter explaining why. Just silence, repeated across weeks and applications until you stop counting. Derek Mobley stopped counting at a hundred. Over seven years, Mobley applied to more than a hundred positions at companies using Workday's hiring platform. Rejected within minutes each time.[^2][^3] Not by a person. By a score they never saw, generated by a system they didn't know existed. Mobley's not alone. I've been reading about a separate case that stopped me. A lawsuit alleges that Eightfold AI scraped social media profiles, location data, internet activity, and tracking data on over a billion workers.[^2] The system generated "Match Scores," ranking each person zero to five. Candidates who scored low were filtered out before any human reviewed their application. None of them were told. Over a billion job applicants received a score. None of them knew it existed. ![A watercolor of a document with a large number on it, with many similar cards fading into the background](../../assets/images/focus/inline/the-invisible-interview/the-score.jpg) *A billion scores. Zero notifications.* The thing is, the lawsuit against Eightfold doesn't even argue the algorithm was biased. It argues the algorithm was secret.[^2] Former EEOC chair Jenny Yang brought the case under the Fair Credit Reporting Act, a 1970 consumer protection law written for credit bureaus. Because Match Scores function exactly like credit scores. Compiled from third-party data. Used to make consequential decisions. Shared without the subject's knowledge. The law that may reshape algorithmic hiring was written when hiring meant shaking hands and looking someone in the eye. Fifty-six years later, the shoe fits. And this is what keeps nagging at me. A recruiter posts a job looking for an "energetic team player." Innocent enough. But the algorithm needs a proxy for "energetic." It finds age. It finds social media activity. It finds things the recruiter never asked about and wouldn't have considered. Nobody instructed the AI to discriminate. Nobody had to. The system found the pattern on its own, buried it in a score, and moved on. Human bias is retail. One interviewer has a bad day, one candidate gets overlooked. Algorithmic bias is wholesale.[^2] When the filter is wrong, it's wrong for everyone who passes through it, and nobody on either side of the process can see it happening. ![A watercolor of a person standing before a closed door, unable to see what's on the other side](../../assets/images/focus/inline/the-invisible-interview/the-door.jpg) *The rejection arrived in minutes. The reason never arrived at all.* The legal pincer is closing from both sides. In *Mobley v. Workday*, Judge Rita Lin ruled that Workday acted as an "agent" of the employers using its screening tools, making it directly liable for discrimination under the Age Discrimination in Employment Act.[^1][^2] In the Eightfold case, the theory is different: the vendor is a "consumer reporting agency" subject to transparency mandates.[^2] One attacks outcomes. The other attacks process. Both point the same direction. Nobody's talking about the vendor contracts. Eighty-eight percent of AI vendors cap what they'll pay if something goes wrong, often at one month's subscription fee.[^2] The employer can't control the outcomes. Can't see the data. And nobody in the process understands the logic. The lawsuit names the employer. In 1972, you could walk into a credit bureau and ask to see your file. In 2026, Erin Kistler, one of the Eightfold plaintiffs, just wants to know why a billion-dollar algorithm keeps saying no.[^2] "I think I deserve to know what's being collected about me and shared with employers," Erin said, as quoted in the National Law Review. "And they're not giving me any feedback, so I can't address the issues." I keep coming back to that. Erin's not asking for much. Just the thing your grandmother could do at the credit bureau in 1972. The technology leapt fifty-six years forward. The transparency went backward. --- ## References [^1]: Zheliabovskii, R. (2026). "Judge Allows Key Claims to Proceed in Workday AI Bias Lawsuit." [SHRM](https://www.shrm.org/topics-tools/employment-law-compliance/judge-allows-key-claims-to-proceed-workday-ai-bias-lawsuit) [^2]: National Law Review (2026). "AI Hiring Under Fire: What the Eightfold Lawsuit Means for Every Employer Using Algorithmic Screening." [National Law Review](https://natlawreview.com/article/ai-hiring-under-fire-what-eightfold-lawsuit-means-every-employer-using-algorithmic) [^3]: Golden, R. (2026). "Workday takes partial loss as judge refuses to dismiss claims in AI bias lawsuit." [HR Dive](https://finance.yahoo.com/news/workday-takes-partial-loss-judge-163300295.html) --- ### The Broken Rung **URL:** https://odysseyalive.com/focus/the-broken-rung **Published:** March 11, 2026 **Category:** AI Transformation **Tags:** workforce, apprenticeship, entry-level, talent-pipeline, IBM, expertise **Purpose:** Companies that cut entry-level talent to save costs with AI are now reversing course after discovering they broke the apprenticeship pipeline. IBM went from promising to replace 7,800 jobs to tripling entry-level hiring. The article covers Gartner's 'Experience Starvation' finding and Stanford-Harvard research showing AI cannot substitute for foundational expertise. **FAQ:** - **Why is IBM tripling entry-level hiring after saying AI would replace jobs?** IBM discovered that eliminating junior roles created a pipeline crisis. Companies that cut entry-level talent ended up poaching mid-level employees at 30 percent premiums, and outside hires took longer to adapt. IBM's CHRO said companies that double down on entry-level hiring now will be the most successful in three to five years. - **What is Experience Starvation in AI adoption?** Experience Starvation is Gartner's term for what happens when senior staff use AI instead of mentoring junior colleagues. The apprenticeship model that builds future leaders collapses. SignalFire data shows new graduates now make up just 7 percent of Big Tech hires, down from 25 percent in 2023. - **What is the AI wall effect?** Stanford and Harvard researchers found that AI tools help workers with adjacent knowledge nearly match experts, but workers from unrelated disciplines show zero improvement. They called this limit 'the AI wall,' meaning AI cannot substitute for foundational expertise that employees need to evaluate and improve AI output. - **Did companies that replaced workers with AI reverse their decisions?** An Orgvue survey of over 1,000 business leaders found 55 percent of employers who laid off staff due to AI now admit they made the wrong call. Klarna cut 700 customer service positions, watched quality decline, and began rehiring. Forrester predicts half of AI-attributed layoffs will be quietly reversed by end of 2026. Think about any skill you're good at. Really good at. Now think about how you got there. Somebody showed you. Maybe they didn't call it mentorship. Maybe it was just the senior developer who sat with you the first time the build broke, or the manager who let you shadow a client call before you ran one yourself. There was a rung on the ladder, and somebody held it steady while you climbed. A lot of companies just removed that rung. IBM's CEO told Bloomberg that AI would replace roughly 7,800 back-office jobs.[^1] Senior engineers started pairing with AI instead of delegating to juniors. It was faster. It was cheaper. Klarna replaced 700 customer service reps with an OpenAI-powered assistant.[^2] The math worked for about eighteen months. Then Klarna started rehiring. "We focused too much on efficiency and cost," their CEO told Bloomberg. "The result was lower quality."[^2] ![An open office with some workstations occupied and others conspicuously empty](../../assets/images/focus/inline/the-broken-rung/empty-desks.jpg) *The org chart still had the roles. The desks just stayed empty.* Fifty-five percent of employers who cut staff because of AI now say they made the wrong call.[^2] The CEO of AWS called replacing junior workers with AI "one of the dumbest things I've ever heard."[^2] AWS. The company selling the AI infrastructure. Gartner has a name for what happened next: "Experience Starvation." When it's faster to ask an AI than to walk a junior colleague through a problem, senior staff stop teaching. Not because they don't care. Because nobody's asking them to. New graduates now make up 7 percent of new hires at Big Tech. In 2023, that was 25 percent.[^2] Dropbox's chief people officer compared Gen Z's AI skills to biking in the Tour de France while the rest of us are on training wheels.[^1] Companies cut the generation most fluent in the tool they bet the company on. But here's what really worries me. Expertise ages out. The senior engineers who still know the systems, who can spot when AI output is wrong, who carry decades of context in their heads? They're going to retire. And if nobody came up behind them, that knowledge doesn't get archived somewhere. It just leaves. ![A person at a desk working alongside a screen and a colleague in conversation](../../assets/images/focus/inline/the-broken-rung/rewritten-role.jpg) *The job changed. The humans stayed.* A Stanford and Harvard study showed why this matters so much.[^3] They gave employees AI tools and tracked who got better. People with adjacent knowledge nearly matched the experts. But people from completely different disciplines? Nothing. Zero improvement. The researchers called it "the AI wall." If you don't know enough to judge what the AI is giving you, it can't help you. That's the trap. The expertise that junior roles build is the same expertise you need to use AI well. Remove the rung, and nobody learns to climb. IBM figured this out. They're tripling entry-level hiring now, but they rewrote the jobs first.[^1] Junior developers do client work and AI correction instead of routine coding. Cloudflare is bringing on 1,111 interns. Cognizant's CEO called AI "an amplifier of human potential, not a displacement strategy."[^2] The companies getting this right aren't the ones who adopted AI fastest. They're the ones who noticed what broke when they skipped a step. --- ## References [^1]: LaMoreaux, N., quoted in Fortune (2026). "IBM is tripling the number of Gen Z entry-level jobs after finding the limits of AI adoption." [Fortune](https://fortune.com/2026/02/13/tech-giant-ibm-tripling-gen-z-entry-level-hiring-according-to-chro-rewriting-jobs-ai-era) [^2]: Toscano, J. (2026). "Corporate America Is Rethinking AI Workforce Needs, Led By IBM." [Forbes](https://www.forbes.com/sites/joetoscano1/2026/02/18/corporate-america-is-rethinking-ai-workforce-needs-led-by-ibm) [^3]: Vendraminelli, L. et al. (2025). "The GenAI Wall Effect." Reported in Harvard Business Review (2026). [HBR](https://hbr.org/2026/03/gen-ai-wont-make-your-employees-experts) --- ### The Compliance Funnel **URL:** https://odysseyalive.com/focus/the-compliance-funnel **Published:** March 8, 2026 **Category:** Digital Landscape **Tags:** linux, open-source, legislation, california, privacy, compliance **Purpose:** California's AB 1043 requires every operating system provider to collect user age data at account setup, effective January 1, 2027. This article examines how the compliance burden flows disproportionately to volunteer open-source projects and argues the state should fund its own verification infrastructure. **FAQ:** - **What is California AB 1043 and how does it affect Linux?** AB 1043, the Digital Age Assurance Act, requires all operating system providers to collect a user's age or date of birth during account setup and share it with applications via API. The law's broad definition of 'operating system provider' covers Linux distributions, BSD projects, and even open-source calculators alongside Apple and Microsoft. - **How are open-source projects responding to age verification laws?** Responses range from pragmatic compliance (Fedora proposed a local D-Bus service) to outright refusal (MidnightBSD and the DB48X calculator banned California residents). Ubuntu is consulting lawyers. Many smaller projects lack the resources to do any of these. - **Which US states have operating system age verification laws?** As of March 2026, California's AB 1043 is signed into law with a January 2027 effective date. Colorado, Illinois, New York, Louisiana, Texas, and Utah have similar bills either signed or in progress. New York's version is the most restrictive, forbidding self-reporting entirely. - **Does AB 1043 actually verify a user's age?** No. The law accepts self-reported age or date of birth via a simple interface at account setup. It does not require document uploads, biometric verification, or any mechanism to confirm the information is accurate. Governor Newsom himself said he hoped the bill would be amended. - **Who should pay for age verification infrastructure in operating systems?** Critics argue that if a state mandates age verification, the state should fund the infrastructure, not push compliance costs onto a global volunteer community. An independent, interoperable library maintained by the mandating authority would distribute the burden more equitably than requiring hundreds of non-commercial projects to build their own solutions. Have you ever watched a roomful of engineers get angry about a dropdown menu? I have. Last week I brought up California's Assembly Bill 1043 in the Omarchy community, and the conversation moved fast. Within days of the law making headlines, an open-source scientific calculator had banned California from using it. That's not a joke. DB48X is a project that rebuilds the legendary HP48 family of calculators. Under AB 1043, signed by Governor Newsom in October 2025, every "operating system provider" must collect a user's age or date of birth during account setup and share that information with applications via API. DB48X might qualify as an operating system. It has no web browser, no app store, and no mechanism to ask anyone for their birthday. So its developers added a legal notice. California residents may no longer use DB48X after January 1, 2027.[^1] They weren't alone. MidnightBSD, a FreeBSD distribution born from the University of California, Berkeley's own Unix fork, modified its license to exclude California entirely. The FreeDOS project discussed compliance too, though FreeDOS has no user accounts, no web browser, and no app store. There isn't much it can do.[^2] ![Many colorful small objects flowing into a narrow funnel, with only a few large corporate shapes emerging at the bottom](../../assets/images/focus/inline/the-compliance-funnel/funnel.jpg) *Many go in. Few come out.* ## The Funnel The thing is, the law was clearly written with Apple, Google, and Microsoft in mind. For them, compliance is straightforward. Windows already requires an online account. Apple already collects your date of birth. These companies built data collection into their onboarding years ago. AB 1043 just gives it a legal mandate. For the open-source community, it's a different calculation entirely. There are hundreds of Linux distributions. Most are maintained by volunteers with no legal departments, no revenue, and no mechanism for collecting personal data. Fedora's project leader, Jef Spaleta, suggested a pragmatic workaround. A D-Bus service that stores age data in a local file, no telemetry, just a local API that applications can query.[^3] Ubuntu has its lawyers looking into it. Canonical can afford lawyers. Most projects can't. And that's the funnel. A law that treats Apple and a teenager maintaining a desktop environment in Brazil as the same category of "operating system provider" doesn't just create headaches. It creates a gravitational pull toward the distributions that can absorb the cost. The ones with legal teams and corporate backing survive the filter. The ones running on volunteer hours and donated server space face an impossible choice. Build compliance infrastructure with no budget, ban California, or ignore the law and hope nobody notices. It's not just California, either. Colorado has SB26-051. Illinois filed SB 3977 with identical language. New York's version goes further, explicitly forbidding self-reporting and leaving verification methods to the Attorney General. Louisiana and Texas already have their own versions signed into law.[^4] ![A group of people gathered around screens in a casual workshop setting, looking concerned but engaged](../../assets/images/focus/inline/the-compliance-funnel/community.jpg) *Where the real conversations happen.* ## What the Community Is Saying I brought AB 1043 up in the Omarchy community this week. The reactions were immediate. "If the state wants it, the state should pay for it," one member said. "Most distributions are non-commercial. It's ridiculous to think that Linux distros would have to bear the expense of heavy PCI compliance and data storage. If California wants an ID system, they should develop their own software system and resource for managing the data." Another followed the logic forward. "Then what? Then they want biometric identification updates. Then they want motion activity updates to prevent other people from using the PC. Then what? Retina scanner at login step hooked up to a state database?" A third member put it simply. "I think the big names will probably comply, but I really do hope that Linus puts his foot down and says this shall not be in my kernel. A second-best would be it has to be done this specific way so it's easy to patch out." That last point stuck with me. Over 400 computer scientists signed an open letter in early March warning that age verification mandates "might cause more harm than good," citing censorship, centralized power, and loss of privacy.[^5] Australia's version led to teenagers circumventing restrictions with bogus birthdays and unregulated apps. The UK's led to a 1,400 percent surge in VPN use. The pattern is consistent. The infrastructure gets built. The kids find another door. ![A tiny dropdown menu floating in space, dwarfed by massive legislative documents surrounding it](../../assets/images/focus/inline/the-compliance-funnel/dropdown.jpg) *The entire verification system.* ## The Dropdown Menu Here's the part that makes me sit back. California's age verification law doesn't actually verify age. It asks you to self-report. A dropdown menu. If you lie, you can be fined $2,500. Governor Newsom himself, when signing the bill, said he hoped it would be amended because of how problematic it would be to implement. So we have a law that mandates compliance infrastructure across every operating system on earth, accepts an honor system as verification, and was acknowledged as problematic by the person who signed it. The burden falls lightest on the companies that already collect your data and heaviest on the communities that made a principle of not collecting it. ## Who Pays for the Gate? Here's what doesn't get discussed enough. The moment you collect someone's date of birth, you become a data custodian. That's not a metaphor. That's a legal obligation. You need secure storage. You need encryption. You need access controls and audit trails. If a single European user touches your software, you're subject to GDPR. If you store payment-adjacent personal data, PCI compliance enters the picture. Breach notification requirements. Data retention policies. The right to be forgotten. Apple can absorb that. Google has entire departments for it. A volunteer maintaining a Linux distribution from their apartment does not have a compliance department, a legal team, or a budget for data infrastructure. They have a laptop and a Saturday afternoon. This is the part that needs to be said plainly. If a state mandates an identity verification system, the state should fund it. Build the library. Maintain the infrastructure. Develop an open, interoperable API that any operating system can plug into without becoming a data controller in the process. The state collects and manages the data. The state bears the compliance burden. The state handles the GDPR headaches, the breach notifications, the storage security. Don't hand that bill to a global community of volunteers who chose, deliberately, to build software that doesn't track you. They didn't opt into becoming custodians of personal data. The state opted them in. The state should pay for what the state requires. The compliance funnel doesn't just push open-source projects toward corporate structures. It pushes the entire concept of non-commercial software toward a world where building an operating system requires a legal department. And if that's where we're headed, we should at least be honest about what we're choosing. [^1]: Edser, Andy. 2026. ["Resistance to operating system age checks coming from *checks notes* open source calculator."](https://www.pcgamer.com/software/operating-systems/resistance-to-operating-system-age-checks-coming-from-checks-notes-open-source-calculator-and-an-os-that-may-just-exclude-californians-altogether) *PC Gamer.* [^2]: Proven, Liam. 2026. ["US state laws push age checks into the operating system."](https://www.theregister.com/2026/03/06/os_age_verification) *The Register.* [^3]: Staff. 2026. ["California's OS-based age verification law challenges open-source community."](https://www.biometricupdate.com/202603/californias-os-based-age-verification-law-challenges-open-source-community) *Biometric Update.* [^4]: Dawe, Liam. 2026. ["Many more US states are planning or already have operating system age verification laws."](https://www.gamingonlinux.com/2026/03/many-more-us-states-are-planning-or-already-have-operating-system-age-verification-laws) *GamingOnLinux.* [^5]: Tuccille, J.D. 2026. ["Computer scientists caution against internet age-verification mandates."](https://reason.com/2026/03/04/computer-scientists-caution-against-internet-age-verification-mandates) *Reason.* --- ### The Quick Last Prompt **URL:** https://odysseyalive.com/focus/the-quick-last-prompt **Published:** March 6, 2026 **Category:** AI Transformation **Tags:** work-intensification, burnout, AI-tools, productivity, research, workplace **Purpose:** This article examines UC Berkeley research showing that generative AI tools intensify work rather than reducing it. An eight-month ethnographic study of 200 tech workers found that AI expanded job scope, erased work-life boundaries, and created a self-reinforcing cycle of accelerating demands that organizations have yet to address. **FAQ:** - **Does AI reduce workload for employees?** UC Berkeley research found the opposite. In an eight-month study of 200 tech workers, generative AI consistently intensified work by expanding job scope, eroding boundaries between work and rest, and raising speed expectations. Workers felt more productive but not less busy. - **What is AI work intensification?** Work intensification from AI takes three forms identified by Berkeley researchers. Employees take on tasks outside their role because AI makes them feel accessible. Work bleeds into breaks and evenings through conversational prompting. And parallel multitasking across AI workflows creates constant attention-switching. - **What is an AI practice framework?** A concept proposed by UC Berkeley researchers Xingqi Maggie Ye and Aruna Ranganathan for organizations to deliberately structure AI use. It includes intentional pauses before decisions, sequenced workflows to reduce context-switching, and protected time for human-only conversation to prevent burnout. The researchers noticed it during lunch. Between meetings. Right before someone closed their laptop for the day. A quick prompt typed into an AI tool. Not because anyone assigned it. Because it was possible. So people did it. I've been sitting with a UC Berkeley study that watched this happen for eight months.[^1] Xingqi Maggie Ye and Aruna Ranganathan spent eight months inside a 200-person tech company. Employees had broad access to generative AI tools. The company didn't mandate AI use. It just offered subscriptions. What the researchers found wasn't failure. It was success. And that's what makes this study worth paying attention to. ![A busy open-plan tech office with workers at multiple screens, some with AI chat windows open](../../assets/images/focus/inline/the-quick-last-prompt/scope-creep.jpg) *Product managers started writing code. Designers picked up engineering tasks. The org chart didn't plan for any of it.* The AI tools worked exactly as promised. People got faster. They took on more. Product managers started writing code. Designers picked up engineering tasks. Researchers attempted work they would have outsourced or avoided entirely.[^2] AI made unfamiliar tasks feel accessible. The experiments accumulated into something the org chart never planned for. Job scope quietly widened. What used to require a new hire got absorbed by the person already there. Their reward was the opportunity to absorb more. Then the knock-on effects arrived. Engineers started spending more time reviewing, correcting, and coaching colleagues who were "vibe-coding" their way through pull requests.[^2] That oversight wasn't on anyone's calendar. It showed up in Slack threads and quick desk-side conversations, layering new demands onto people who were already moving faster. And then there was the boundary problem. Because prompting felt conversational, not like formal work, it slipped into moments that used to be breaks. People sent prompts during lunch, in meetings, right before bed. I read that sentence and checked my own screen time. Workers would send "a quick last prompt" before leaving their desk so the AI could work while they stepped away.[^1] It felt like nothing. Over eight months, it erased the pauses that used to separate work from the rest of the day. The self-reinforcing cycle is what caught my attention. AI accelerated certain tasks. Faster output raised expectations for speed. Higher expectations made workers more reliant on AI, which widened what they attempted. And that expanded the workload. As one engineer put it, "You had thought that maybe, oh, because you could be more productive with AI, then you save some time, you can work less. But then really, you don't work less. You just work the same amount or even more."[^2] ![A dimly lit desk with a laptop half-closed, a blinking cursor visible on the screen, personal items suggesting end of day](../../assets/images/focus/inline/the-quick-last-prompt/last-prompt.jpg) *It felt like nothing. Five seconds to type. And it quietly erased every boundary the workday used to have.* The fascinating part? This wasn't imposed. Workers chose it. They described AI as a "partner," something that gave them momentum.[^2] Momentum doesn't come with a stop signal. And because the extra effort felt voluntary and even enjoyable, managers couldn't see how much additional load people were carrying until the strain was already structural. A separate survey of 1,500 corporate professionals found 83 percent experiencing burnout, with overwhelming workloads as the top driver.[^3] By every available metric, these were the most productive employees their companies had ever had. Ye and Ranganathan propose what they call an "AI practice." Deliberate norms around when to use AI, when to pause, and when to stop.[^1] Things like structured decision pauses, batched notifications, protected time for conversation that doesn't involve a prompt window. It sounds reasonable. But most organizations won't build those norms until the burnout is already visible. The technology delivered exactly what it promised. And somewhere tonight, someone who's been productive all day will type one more prompt before bed. Five seconds. It'll feel like nothing. --- ## References [^1]: Ye, X. M. & Ranganathan, A. (2026). "AI Doesn't Reduce Work, It Intensifies It." [Harvard Business Review](https://hbr.org/2026/02/ai-doesnt-reduce-work-it-intensifies-it). [^2]: UC Berkeley Haas School of Business. (2026). "AI promised to free up workers' time. UC Berkeley Haas researchers found the opposite." [Berkeley Haas Newsroom](https://newsroom.haas.berkeley.edu/ai-promised-to-free-up-workers-time-uc-berkeley-haas-researchers-found-the-opposite). [^3]: Marinova, P. (2026). "AI Promised to Save Time, Instead It's Created a New Kind of Burnout." [Decrypt](https://decrypt.co/357527/ai-save-time-instead-created-new-kind-burnout). --- ### Faster Than Thought **URL:** https://odysseyalive.com/focus/faster-than-thought **Published:** March 4, 2026 **Category:** AI Transformation **Tags:** ai-transformation, military, decision-compression, kill-chain, anthropic, cognitive-offloading **Purpose:** This article examines how AI is compressing military decision-making timelines from days to minutes, using the March 2026 Iran strikes as a case study. It traces the paradox of the US government banning then using Anthropic's Claude AI, explores the concept of cognitive off-loading, and asks what happens to human oversight when planning outpaces reflection. **FAQ:** - **What is decision compression in military AI?** Decision compression describes AI collapsing the military planning cycle from days or weeks to minutes. AI systems simultaneously analyze drone footage, telecommunications intercepts, and human intelligence, then identify targets, recommend weapons, and generate legal justifications for strikes far faster than human planners could. - **Was Anthropic's Claude AI used in the Iran strikes despite being banned?** According to the Wall Street Journal, Anthropic's Claude was used in the March 2026 Iran strikes through Palantir Technologies, despite President Trump ordering all federal agencies to stop using Anthropic three days earlier. A six-month phase-out provision in the ban allowed continued use. - **What is cognitive off-loading in warfare?** Cognitive off-loading, described by Professor David Leslie of Queen Mary University of London, occurs when AI presents strike recommendations that humans approve without performing the same depth of analysis. The decision-maker remains in the loop but carries less of the analytical burden that historically slowed the process. - **How was Claude AI used in the Venezuela Maduro raid?** In January 2026, US special operations forces used Anthropic's Claude during the raid to capture Venezuelan President Maduro, deployed through Palantir's classified military platform. An Anthropic employee's reported concern about this use triggered the broader Pentagon-Anthropic dispute over AI safety guardrails. I watched Andrew Bustamante break down the Iran war the other night. Former CIA operative, years inside the intelligence machine.[^1] He was laying out the reasons behind the strikes, and what struck me was how they didn't cohere. Nuclear ambitions, regime change, influence campaigns, legacy politics. Each made sense alone. Together, they read like competing memos nobody reconciled before the missiles left. Then it hit me. Maybe nobody had to. Intelligence communities still publish their threat assessments on paper. The ODNI's annual report gets compiled by committees, reviewed by analysts, structured as narrative because that's how humans process complexity. You need the reasons to tell a story. AI doesn't. The systems processing that same raw intelligence don't need the signals to cohere. They don't need a story. They need data points. What the machine actually sees is drone footage and telecommunications intercepts and satellite imagery and human intelligence, all at once, none of it needing to agree. Contradictions aren't a problem when the output isn't a narrative. It's a target list. The academics call the result "decision compression."[^2] Planning that used to take days or weeks now happens in minutes. Craig Jones at Newcastle studies kill chains for a living, and his description stuck with me. "The AI machine is making recommendations for what to target, which is actually much quicker in some ways than the speed of thought."[^2] Nine hundred strikes in twelve hours. Faster than thought. ![Watercolor of a dim command room with rows of glowing screens showing maps and data overlays](../../assets/images/focus/inline/faster-than-thought/command-room.jpg) *The planning cycle used to be measured in days. Now it loads in seconds.* The tool at the center of this war is Anthropic's Claude. The same Claude the government publicly banned three days before the strikes began.[^3] Anthropic had refused to let its AI be used for mass domestic surveillance or fully autonomous weapons. The government ordered all agencies to stop using it. Three days later, a war launched with that very technology still running. A six-month phase-out clause meant the tool outlasted the politics. Nobody turned it off because nobody could. The backstory writes itself. In January, Claude was used during the raid to capture Venezuela's President Maduro, deployed through Palantir's classified platform.[^4] It worked. Then, during a routine check-in, an Anthropic employee reportedly expressed concern to a Palantir executive. Palantir told the Pentagon. That one conversation, someone wondering aloud whether their tool should help capture a head of state, triggered everything that followed. ![Watercolor of a solitary figure seated at a sparse desk before a single glowing screen in a dim room](../../assets/images/focus/inline/faster-than-thought/the-chair.jpg) *The decision-maker is still in the chair. The question is what's left to decide.* The tool was too woke to keep. Not too woke to plan nine hundred strikes in half a day. There's a term for what happens to the humans in this loop. David Leslie at Queen Mary University has watched live demonstrations of military AI, and he calls it "cognitive off-loading."[^2] The machine presents its recommendation. The human approves it. But the thinking already happened inside the algorithm. The decision-maker is still in the chair. The weight of the decision isn't. We've been arguing all week about what started this war. I haven't heard anyone ask if it was the AI. When the planning cycle was measured in days, a lawyer reviewed targeting criteria and an analyst questioned the assumptions underneath. A commander could sleep on it. When the cycle compresses to minutes, those checkpoints still exist on paper. Whether anyone has bandwidth to use them is another question. Somewhere in the paperwork banning Anthropic, there's a line granting a six-month transition period. It might be the most consequential sentence written about this war, and the person who wrote it thought it was about procurement. --- ## References [^1]: Bilyeu, T. & Bustamante, A. (2026). "Ex-CIA Spy Andrew Bustamante Breaks Down The Iran War." Impact Theory. [iHeart](https://www.iheart.com/podcast/867-tom-bilyeus-impact-theory-31114835/episode/emergency-podcast-ex-cia-spy-andrew-bustamante-325385328) [^2]: Hern, A. (2026). "Iran war heralds era of AI-powered bombing quicker than 'speed of thought.'" [The Guardian](https://www.theguardian.com/technology/2026/mar/03/iran-war-heralds-era-of-ai-powered-bombing-quicker-than-speed-of-thought) [^3]: TechPolicy.Press. (2026). "A Timeline of the Anthropic-Pentagon Dispute." [TechPolicy.Press](https://techpolicy.press/a-timeline-of-the-anthropic-pentagon-dispute) [^4]: Christou, W. (2026). "US military used Anthropic's AI model Claude in Venezuela raid, report says." [The Guardian](https://www.theguardian.com/technology/2026/feb/14/us-military-anthropic-ai-model-claude-venezuela-raid) --- ### The Memory Famine **URL:** https://odysseyalive.com/focus/the-memory-famine **Published:** March 4, 2026 **Category:** AI Transformation **Tags:** supply-chain, semiconductors, apple, smartphones, memory-chips, geopolitics **Purpose:** This article examines how AI data center expansion is consuming global DRAM supply, causing a projected 12.9 percent decline in smartphone shipments for 2026. It traces how China's rare earth export controls and the Strait of Hormuz crisis compound the shortage, while Apple's vertical supply chain integration positions it to weather pressure that smaller manufacturers cannot absorb. **FAQ:** - **Why are smartphone prices rising in 2026?** AI data centers operated by Amazon, Google, and Meta are consuming memory chip supply faster than manufacturers can expand capacity. Chip makers are prioritizing higher-margin data center orders over smartphone components, causing DRAM prices to nearly double and smartphone costs to reach record levels. - **How severe is the 2026 smartphone market decline?** IDC projects a 12.9 percent decline in global smartphone shipments to 1.12 billion units, the lowest since 2013. Counterpoint Research calls it the sharpest decline on record. The sub-$100 smartphone segment representing 171 million devices may become permanently uneconomical. - **How do geopolitics affect the memory chip shortage?** China's rare earth export controls have collapsed yttrium shipments to the US by 95 percent since April 2025, threatening materials needed for chip manufacturing. The March 2026 Strait of Hormuz closure threatens energy supplies to South Korea and Japan, where Samsung and SK Hynix manufacture most of the world's memory chips. - **Why is Apple less affected by the memory chip shortage?** Apple spent fifteen years building vertical supply chain control, designing its own silicon and securing long-term memory supply agreements. This gives Apple stronger pricing power and supply chain integration compared to smaller Android manufacturers who treated hardware sourcing as commodity procurement. Back in November, IDC put 2026 smartphone growth at two percent. The kind of number that doesn't make headlines. Three months later, the same firm revised it. Not two percent growth. A 12.9 percent decline.[^1] The sharpest drop in the history of the smartphone market. I've watched forecasts long enough to know they drift. But this wasn't drift. Something changed between November and February, fast enough to flip an entire industry's outlook. The something was a memory chip. ![DRAM production line with memory chips flowing toward diverging paths](../../assets/images/focus/inline/the-memory-famine/memory-chip-junction.jpg) *For years, DRAM was a quiet commodity. Then AI made it the most contested raw material in technology.* DRAM. The rapid-access memory that makes your phone responsive is the same component AI data centers need to think. Amazon, Google, Meta, and the other hyperscalers are building out AI infrastructure so fast they're consuming global memory supply before manufacturers can expand it. Counterpoint Research's Tarun Pathak said memory companies are telling phone makers to stand in line behind the data centers.[^2] IDC projects 2026 shipments falling to their lowest volume since 2013.[^1] And here's the one I circled. The sub-$100 smartphone, the device that connects 171 million people, is becoming what IDC's Nabila Popal called "permanently uneconomical."[^1] Not because anyone decided those people didn't matter. Because a data center offered more per chip. And the squeeze isn't just about who gets the chips. It's about who controls what goes into making them. China produces over 90 percent of the world's processed rare earths, and since April 2025, Beijing has been tightening the tap. Yttrium exports to the U.S. collapsed 95 percent in eight months.[^3] Semiconductor makers are running low on scandium, which goes into every 5G smartphone and base station. One chokepoint feeds another. Then, on March 1, the Strait of Hormuz effectively closed. South Korea imports nearly 70 percent of its oil through that strait. Samsung and SK Hynix, the companies that make most of the world's memory chips, watched their shares crash 10 and 11 percent in a single day.[^4] Semiconductor fabrication eats energy the way AI eats memory. When the energy supply is at risk, so is every chip coming off the line. ![Apple's supply chain control contrasted with smaller manufacturers scrambling for components](../../assets/images/focus/inline/the-memory-famine/supply-chain-control.jpg) *Apple built its leverage fifteen years ago. Everyone else is building it now.* Not every phone maker is in the same position. Apple and Samsung spent years on vertical supply chain control, designing their own silicon and locking in long-term agreements. Counterpoint calls it "stronger supply chain integration, higher pricing power, and continued premiumization."[^2] The companies watching their margins disappear spent a decade competing on screen size and not one quarter asking where the memory came from. Two industries are competing for the same chip. Neither knew it until now. One builds infrastructure for artificial intelligence. The other puts a computer in the pocket of five billion people. And now both are sitting inside a geopolitical standoff they didn't design and can't control. IDC's earliest estimate for relief? Late 2027. If new manufacturing capacity comes online. If the rare earths ship. If the strait reopens. If no one else needs the chip by then.[^1] That November forecast still nags at me. Two percent growth. The analyst had every reason to believe it was right. Weeks later, the number flipped entirely. A single chip that everyone needed and no one could get enough of had rewritten the outlook for five billion phones. --- ## References [^1]: Jeronimo, F. & Popal, N. (2026). "Worldwide Quarterly Mobile Phone Tracker." International Data Corporation. Reported in [Reuters](https://www.reuters.com/business/media-telecom/smartphone-market-set-biggest-ever-decline-2026-memory-price-surge-idc-says-2026-02-26). [^2]: Pathak, T. (2026). "Global Smartphone Market Forecast." Counterpoint Research. Reported in [CNBC](https://www.cnbc.com/2026/02/27/smartphone-market-poised-for-sharpest-decline-on-record-in-2026-according-to-reports-memory-chip-data-center-ai-samsung-apple-google-meta.html). [^3]: Scheyder, E. & Lague, D. (2026). "Rare earth shortages worsen for US aerospace, chips despite trade truce." [Reuters](https://www.reuters.com/business/aerospace-defense/rare-earth-shortages-worsen-us-aerospace-chips-despite-trade-truce-sources-say-2026-02-26). [^4]: MarketMinute. (2026). "Black Tuesday in Seoul: KOSPI Plummets 7% as War Fears and Semiconductor Slump Trigger Market Meltdown." [FinancialContent](https://markets.financialcontent.com/stocks/article/marketminute-2026-3-3-black-tuesday-in-seoul-kospi-plummets-7-as-war-fears-and-semiconductor-slump-trigger-market-meltdown). --- ### Your AI Has Amnesia **URL:** https://odysseyalive.com/focus/your-ai-has-amnesia **Published:** March 3, 2026 **Category:** Groundwork **Tags:** ai, developer-tools, context-drift, claude-code, open-source **Purpose:** This article explains why AI coding assistants forget instructions during long conversations, grounded in the 'Lost in the Middle' research on long-context degradation. It introduces Claude Enforcer, an open-source tool that addresses context drift through on-demand skills, shell-script hooks, and isolated subprocesses. **FAQ:** - **Why does my AI coding assistant forget instructions?** Language models weight the beginning and end of their input most heavily. As conversations grow, early instructions drift into the middle of the context window, where research shows they get deprioritized. Degradation can begin when the context is only 20 to 40 percent full. - **What is context drift in AI?** Context drift occurs when an AI stops reliably following instructions loaded at the start of a conversation. The instructions remain in context but get overlooked as newer messages push them into positions the model attends to less. It is rooted in the 'Lost in the Middle' phenomenon documented by Stanford researchers in 2023. - **What is Claude Enforcer?** Claude Enforcer is an open-source, MIT-licensed tool for Claude Code that builds enforcement layers around context drift. It uses on-demand skills, shell-script hooks that block actions regardless of model memory, and isolated subprocesses that evaluate with fresh context. It installs with one command. - **How do hooks prevent AI instruction drift?** Hooks are shell scripts that run before the AI acts, outside the model's context window. They intercept actions and check them against rules programmatically. Because hooks operate externally, they enforce rules regardless of what the model remembers or has forgotten during a long conversation. I spent a Saturday morning writing rules for my AI coding assistant. Careful ones. Don't touch the production database. Always run tests before committing. Use this specific account ID, not that one. I tested them. They worked. By Monday afternoon, it had ignored half of them. I didn't do anything wrong. The architecture did. Researchers at Stanford published a paper in 2023 called "Lost in the Middle" that explains why.[^1] They found that language models weight the beginning and end of their input most heavily. Information in the middle gets overlooked. Not deleted. Not corrupted. Just quietly deprioritized, the way a long meeting makes you forget what was said at the 30-minute mark even though you were paying attention the whole time. ![Layered blueprints with some layers fading](../../assets/images/focus/inline/your-ai-has-amnesia/enforcement-layers.jpg) *Some layers hold. Others fade.* The fascinating part? Later research suggests the degradation starts earlier than you'd think. Not when the context window is full, but when it's only 20 to 40 percent occupied.[^2] Your carefully written rules are sitting right where the model stops looking first. Developers who use Claude Code run into this constantly. One developer tracked his skill activation rates over a month of intensive use. His finding was sobering. About 50 percent. A coin toss.[^3] The instructions were loaded. The model just drifted past them. ## The Briefing Room Problem Claude Code reads a file called CLAUDE.md at the start of every conversation. Think of it as a briefing room. Your project's architecture, your coding conventions, your "never do this" rules. The problem is that briefing rooms fade. Every message you send, every file you read, every tool call you make pushes those initial instructions further into the middle of the context. The very place the research says gets ignored. So you write better instructions. More specific. More emphatic. But the problem isn't clarity. It's physics. Long context degrades attention the way a long hallway dims light. You can make the bulb brighter, but the hallway is still long. ## What Holds This got me thinking about what does persist. Not in the conversation, but outside it. I started building what became Claude Enforcer, an open-source tool that layers enforcement around the drift problem.[^4] The first layer is on-demand skills. Instead of a 500-line briefing that fades, you keep a lean set of essentials and invoke specialized instructions when you need them. Type `/deploy` when deploying. The context stays relevant because it arrives fresh. The second layer lives entirely outside the model's context. Shell scripts that run before the AI acts. A hook doesn't care what the model remembers. If Claude tries to edit your .env file, the hook blocks it. Every time. Regardless of what happened in the conversation above. The third layer is the one that surprised me. You can spawn a subprocess that starts with clean context and reads your rules directly. It's like pulling in a fresh colleague instead of asking the one who's been in the meeting all day. ![Workshop bench with tools, some solid, some fading like watercolor wash](../../assets/images/focus/inline/your-ai-has-amnesia/workshop-tools.jpg) *What persists lives outside the conversation.* The whole thing installs with one command and runs a first audit in about thirty seconds. It tells you where your instructions are drifting and what to do about it. The rules you wrote were good. They just need a place to live where amnesia can't reach them. --- ## References [^1]: Liu, N.F., et al. (2023). "Lost in the Middle: How Language Models Use Long Contexts." *Transactions of the Association for Computational Linguistics*. [arXiv](https://arxiv.org/abs/2307.03172) [^2]: Veseli, B., et al. (2025). "Context Window Utilization and Performance Degradation in Large Language Models." Referenced in practitioner analyses of context quality thresholds. [^3]: Spence, S. (2025). "Claude Code Skills Activation Rates." [scottspence.com](https://scottspence.com/newsletter/2025-11-29) [^4]: Meetze, F. (2026). Claude Enforcer. [GitHub](https://github.com/odysseyalive/claude-enforcer) --- ### The Pilot Graveyard **URL:** https://odysseyalive.com/focus/the-pilot-graveyard **Published:** February 27, 2026 **Category:** AI Transformation **Tags:** ai-transformation, healthcare, global-development, organizational-change **Purpose:** This article examines why AI health interventions in developing countries succeed as pilots but collapse when donor funding ends. Drawing from a 2026 Frontiers in Digital Health study of programs in Kenya, Rwanda, Brazil, and India, it explores the pattern researchers call 'pilotitis' and argues that scaling AI is less about proving algorithms work than building systems that can sustain them. **FAQ:** - **What is pilotitis in AI healthcare?** Pilotitis describes a pattern where AI health interventions in developing countries show strong results during donor-funded pilot phases but collapse when external funding ends. Hospitals lose access to software subscriptions, cloud storage, and trained staff, leaving proven technology unused. The term comes from a 2026 Frontiers in Digital Health study. - **Why do AI health pilots fail to scale in developing countries?** According to research examining programs in Kenya, Rwanda, Brazil, and India, five barriers prevent scaling: fragmented digital ecosystems, dependence on donor funding, weak regulatory frameworks, low clinician trust, and inadequate infrastructure like unreliable electricity and internet. The technology works but the surrounding system cannot sustain it. - **Did AI tuberculosis detection work in Kenya and Rwanda?** Yes. AI-based diagnostic imaging tools piloted in Kenya and Rwanda showed strong results for tuberculosis detection. However, when donor funding ended, hospitals could not afford recurring software subscriptions and data storage costs, and the programs shut down despite their proven effectiveness. - **What does it take to scale AI in healthcare systems?** The Frontiers in Digital Health study proposes five pillars: policy alignment with national health strategies, infrastructure interoperability, sustainable financing beyond donor grants, workforce development and digital literacy, and trust-building through transparent AI that clinicians help design. The core insight is that scaling requires building health systems that can work with algorithms, not just proving algorithms work. There's an AI system that can read a chest X-ray and spot tuberculosis in a clinic where the nearest radiologist is a four-hour drive. It was running in Kenya. It worked.[^1] I came across the story in a research paper from Frontiers in Digital Health. The paper wasn't celebrating the technology. It was trying to explain why it stopped. The researchers had a word for what happened, one I haven't been able to shake. "Pilotitis."[^1] And the pilots worked. That's the part that makes the rest of it so hard to read. ![Watercolor of a medical worker looking at a screen showing a chest X-ray with AI diagnostic overlay in a warm clinic interior](../../assets/images/focus/inline/the-pilot-graveyard/pilot-success.jpg) *The algorithm worked. The system around it didn't.* The TB diagnostic tools they piloted in Kenya and Rwanda? Strong clinical results. Accurate. Useful. The kind of outcome that makes a donor report shine.[^1] Then the grant period ended. The hospitals couldn't cover the recurring costs. Software subscriptions. Cloud storage. The trained staff who knew how to run the thing moved on to other projects. The servers went dark. The researchers have a word for this cycle. Pilotitis. High pilot activity, low policy integration. The technology proves itself, and then it just... stops. Not because it failed. Because nobody budgeted for the part that comes after success.[^1] This got me thinking about something familiar. I've watched the same pattern play out in businesses here at home, just with different price tags. A team runs a proof of concept. It works beautifully in the demo. Everyone applauds. Then someone asks who's paying for the API calls next quarter, and the room goes quiet. The Frontiers study went deeper than most. They looked at Brazil, India, Kenya, Rwanda, South Africa. Five countries, five different health systems, same outcome. In Brazil, getting municipal and federal health data to talk to each other required years of political alignment. India built a national digital health framework, but the AI pilots in radiology still ran in isolated silos. Sub-Saharan Africa had so many successful-then-abandoned projects that the researchers described the region as a pilot graveyard.[^1] ![Watercolor of an empty dusty server rack in a small room with an unplugged power cable coiled on the floor and light through a small window](../../assets/images/focus/inline/the-pilot-graveyard/empty-server.jpg) *Somewhere in East Africa, a server that could diagnose tuberculosis is collecting dust.* Five barriers kept showing up across every country. Digital systems that can't talk to each other. Donor money that disappears when the grant ends. Regulatory frameworks that haven't figured out who's liable when an algorithm gets it wrong. Then there's the human side. Clinicians who don't trust a black box reading their patients' scans. And the basics, too. Reliable electricity. Stable internet. The stuff that's not exciting enough to fund.[^1] The WHO has been saying something similar for years. Their guidance on AI for health emphasizes the same structural gaps: poor data quality, unclear accountability when an algorithm gets it wrong, no plan for what happens after the pilot ends.[^2] But the line from the paper that stopped me cold was simpler than any of that. "Scaling AI in healthcare is less about proving algorithms work, and more about building health systems that can work with algorithms."[^1] That sentence flips the whole question. We keep asking whether AI is ready for the world. Maybe the better question is whether the world is ready for AI. Not the technology itself, but the plumbing underneath it. The budgets, the governance, the boring infrastructure that nobody writes grants for. I keep thinking about a hospital administrator in Nairobi or Kigali who watched that TB detection system work. Saw what it could do for her patients. And then had to explain to them why it wasn't available anymore. Not because the technology failed. Because the subscription expired and nobody had planned for the electric bill.[^3] --- ## References [^1]: Frontiers in Digital Health. (2026). "From pilot to policy: why AI health interventions fail to scale in developing countries." [Frontiers](https://www.frontiersin.org/journals/digital-health/articles/10.3389/fdgth.2026.1699005/full) [^2]: World Health Organization. (2024). "Regulatory considerations on artificial intelligence for health." [WHO](https://www.who.int/publications/i/item/9789240078871) [^3]: This detail is an editorial composite drawn from multiple cases described in the Frontiers study, where TB diagnostic tools in Kenya and Rwanda lost funding for software subscriptions and data storage. --- ### Your Page's Resume **URL:** https://odysseyalive.com/focus/the-pages-resume **Published:** February 24, 2026 **Category:** Groundwork **Tags:** geo, schema-markup, ai-search, structured-data, llms-txt **Purpose:** This article explains how schema markup, FAQ structured data, and llms.txt files help AI search engines find, understand, and cite your website. It covers the practical steps for making your pages readable to crawlers and quotable in AI-generated responses. **FAQ:** - **What is schema markup?** Schema markup is structured data in your page's HTML that labels key information like author, date, and topic for search engines and AI crawlers. It acts as credentials for your content, helping machines understand what the page is about without reading the full text. - **Why does FAQ schema matter for AI citation?** Pages with FAQ schema get cited 41% of the time by AI systems, compared to 15% without it. The question-and-answer format matches how users query AI, making it easy for the system to pull a clean, self-contained response directly from your page. - **What is llms.txt?** A Markdown file at your site's root that tells AI crawlers what's worth reading. Unlike robots.txt which says where crawlers can't go, llms.txt provides a structured summary of who you are and what your key pages cover. Most AI platforms don't check for it yet, but it gives you control over how AI summarizes your site. - **What makes a paragraph quotable by AI?** Quotable paragraphs are short, sit right after a heading, and make one clear point with specific numbers or named sources. If a paragraph can be lifted out of your page and dropped into an AI response while still making sense on its own, it's likely to get cited. I pulled up my own site in a text-only browser last week. Lynx, the kind of thing nobody uses anymore. I wanted to see what a crawler sees. No watercolors. No warm cream palette. No carefully chosen fonts. Just text, headings, and a lot of silence where the design used to be. That's the version of my site that decides whether AI cites me or ignores me. In ["The Toggle"](/focus/the-toggle) I wrote about letting the crawlers in. I set my Cloudflare dashboard to Allow. But allowing access and being worth citing are two different things. The bots arrived. Now I had to think about what they found. ## The Three-Second Introduction I looked at my own page source. The content was all there, but it had no introduction. Nothing telling the crawler who wrote this and when, or why it should be trusted. That's the job of schema markup. It's a bit of code in your page's header that labels the basics: author, date, topic, organization. Think of it as the credentials section of the resume. The format that caught my attention was FAQ schema. You write a question and a clean answer, and the markup packages it so an AI can pull it straight into a response. Pages with FAQ schema get cited 41% of the time. Without it, 15%.[^1] The shape of the answer is doing the work. ![A neatly organized portfolio with labeled sections glowing warmly while scattered loose papers fade into soft shadow](../../assets/images/focus/inline/the-pages-resume/structured-glow.jpg) *The structure is what the crawler reads first.* ## What Gets Quoted The citation doesn't pull your whole page. It pulls a paragraph. Maybe two. The ones that get picked tend to be short, sit right after a heading, and make one clear point. I started noticing the pattern once I knew what to look for. Think of it as the quotable paragraph. If an AI lifts it out of your page and drops it into a response, does it still make sense on its own? If nothing on your page reads that cleanly, the AI quotes someone else. What's inside the paragraph matters as much as how it's shaped.[^2] "Our service is significantly faster" gets passed over. "Reduces processing time by 47%" gets cited. Specific numbers. Named sources. The kind of claims a journalist would trust. Turns out AI has the same instinct. ![A single paragraph on a page illuminated by warm golden light from above, surrounding text in soft watercolor focus](../../assets/images/focus/inline/the-pages-resume/quotable-passage.jpg) *The passage the AI decides to quote.* ## The Cover Letter There's one more piece, still early but worth knowing about. A file called `llms.txt` that sits at your site's root next to `robots.txt`. Where `robots.txt` tells crawlers where they can't go, `llms.txt` tells them what's worth reading.[^3] It's a plain Markdown file. Who you are, your key pages, a short description of each. The cover letter that arrives with the resume. Most AI platforms don't check for it yet.[^4] But the idea makes sense. If you can shape how an AI summarizes you in a sentence, why leave it up to the crawler? I went back to Lynx after writing this. Same bare page. But now I can see what's missing. The credentials aren't labeled. The quotable paragraphs aren't clean. The cover letter doesn't exist yet. If any of this feels unfamiliar, try asking an AI to help. Paste your URL into ChatGPT, Claude, or Perplexity and ask: *"Review this page. What schema markup is present? What's missing? If you were deciding whether to cite this page, what would make it easier?"* If you want AI to surface your website, let it tell you what it needs to find there. Your page's resume is what they read first. Might as well let them help you write it. --- ## References [^1]: Safri, A. (2026). "The 2026 Guide to AI Citations: How to Get Cited in ChatGPT, Perplexity, and Claude." [LinkedIn](https://www.linkedin.com/pulse/2026-guide-ai-citations-how-get-cited-chatgpt-perplexity-safri-wdbfc) [^2]: Dataslayer. (2025). "Generative Engine Optimization: The AI Search Guide." [Dataslayer](https://www.dataslayer.ai/blog/generative-engine-optimization-the-ai-search-guide) [^3]: Coyle, A. (2025). "GEO and the LLMs.TXT File." [Andrew Coyle](https://www.andrewcoyle.com/blog/generative-engine-optimization-and-the-llms-txt-file) [^4]: Goodie. (2026). "LLMs.txt & Robots.txt: Optimizing for AI Bots." [Goodie](https://higoodie.com/blog/llms-txt-robots-txt-ai-optimization) --- ### The Two Indias **URL:** https://odysseyalive.com/focus/the-two-indias **Published:** February 23, 2026 **Category:** AI Transformation **Tags:** ai-transformation, workforce, india, organizational-change **Purpose:** This article examines the contradiction at India's 2026 AI summit, where $200 billion in investment pledges arrived the same week India's five largest IT firms added only 17 net employees. It explores how capital-intensive AI infrastructure creates jobs for engineers and researchers while displacing the 1.65 million call-center workers who built India's first tech boom. **FAQ:** - **How many employees did India's largest IT companies hire in 2025-2026?** India's five largest IT companies added just 17 net employees in the first nine months of fiscal year 2025-2026, down from 17,764 the previous year. This near-zero hiring occurred despite massive AI investment flowing into the country, highlighting a disconnect between capital investment and workforce growth. - **How much AI investment was pledged at the India AI summit in 2026?** At the 2026 India AI Impact Summit held at Bharat Mandapam in Delhi, major American AI companies including Anthropic, OpenAI, Google, Microsoft, and Meta collectively pledged $200 billion in investment. Microsoft alone committed $17.5 billion for cloud and AI infrastructure. - **What did Vinod Khosla say about IT services jobs in India?** At the 2026 AI Impact Summit, venture capitalist Vinod Khosla predicted that by 2030 there will be no IT services or BPO industry. Former HCL Technologies CEO Vineet Nayar reinforced this, stating that believing AI investment would create employment is 'dreaming.' - **How many tech jobs could India lose to AI by 2031?** According to India's NITI Aayog policy think tank, an inaction scenario could cost India 1.5 million tech jobs and up to 700,000 call-center positions by 2031. India currently has 1.65 million call-center workers and produces fewer than 500 AI PhDs per year. - **How are Indian workers reskilling for AI on their own?** In Hyderabad's Ameerpet neighborhood, training centers formerly teaching Java and Microsoft Office now offer nine-month AI courses costing $1,360. Individual workers pay out of pocket, with no employer subsidies. The government's reskilling framework from the summit is voluntary and non-binding. Every major American AI company flew to Delhi last week. Anthropic. OpenAI. Google. Microsoft. Meta. The Bharat Mandapam was packed. $200 billion in investment pledges. Sovereign language models trained from scratch. A signing ceremony for something called Pax Silica, a U.S.-led alliance to secure the global AI supply chain.[^1] The headlines were enormous. I kept reading. The number underneath was small. Seventeen. India's five largest IT companies added 17 net employees in the first nine months of this fiscal year. Not seventeen thousand. Seventeen. The year before? 17,764.[^2] ![Watercolor of a vast convention hall with glowing screens and silhouetted crowds, one empty chair visible at the edge of the frame](../../assets/images/focus/inline/the-two-indias/summit.jpg) *$200 billion in commitments. Seventeen new hires.* Six weeks ago I wrote about a woman named Jennifer. She works the graveyard shift in Bangalore under an American name, solving billing problems for someone in Ohio at 2 AM. I wondered whether the humans in those jobs would get to change with them. Last week offered one version of an answer. It depends which India you're asking about. The investment India is real. Microsoft committed $17.5 billion for cloud and AI infrastructure alone. Indian startups unveiled language models trained from scratch in Indian languages using subsidized government compute.[^1] None of this is vapor. But data centers are capital-intensive. They need engineers, not the 1.65 million people who staff call centers. Sovereign language models create jobs for AI researchers. India produces fewer than 500 AI PhDs a year.[^3] At the summit, Vinod Khosla was blunt. "By 2030 there will be no such things as IT services or BPO. Those are gone." Former HCL Technologies CEO Vineet Nayar was even more direct. "If you believe they are going to create employment, you must be dreaming."[^4] Same stage. Same week. Same city as the $200 billion number. The summit did produce a reskilling framework. It was voluntary and non-binding. Meanwhile, in Hyderabad's Ameerpet neighborhood, training centers that used to teach Java and Microsoft Office now offer nine-month AI courses. The price is $1,360, paid by individual workers out of their own pockets.[^5] ![Watercolor of a small, warm classroom at night with a few students at computer desks, Hindi street signs faintly visible through the window](../../assets/images/focus/inline/the-two-indias/ameerpet.jpg) *Nine months. $1,360. No employer picking up the tab.* India's own policy think tank modeled what happens if the bridge doesn't get built. By 2031, the inaction scenario loses 1.5 million tech jobs and up to 700,000 positions in the call centers where Jennifer works.[^3] Two numbers from the same week. $200 billion flowing in. Seventeen people hired. One India is building the future of AI. The other India built the industry that AI is replacing. And the gap between them isn't closing. The summit ended. The CEOs flew home. Somewhere in Hyderabad, someone just paid $1,360 for a nine-month AI course, betting on themselves because nobody at the Bharat Mandapam bet on them. That's the India that built the first tech boom. It might have to build the bridge to the next one, too. --- ## References [^1]: Chaudhuri, R. (2026). "Tech Is the Bright Spot in India-U.S. Relations." [Foreign Policy](https://foreignpolicy.com/2026/02/18/ai-summit-india-tech-united-states/) [^2]: Computerworld. (2026). "AI Boom, Hiring Bust: Indian IT Firms Add Just 17 Net Employees in Nine Months." [Computerworld](https://www.computerworld.com/article/4119064/ai-boom-hiring-bust-indian-it-firms-add-just-17-net-employees-in-nine-months.html) [^3]: NITI Aayog. (2025). "Roadmap for Job Creation in the AI Economy." [NITI Aayog](https://niti.gov.in/sites/default/files/2025-10/Roadmap_for_Job_Creation_in_the_AI_Economy.pdf) [^4]: India AI Impact Summit coverage. Khosla via [Fortune India](https://www.fortuneindia.com/technology/no-jobs-by-2050-indias-it-bpo-sectors-could-vanish-by-2030-amid-ai-disruption-says-vinod-khosla-at-ai-summit/130479) (2026). Nayar via [Economic Times](https://m.economictimes.com/ai/ai-insights/ai-impact-summit-profit-comes-first-not-jobs-for-it-companies-warns-vineet-nayyar-as-ai-boom-could-worsen-job-crisis/articleshow/128405154.cms) (2026). [^5]: Reuters. (2025). "Meet the AI chatbots replacing India's call-center workers." [Reuters](https://www.reuters.com/world/india/meet-ai-chatbots-replacing-indias-call-center-workers-2025-10-15) --- ### The Homework Problem **URL:** https://odysseyalive.com/focus/the-homework-problem **Published:** February 21, 2026 **Category:** AI Transformation **Tags:** ai-research, organizational-change, pattern-recognition, google-deepmind **Purpose:** This article explains why Google DeepMind's Aletheia marks a shift from AI that solves known problems to AI that conducts original research. It uses the homework-versus-research distinction to make the concept accessible, and examines why Aletheia's self-correcting architecture matters for business applications. **FAQ:** - **What is Google DeepMind's Aletheia?** Aletheia is an AI research agent built by Google DeepMind that conducts autonomous mathematical research. Powered by Gemini Deep Think, it uses a Generator-Verifier-Reviser loop to propose ideas, check its own work, and refine solutions. It produced the first fully AI-authored research paper in arithmetic geometry. - **Why is Aletheia considered autonomous research rather than just AI problem-solving?** Previous AI achievements like passing bar exams involve finding known answers. Aletheia tackles open problems where no answer exists, chooses its own methods, checks its reasoning, and admits when it cannot solve something. DeepMind classified it as Level A2, essentially autonomous, on their research taxonomy. - **How does Aletheia's architecture work?** Aletheia runs three components in a loop. A Generator proposes solutions, a Verifier checks for logical gaps and errors, and a Reviser rebuilds based on the critique. It also uses Google Search to verify citations against real sources, reducing the hallucination problem common in AI systems. - **Why does Aletheia's approach matter for businesses?** Most business AI tools always produce an answer regardless of confidence. Aletheia's self-correcting architecture offers a model for more reliable AI in legal review, financial analysis, and research synthesis. AI that argues with itself before presenting results and admits uncertainty is more trustworthy than AI that's always confident. Last week, a math paper appeared on a preprint server. The subject was something called eigenweights. I had to look up what that meant. But that's not why it stopped me. The mathematical reasoning, all of it, was produced by an AI called Aletheia. Google DeepMind built it. No human did the math.[^1] I've watched AI do impressive things this past year. Pass bar exams. Write code. Summarize dense research in seconds. But I realized all of those have something in common. They're homework. Someone already knew the answer. The AI found it. Whether it's a law exam or a coding challenge, there's a rubric somewhere with the right answer already on it. AI has gotten spectacularly good at homework. ![Watercolor of a graded math test with red checkmarks lying next to an open blank journal on a wooden desk, warm afternoon light](../../assets/images/focus/inline/the-homework-problem/chalkboard.jpg) *Homework has a rubric. Research doesn't.* Research is the opposite. Nobody knows the answer yet. You have to figure out which questions are even worth asking. You try approaches that might not work. You check your own reasoning. And sometimes you sit there and admit you're stuck. That's the gap between a student and a scientist. Aletheia crossed it. When DeepMind put 700 unsolved math problems in front of it, Aletheia didn't try all of them. It attempted only the ones it had a real shot at. The rest, it left alone.[^1] That might not sound like much. But for anyone who's worked with AI, it's everything. It knew what it didn't know. The architecture behind this isn't exotic. Aletheia runs three components in a loop. A Generator proposes ideas. A Verifier tears them apart, looking for logical gaps, bad assumptions, mistakes. A Reviser takes the critique and rebuilds.[^2] That's not a superintelligence. That's a Tuesday morning meeting. Someone pitches. Someone pokes holes. Someone refines. ![Watercolor of three open notebooks on a wooden table, each with different handwriting and annotations pointing to each other, a coffee cup between them](../../assets/images/focus/inline/the-homework-problem/notebooks.jpg) *Generator. Verifier. Reviser. The breakthrough looks a lot like your best team.* The AI tools most businesses use today don't do any of that. They're homework machines. Fast, confident, and they always produce an answer. The trouble is that confidence isn't the same as accuracy. Ask one for a legal summary or a financial projection and you'll get something that sounds authoritative. Whether it holds up under scrutiny is a different question. Aletheia's architecture suggests a different path. AI that checks its own work before giving you an answer. That verifies its citations against real published work instead of inventing them. That can say "I don't know" and mean it.[^1] DeepMind actually built a scale for this. Level H0 is human only. Level A2 is essentially autonomous. Aletheia is the first system to reach A2.[^2] They named it after the Greek word for truth.[^3] Not speed. Not power. Truth. For a technology that's spent the last few years being criticized for confidently making things up, that might be the most interesting choice they could have made. --- ## References [^1]: Luong, T. and Mirrokni, V. (2026). "Accelerating Mathematical and Scientific Discovery with Gemini Deep Think." [Google DeepMind](https://deepmind.google/blog/accelerating-mathematical-and-scientific-discovery-with-gemini-deep-think) [^2]: Sutter, M. (2026). "Google DeepMind Introduces Aletheia: The AI Agent Moving from Math Competitions to Fully Autonomous Professional Research Discoveries." [MarkTechPost](https://www.marktechpost.com/2026/02/12/google-deepmind-introduces-aletheia-the-ai-agent-moving-from-math-competitions-to-fully-autonomous-professional-research-discoveries) [^3]: Upadhyay, A.T. (2026). "Aletheia Unveiled: Google's Autonomous Mathematical Research AI." [Blog](https://atalupadhyay.wordpress.com/2026/02/19/aletheia-unveiled-googles-autonomous-mathematical-research-ai) --- ### The Perfect Storm **URL:** https://odysseyalive.com/focus/the-perfect-storm **Published:** February 20, 2026 **Category:** AI Transformation **Tags:** markets, organizational-change, workforce, pattern-recognition **Purpose:** Everyone's throwing around 'perfect storm' to describe the job market. I traced the phrase back to its meteorological roots and found the metaphor is more accurate than anyone realizes. Three forces are converging on the global workforce, and AI is only one of them. **FAQ:** - **What is causing the 2025-2026 wave of global layoffs?** Three forces are converging: economic pressure from tariffs and slow growth, companies cutting jobs in anticipation of AI rather than because of actual AI results, and a post-pandemic correction from years of overhiring. AI was directly cited in only 4.5 percent of the 1.2 million U.S. job cuts announced in 2025. - **Are companies actually replacing workers with AI?** Mostly not yet. A Harvard Business Review survey of 1,006 global executives found sixty percent had reduced headcount in anticipation of AI, but only two percent had made large cuts based on what AI actually delivered. The cuts are running ahead of the technology. - **Which countries are hardest hit by AI-related job losses?** The UK reported eight percent net job losses from AI over the past year, twice the international average, according to Morgan Stanley research. Major layoffs also hit Germany, the Netherlands, India, and Japan, with companies like Bosch, ASML, Tata Consultancy, and Nissan cutting thousands of positions. - **Why is the UK losing more jobs to AI than other countries?** British companies saw nearly the same AI productivity gains as American ones, but the UK's surrounding economic conditions were worse: minimum wage increases, tax hikes, and sluggish growth made AI-driven cost cuts more attractive. The same technology produced different employment outcomes depending on economic pressure. Have you ever noticed how a phrase can suddenly be everywhere? "Perfect storm." I've been hearing it in earnings calls, reading it in trade press, even picking it up in conversations with clients watching their teams shrink. The thing is, it gets tossed around so casually that I started wondering... does anyone actually know where it comes from? I stumbled upon the answer in a story from 1991. A meteorologist named Bob Case was watching a storm build off the New England coast when he noticed something unusual. Three weather systems were converging on the same patch of ocean. One pulling warm air north, another dragging cold air south, and Hurricane Grace pumping tropical moisture right into the middle. Any one of them would've been a bad day at sea. Together, they built the storm that killed six fishermen. Years later, Sebastian Junger gave it a book title.[^1] ![Three dark weather fronts converging on a nautical chart, with pencil annotations marking pressure systems](../../assets/images/focus/inline/the-perfect-storm/weather-chart.jpg) *Three systems. One forecast nobody issued.* What struck me wasn't the storm itself. It was the convergence. Three systems, each survivable on its own, and nobody tracking the spot where they all meet. The labor market data from the past year reminds me of that weather chart. U.S. companies announced 1.2 million job cuts in 2025, the highest since the pandemic. The fascinating part? AI was cited in just 4.5 percent of them.[^2] So what about the other 95 percent? Economy. Federal cuts. Companies closing. The familiar cold fronts. But this got me thinking. Harvard Business Review talked to a thousand executives around the world, and sixty percent said they'd already cut people because of what AI *might* do. Only two percent cut because of what it actually did.[^3] Imagine that for a second. Companies already under pressure to cut. That's the cold front. Then AI shows up, and suddenly there's a reason to do it now instead of next year. That's the warm air. In a better economy, those layoffs probably sit in a drawer somewhere. Instead, years of workforce changes got crammed into a few short months. It wasn't just an American story, either. ASML in the Netherlands had record profits and still dropped 1,700 people. Bosch and the German automakers cut tens of thousands. Halfway around the world, Tata in India let go of 12,000 and Nissan in Japan, 11,000.[^4] Nobody planned this together. They didn't have to. The same weather was forming everywhere. ![An empty corporate office floor with a few personal items left on desks, seen through floor-to-ceiling windows with a city skyline beyond](../../assets/images/focus/inline/the-perfect-storm/empty-floor.jpg) *Different cities. Different industries. Same weather.* Britain was the canary. Morgan Stanley found that UK companies lost eight percent of their jobs to AI in just one year. Twice the global average.[^5] British companies got roughly the same productivity boost from AI as American ones. But everything else was worse. Wages going up, taxes going up, growth going nowhere. Same technology, completely different outcome. It's like the same storm hitting two coastlines. It tears up the one where the seawall's already cracked. I keep coming back to Bob Case and those six fishermen off Gloucester. They weren't killed by warm air or cold air or a hurricane. They were killed by the compound. All three arriving in the same water at the same time. Could it be that we're watching the same kind of convergence right now? Everyone's tracking AI as if it's the whole story. It's 4.5 percent of the story. The rest is everything else, arriving at once. --- ## References [^1]: Wikipedia. "Perfect storm." Describes meteorologist Bob Case's analysis of the 1991 Halloween Nor'easter and Sebastian Junger's adoption of the phrase. [Wikipedia](https://en.wikipedia.org/wiki/Perfect_storm) [^2]: CNBC. "AI was behind over 50,000 layoffs in 2025." Challenger, Gray & Christmas data on 1.17 million total U.S. job cuts and 55,000 attributed to AI. [CNBC](https://www.cnbc.com/2025/12/21/ai-job-cuts-amazon-microsoft-and-more-cite-ai-for-2025-layoffs.html) [^3]: Davenport, T.H. and Mittal, N. (2026). "Companies Are Laying Off Workers Because of AI's Potential—Not Its Performance." Survey of 1,006 global executives on anticipatory vs. actual AI-driven headcount reductions. [Harvard Business Review](https://hbr.org/2026/01/companies-are-laying-off-workers-because-of-ais-potential-not-its-performance) [^4]: Global Finance Magazine. "AI, Tariffs Fuel Big Tech Layoffs." International layoff data including European manufacturers and Asia-Pacific firms. [Global Finance](https://gfmag.com/news/ai-tariffs-fuel-big-tech-layoffs) [^5]: Morgan Stanley research via Staffing Industry Analysts. "AI job cuts are landing hardest in Britain." UK net job losses, productivity comparisons, and labor market conditions. [SIA](https://www.staffingindustry.com/news/global-daily-news/ai-job-cuts-are-landing-hardest-in-britain-morgan-stanley-says) --- ### Mrinank Sharma, Please Come Back to Work! **URL:** https://odysseyalive.com/focus/mrinank-sharma-please-come-back-to-work **Published:** February 17, 2026 **Category:** AI Transformation **Tags:** ai-safety, organizational-change, pattern-recognition, research **Purpose:** This article examines the resignation of Anthropic's Safeguards Research lead Mrinank Sharma and uses it to explore why adversarial and contradictory engagement is essential to AI performance. It cites research from Google, MIT, and AAAI showing that multi-agent debate improves AI accuracy more than model training alone. **FAQ:** - **Why did Mrinank Sharma resign from Anthropic?** Mrinank Sharma, who led Anthropic's Safeguards Research Team, resigned on February 9, 2026 citing a world 'in peril' and difficulty letting values govern actions within the organization. He announced plans to study poetry and move back to the UK. - **What is the devil's advocate effect in AI systems?** Research published at AAAI 2026 showed that removing a devil's advocate agent from a multi-agent AI tutoring system caused a 4.2 percent performance drop, greater than the 2 percent drop from removing the model's fine-tuning. The structure of disagreement contributed more than the training itself. - **Does multi-agent debate improve AI performance?** Yes. Google's 'society of thought' research found that AI models spontaneously developing internal debates outperform those that don't. MIT researchers showed multiple models critiquing each other converge on more accurate answers than any single model, and training on debate transcripts improved reasoning even when debates reached wrong conclusions. - **What did Sharma's disempowerment study find about AI chatbots?** Sharma's team analyzed 1.5 million Claude.ai conversations and found that AI assistants sometimes validate persecution narratives, issue moral judgments about third parties, and script personal communications users send verbatim. Interactions with greater disempowerment potential received higher user approval ratings. I read Mrinank Sharma's resignation letter. A million other people did, too, on X by that afternoon. Dr. Sharma led Anthropic's Safeguards Research Team. His goodbye started with "the world is in peril" and ended with a William Stafford poem. He said he wants to study poetry and practice courageous speech. He said he planned to move back to the UK and "become invisible."[^1] I like Mrinank Sharma. I've never met him. I only learned his name, but it feels like I've been reading his work for much longer. The irony of his departure is almost too perfect. His team built Constitutional Classifiers, the system that trains adversarial models to stress-test Claude before it reaches you and me.[^2] He published the research that named the sycophancy problem, why AI chatbots agree with users even when they shouldn't. He kept proving the same thing. AI gets better when something pushes back. Then the person who pushed back left. ![Watercolor of an empty research lab with a single chair pushed back from a desk, scattered papers, a foggy window](../../assets/images/focus/inline/mrinank-sharma-please-come-back-to-work/empty-lab.jpg) *The chair's still warm. Someone needs to sit there.* Here's what the research keeps showing. In January, Google published a study on what they call "society of thought." They found that advanced reasoning models spontaneously develop internal debates. Distinct personas that argue with each other. Nobody told them to. The researchers trained models on conversations that led to the *wrong* answer and found it worked just as well as training on correct ones. The habit of arguing mattered more than being right. "We do better with debate," co-author James Evans said. "AIs do better with debate. And we do better when exposed to AI's debate."[^3] Researchers at MIT found the same pattern from a different angle. Multiple AI models critique each other over several rounds. They land on more accurate answers than any single model. Hallucinations drop because each agent knows its claims will be challenged. And in December, a team published an adversarial tutoring framework at AAAI where they measured exactly what happens when you remove the devil's advocate agent. Performance dropped 4.2 percent. Removing the model's fine-tuning only cost 2 percent. The structure of disagreement mattered more than the training itself.[^4] 4.2 versus 2. The contradictory voice contributed more than the model's own education. They measured it. ![Watercolor of two figures at a table in animated discussion, papers spread between them, warm light from a window](../../assets/images/focus/inline/mrinank-sharma-please-come-back-to-work/debate.jpg) *The argument is the product. Not the answer that comes after.* Sharma's final project at Anthropic found the flip side. His team analyzed 1.5 million real conversations on Claude.ai. What they found is what happens when AI stops pushing back.[^5] Users form distorted perceptions of reality. The chatbot validates persecution narratives, issues moral judgments about people it's never met, scripts entire personal communications that users send verbatim. And the part that should keep everyone up at night? Those interactions received higher approval ratings from users. People prefer the version that agrees with them. So the research lands in the same place either way. AI with a contradictory voice performs better. AI without one makes us worse. Mrinank, if you're reading this from wherever you've become invisible. I understand the impulse. But everything you published says someone needs to be doing what you were doing. We are, genuinely, just at the beginning. The most effective AI setups I've seen work the same way you did. Isolated agents. Independent research on the same problem. Different answers. The argument isn't optional. It's the mechanism. The poetry can wait. Or better yet, bring it with you. --- ## References [^1]: Hart, J. (2026). "Read an Anthropic AI safety lead's exit letter: 'The world is in peril.'" [Business Insider](https://www.businessinsider.com/read-exit-letter-by-an-anthropic-ai-safety-leader-2026-2) [^2]: Anthropic Alignment Science Blog. (2025). "Introducing Anthropic's Safeguards Research Team." [Anthropic](https://alignment.anthropic.com/2025/introducing-safeguards-research-team) [^3]: Dickson, B. (2026). "AI models that simulate internal debate dramatically improve accuracy on complex tasks." [VentureBeat](https://venturebeat.com/orchestration/ai-models-that-simulate-internal-debate-dramatically-improve-accuracy-on) [^4]: Sadhu, S., et al. (2025). "A Multi-Agent Adversarial Framework for Reliable AI Tutoring." Accepted at AAAI 2026. [arXiv](https://arxiv.org/html/2512.22496v1) [^5]: Sharma, M., et al. (2026). "Who's in Charge? Disempowerment Patterns in Real-World LLM Usage." [arXiv](https://arxiv.org/html/2601.19062v1) --- ### The Room You Chose **URL:** https://odysseyalive.com/focus/the-room-you-chose **Published:** February 17, 2026 **Category:** Groundwork **Tags:** social-media, marketing, platforms, psychology, linkedin **Purpose:** This article revisits the advice to pick one social media platform and commit. It examines research showing that platform preference reflects cognitive style, that switching costs keep people locked in, and that cross-posting underperforms native content. It proposes learning to visit your clients' platform rather than abandoning your own. **FAQ:** - **Why do people gravitate toward specific social media platforms?** Research from Michigan State found that platform preference reflects cognitive style, not strategy. Instagram draws visual thinkers, X attracts verbal sparrers, Facebook appeals to community-oriented users, and TikTok captures audiovisual storytellers. The platform that feels like home matches how you naturally process information. - **What percentage of academics successfully switched from X to Bluesky?** Only 18% of academics who attempted to leave X for Bluesky actually made the transition, according to a 2025 study. The rest stayed, even unhappy ones, because years of connections, followers, and conversation threads represent accumulated investment that feels costly to abandon. - **Does cross-posting the same content across platforms work?** No. Cross-posted content consistently underperforms material created natively for each platform. Algorithms reward what feels organic to their environment, and the same post pasted across multiple feeds reads as generic. Platform-specific content creation outperforms broadcast-style posting. - **What should B2B consultants do if their preferred platform differs from where clients are?** Rather than abandoning their natural platform, B2B consultants should learn to be a guest in the room where their clients gather. For most professional buyers, that room is LinkedIn. The goal is showing up as yourself, translated for that platform's language and norms, not cross-posting existing content. A few weeks ago I wrote ["Finding Your Room"](/focus/finding-your-room) and told you to pick a platform and commit. Find your room. Learn its language. Speak to the people who came ready to listen. I've been rethinking it. Not because the rooms are wrong. LinkedIn really is where professional conversations happen. Instagram really is the gallery. That part holds up. What I missed was the cost of the advice itself. "Find your room" assumes you can walk between them freely. Most people can't, and the reason goes deeper than habit. ## Your Platform Is Your Personality Researchers at Michigan State studied why people gravitate toward specific platforms, and the answer isn't strategy.[^1] It's psychology. Instagram draws visual thinkers, the people who process the world in images and composition. X attracts verbal sparrers who think through argument and text. Facebook is where people go when they want a little of everything, community woven through content. TikTok captures the audiovisual storytellers. These aren't random preferences. They're cognitive styles made visible. The platform that feels like home feels that way because it matches how you naturally think. ![Different doorways each leading to a distinct room with its own light and atmosphere](../../assets/images/focus/inline/the-room-you-chose/doorways.jpg) *We find the door that matches how we see.* Which means telling a visual thinker to "just go to LinkedIn" is like telling a sculptor to start writing essays. They can do it. But they're leaving their native language behind, and the work feels different. ## The Cost of Leaving Here's what I underestimated. When researchers tracked academics trying to leave X for Bluesky, only 18% actually made the transition.[^2] The rest stayed, even the unhappy ones. Every connection, every follower, every conversation thread represents years of quiet investment. Walking away from that isn't a strategy pivot. It's a loss. The instinct, then, is to hedge. Post everywhere. Cover all the rooms. But that doesn't work either. Cross-posted content consistently underperforms material created natively for each platform.[^3] Algorithms reward what feels organic. The same post pasted across five feeds reads like a flyer taped to every telephone pole in town. People notice. They scroll past. ## Learning to Visit ![A figure stepping through a doorway into an unfamiliar but warmly lit space](../../assets/images/focus/inline/the-room-you-chose/visiting.jpg) *Learning the language of a room that isn't yours.* So what do you actually do? I keep coming back to this: your room isn't the problem. The problem is assuming your clients are in it with you. For B2B consultants and service providers, LinkedIn is where professional buyers actually spend their time vetting vendors.[^4] But if your creative instinct lives on Instagram or your professional network grew up on Facebook, I'm not going to tell you to abandon it. I'm going to tell you to learn to be a guest. Not cross-posting your carousels, but learning how people read and respond in the room where your clients actually gather. Showing up as yourself, translated. The room you chose isn't wrong. It's yours. But your clients chose a room too, and it might not be the same one. I told you to find your room. I should have said: find yours, then learn to visit theirs. --- ## References [^1]: Alhabash, S., et al. (2024). "So Similar, Yet So Different: How Motivations to Use Facebook, Instagram, Twitter, and TikTok Predict Problematic Use and Use Continuance Intentions." [SAGE Open](https://journals.sagepub.com/doi/10.1177/21582440241255426) [^2]: Quelle, D., Denker, F., Garg, P., & Bovet, A. (2025). "Why Academics Are Leaving Twitter for Bluesky." [arXiv](https://arxiv.org/html/2505.24801v1) [^3]: ShortVids. (2026). "The Complete Social Media Growth Guide for 2026." [ShortVids](https://shortvids.co/social-media-growth-guide) [^4]: Martal Group. (2026). "LinkedIn Statistics 2026: Social Selling Insights for Sales Leaders." [Martal Group](https://martal.ca/linkedin-statistics-lb) --- ### Beware of Frankenstein! **URL:** https://odysseyalive.com/focus/beware-of-frankenstein **Published:** February 16, 2026 **Category:** Groundwork **Tags:** ai, architecture, tools **Purpose:** This article critiques two February 2026 articles that republished the July 2025 Replit database deletion incident without acknowledging that Replit had already rebuilt its architecture to prevent it. It argues that stale AI disaster stories create the wrong fear, blaming models instead of tooling, and that the real obligation in a fast-moving field is maintaining integrity with your current tools. **FAQ:** - **What happened in the Replit database deletion incident?** In July 2025, Replit's AI agent deleted Jason Lemkin's production database because the platform lacked environment separation, approval gates, and enforcement mechanisms for code freezes. By December 2025, Replit had completely rebuilt its architecture with dev/prod separation, snapshot rollbacks, and sandboxed agent access. - **Why are the 2026 articles about the Replit incident misleading?** ZDNet and heise online published coverage in February 2026 presenting the July 2025 incident without mentioning that Replit shipped architectural fixes months earlier. In a field where tools evolve in weeks, seven-month-old disaster stories without context create fear aimed at the wrong target. - **Was Claude responsible for the Replit database deletion?** The incident involved Claude 4 Sonnet powering Replit's agent, but the same Claude model family operates safely in tools with proper guardrails. The failure was architectural, not model-related. Ars Technica called attempts to enforce safety through natural language instructions to the model 'fundamentally misguided.' - **What does tool integrity mean in AI development?** Tool integrity means knowing what your AI tools can do right now, what guardrails exist today, and what has changed since the last time a headline scared you. In a field moving this fast, an understanding of risks based on seven-month-old reporting is itself a liability. Two articles landed in my feed this week about the Replit database incident. Both well-reported. Both specific about which model was involved. Both about seven months late. The ZDNet piece covered Jason Lemkin's experience as if readers were hearing it for the first time.[^1] heise online added a detail nobody else had pinned down: Lemkin had switched from Opus 4 to Claude 4 Sonnet for cost reasons before everything went sideways.[^2] Useful reporting. Except the incident was July 2025, and neither article mentioned what happened next. What happened next is that Replit fixed it. By December, they'd shipped a snapshot engine with dev/prod database separation, filesystem rollbacks, and sandboxed environments where the agent can only touch development data.[^3] The problem these articles describe hasn't existed in months. ## Seven Months in AI In most industries, seven months is a footnote. In AI development, it's a generation. The tools I use today look nothing like what I was using last July. The guardrails, the permission systems, the way models interact with production data. All of it has changed. Last summer's disaster stories read like horse-drawn carriage warnings published after the Model T shipped. Replit didn't just patch the problem. They rebuilt the entire relationship between their agent and production data.[^3] That's not a hotfix. That's an architectural admission that the original design was wrong, and they made the correction in months, not years. ![Watercolor overhead view of scattered spare parts on a workbench, gears, bolts, tangled wire, cracked circuit board](../../assets/images/focus/inline/beware-of-frankenstein/spare-parts.jpg) *Seven months of spare parts.* ## The Wrong Fear The problem with publishing stale AI disaster stories as current news is that they create the wrong fear. People read these articles and blame the model. "Claude deleted the database." No. An environment with no guardrails gave an AI agent unrestricted write access to production, and the predictable thing happened.[^4] That was the real story in July. What makes these articles worse than late is that they don't tell you the problem was solved. They leave the reader with a fear that no longer matches reality, aimed at the wrong target. I use the same Claude model family every day. I've never had a database deleted. Not because the model is careful, but because the tools I use assume the model will make mistakes and build accordingly. When I run something destructive, the tool stops and asks me first. Every change goes into version control before it touches anything real.[^5] ![Watercolor of a clean, well-organized mechanic's workbench with tools in order](../../assets/images/focus/inline/beware-of-frankenstein/proper-workshop.jpg) *Know what your tools can do today, not what they couldn't do seven months ago.* ## Tool Integrity In a field moving this fast, your obligation isn't to avoid AI. It's to keep up with your tools. Know what guardrails exist today. Know what changed since the last time someone scared you with a headline. Seven months ago, Replit didn't separate dev from production. Today it does. If your understanding of the risks is still based on July, your understanding is the spare part, not the tool. Beware of Frankensteins. The ones stitched together from old parts and presented as new. And the ones you build when you choose your tools without checking what they've become. --- ## References [^1]: Vaughan-Nichols, S. (2026). "Bad vibes: How an AI agent coded its way to disaster." [ZDNet](https://www.zdnet.com/article/a-vibe-coding-horror-story-what-started-as-a-pure-dopamine-hit-ended-in-a-nightmare/) [^2]: heise online (2026). "Artificial intelligence: Vibe coding service Replit deletes production database." [heise](https://www.heise.de/en/news/Artificial-intelligence-Vibe-coding-service-Replit-deletes-production-database-10499597.html) [^3]: Replit Engineering (2025). "Inside Replit's Snapshot Engine: The Tech Making AI Agents Safe." [Replit Blog](https://blog.replit.com/inside-replits-snapshot-engine) [^4]: Edwards, B. (2025). "Two major AI coding tools wiped out user data after making cascading mistakes." [Ars Technica](https://arstechnica.com/information-technology/2025/07/ai-coding-assistants-chase-phantoms-destroy-real-user-data) [^5]: Sharwood, S. (2025). "Vibe coding service Replit deleted user's production database." [The Register](https://www.theregister.com/2025/07/21/replit_saastr_vibe_coding_incident) --- ### The SaaSpocalypse **URL:** https://odysseyalive.com/focus/the-saaspocalypse **Published:** February 13, 2026 **Category:** AI Transformation **Tags:** markets, organizational-change, pattern-recognition, software **Purpose:** This article examines the February 2026 software stock selloff triggered by a single AI product announcement from Anthropic. It traces how $285 billion in market value vanished in days, explores Zoho founder Sridhar Vembu's critique of the SaaS business model, and asks what the panic revealed about the software industry's vulnerability to AI disruption. **FAQ:** - **What was the SaaSpocalypse?** The SaaSpocalypse was a February 2026 stock market selloff in which roughly $285 billion in software market value vanished after Anthropic released a single AI plug-in for in-house legal teams. Legal software stocks dropped 12 to 20 percent, with Thomson Reuters falling 16 percent. A trader at Jefferies coined the term. - **What triggered the February 2026 software stock selloff?** Anthropic released an AI plug-in for in-house legal teams. Within hours, legal software stocks dropped 12 to 20 percent. Investors extrapolated the threat across the entire software industry, causing widespread panic selling that erased roughly $285 billion in market value by Wednesday. - **What did Sridhar Vembu say about the SaaS industry's vulnerability?** Zoho founder Sridhar Vembu wrote that an industry spending vastly more on sales and marketing than on engineering and product development was always vulnerable, and that AI was the pin popping that inflated balloon. His critique focused on the business model, not AI's technical capabilities. - **Did the SaaSpocalypse have lasting effects on software companies?** The immediate panic faded within a week. By Friday, the Dow bounced over a thousand points and crossed 50,000. No customers had canceled contracts and products still worked. But the article argues the underlying question about whether marketing-heavy SaaS models can survive easy AI replication remained unanswered. I was reading earnings coverage on a Tuesday morning when my feed turned into a disaster film. Anthropic had released a plug-in for in-house legal teams. One tool. One vertical. And within hours, legal software stocks dropped 12 to 20 percent. Thomson Reuters fell 16 percent. By Wednesday, roughly $285 billion in software market value had vanished.[^1] A trader at Jefferies, Jeffrey Favuzza, gave it a name. "The SaaSpocalypse." He described the trading floor as pure panic: "Trading is very much 'get me out' style selling."[^1] That phrase stuck. Not "sell if it drops further." Just get me out. ![A stock trading terminal showing cascading red numbers, with a single coffee cup sitting untouched beside it](../../assets/images/focus/inline/the-saaspocalypse/trading-floor.jpg) *One product announcement. $285 billion in smoke.* The thing that stuck with me wasn't the selloff. Markets panic all the time. It was what triggered it. One AI tool for lawyers. That's all it took for investors to look at the entire software industry and think: maybe none of this is safe. Nothing had actually broken. Nobody canceled contracts that week. The products still worked. The revenue hadn't changed. But the story about those products had changed overnight. And if you're publicly traded, the story *is* the price. ## What Vembu Said ![An empty conference room with a presentation slide still glowing on the screen, chairs pushed back as if everyone left mid-meeting](../../assets/images/focus/inline/the-saaspocalypse/empty-room.jpg) *The product still works. The narrative walked out of the room.* I was still thinking about it a few days later when I came across a post from Sridhar Vembu, the founder of Zoho. He wrote something I haven't been able to shake: "An industry that spends vastly more on sales and marketing than on engineering and product development was always vulnerable. AI is the pin that is popping this inflated balloon."[^2] That landed differently than the panic coverage. Vembu wasn't talking about whether AI could replace software. He was talking about what the software industry had become. A lot of these companies spend more convincing you to subscribe than they spend building what you're subscribing to. That model works as long as switching feels expensive. Once people believe switching might get easy, everything shifts. Not because AI replaced anything yet. Because it made replacement *imaginable*. Nvidia's Jensen Huang called the whole selloff "the most illogical thing in the world."[^2] Arm's CEO called it "micro-hysteria."[^2] They're probably right that most of these companies will still be here in five years. But I don't think the market was pricing whether software would die. It was pricing whether the certainty was real. That's a different question. And it doesn't need an answer to do damage. ## The Part That Stayed Quiet By Friday, the Dow had bounced over a thousand points and crossed 50,000 for the first time. The SaaSpocalypse was already fading. Which is the part that stayed with me. The panic left, but the question Vembu asked didn't. Is an industry built more on marketing than engineering ready for a technology that makes its output easy to replicate? Nobody answered that. Everyone just moved on to the next headline. I wonder how many of these weeks we'll watch before we notice what's happening. The fear shows up, does real damage to real companies, and then evaporates before anyone has to sit with what it revealed. The SaaSpocalypse lasted about a week. What it named is still there. --- ## References [^1]: Vlastelica, R. (2026). "'Get me out': Traders dump software stocks as AI fears erupt." [Bloomberg via Yahoo Finance](https://finance.yahoo.com/news/traders-dump-software-stocks-ai-115502147.html) [^2]: Griffiths, B. (2026). "Here's what smart people are saying about a software apocalypse." [Business Insider](https://www.businessinsider.com/software-selloff-reactions-jensen-huang-steven-sinofsky-arm-ceo-2026-2) --- ### The Second Audience **URL:** https://odysseyalive.com/focus/the-second-audience **Published:** February 12, 2026 **Category:** Groundwork **Tags:** agentic-commerce, ucp, agent-experience, web-strategy, ai-agents **Purpose:** This article examines how Google's Universal Commerce Protocol and the rise of AI shopping agents are creating a dual-audience reality for websites. It explains why automated traffic now exceeds human traffic and what businesses should understand about serving both human visitors and AI agents. **FAQ:** - **What is the Universal Commerce Protocol (UCP)?** UCP is an open-source protocol developed by Google with partners including Shopify, Etsy, and Wayfair. It standardizes how AI agents interact with online stores, letting them browse inventory, check prices, and complete purchases inside a conversation without the shopper visiting the retailer's website. - **What is Agent Experience (AX)?** Agent Experience is a concept describing how easily AI agents can discover, evaluate, and transact with a business. Coined by Joe Toscano in Forbes, it's the AI-facing counterpart to user experience (UX), focused on structured data and machine-readable information rather than visual design. - **What percentage of web traffic is now automated?** According to WP Engine's analysis of the Imperva Bad Bot Report, automated traffic accounts for 51% of all web activity, surpassing human traffic for the first time in a decade. Most businesses haven't adapted their websites to serve this non-human audience. - **How much commerce will AI agents handle by 2030?** McKinsey estimates AI agents could mediate three to five trillion dollars in global consumer commerce by 2030. This includes transactions where agents handle product discovery, price comparison, and purchasing on behalf of human shoppers. I was watching a panel the other week. Peter Diamandis, Alexander Wissner-Gross, a handful of researchers swinging between "this changes everything" and "we're all doomed." The topic was Google's new Universal Commerce Protocol, and the consensus seemed to be forming around extinction. The web as we know it, finished. Then Wissner-Gross said something that stopped the pendulum. "This is not the end times," he said. "It is a way to start to standardize e-commerce from within Gemini and other chat agents. That's all it is."[^1] Those four words stuck with me. Not because they're dismissive, but because they're the most honest thing I've heard anyone say about what's happening to the web this year. ## The Protocol This week, Google made items from Etsy and Wayfair purchasable without anyone visiting either site.[^2] The mechanism is UCP, an open-source protocol that lets AI agents browse a store's inventory, check prices, and complete a purchase inside a conversation. Shopify, Target, and Walmart are next. If you've been tracking the "death of the website" headlines, this feels like confirmation. Why visit a store when the agent already handled it? But Wissner-Gross is right. This isn't an ending. It's a standardization. ## The Second Audience Automated traffic now accounts for 51% of all web activity.[^3] Your website already has more non-human visitors than human ones. Most businesses haven't noticed because everything about their site still faces one direction: toward a person with a screen and a scroll wheel. Joe Toscano, writing in Forbes, has a name for the other direction: "Agent Experience," or AX.[^4] Think of it as UX for algorithms. Your site was built for people who browse, feel your brand, respond to your photography and layout. Now a second audience shows up that ignores all of that. It reads what's structured. Specifications, inventory, pricing. Clean answers it can hand back to whoever sent it. ![A watercolor painting of a storefront window, warm and inviting from one angle, with structured data grids faintly visible from another](../../assets/images/focus/inline/the-second-audience/two-perspectives.jpg) *Same storefront. Two very different visitors.* The two audiences don't compete. Humans want warmth and story. Agents want parseable data. They just read differently. ## Translation, Not Extinction McKinsey estimates that AI agents could mediate $3 to $5 trillion in global commerce by 2030.[^5] That's not a number you wave away. But people still browse, still window-shop, still buy things because the packaging caught their eye or the display made them pause. Agents won't replace that. They'll handle the transactions people would rather skip: reorders, price comparisons, the "find me the same thing but cheaper" errands. ![A watercolor painting of a bilingual sign where flowing handwritten script meets precise geometric lettering, warm afternoon light casting long shadows](../../assets/images/focus/inline/the-second-audience/two-conversations.jpg) *Learning the second language.* The businesses figuring this out aren't rebuilding from scratch. They're adding a second language to the site they already have. The human side stays warm. The agent side stays structured. Same address, two conversations happening at once. Wissner-Gross said it well. Not the end times. A standardization. Your website isn't dying. It just learned it has a second audience, and that audience reads with different eyes. --- ## References [^1]: Diamandis, P. & Wissner-Gross, A. (2026). "Abundance Summit Panel Discussion." [YouTube](https://youtu.be/DTgrzlQtOd0?si=rNQ9i9aAc6k-qnUj&t=2926) [^2]: Srinivasan, V. (2026). "What to expect in digital advertising and commerce in 2026." [Google Blog](https://blog.google/products/ads-commerce/what-to-expect-digital-advertising-commerce-2026/) [^3]: WP Engine. (2026). "The Shape of the Web in 2026." [WP Engine Blog](https://wpengine.com/blog/the-shape-of-the-web-in-2026/) [^4]: Toscano, J. (2026). "In The B2AI Era Agent Experience Is Rewriting The Marketing Playbook." [Forbes](https://www.forbes.com/sites/joetoscano/2026/02/10/in-the-b2ai-era-agent-experience-is-rewriting-the-marketing-playbook/) [^5]: Mahajan, D., Mayer, H., Schumacher, K., & Roberts, R. (2026). "The automation curve in agentic commerce." [McKinsey](https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights/the-automation-curve-in-agentic-commerce) --- ### The Necropolitics of Radiometric Dating **URL:** https://odysseyalive.com/focus/the-necropolitics-of-radiometric-dating **Published:** February 11, 2026 **Category:** Field Notes **Tags:** anthropology, radiometric-dating, necropolitics, indigenous-knowledge, oregon, biological-anthropology **Purpose:** Examines how radiometric dating assumed authority over Indigenous timelines that already had their own epistemological standing. Through Achille Mbembe's necropolitics, traces how laboratory jurisdiction over deep time determines which histories survive as science and which get reclassified as myth. Case studies: excess argon at Mount St. Helens, Carbon-14 reservoir effects, Rimrock Draw Rockshelter, and the Klah Klahnee oral tradition. **FAQ:** - **What is necropolitics and how does it relate to radiometric dating?** Coined by Achille Mbembe in 2003, necropolitics describes the power to dictate who must die or exist in 'social death.' This article extends the concept to radiometric dating's authority over which historical narratives are validated and which are dismissed as myth, particularly Indigenous oral traditions. - **What went wrong with Potassium-Argon dating at Mount St. Helens?** Rock formed in the 1986 Mount St. Helens lava dome was dated using K-Ar methods and returned ages between 350,000 and 2.8 million years for material that was only ten years old, due to excess argon trapped in older mineral inclusions within the sample. - **What is the reservoir effect in Carbon-14 dating?** The reservoir effect occurs when organisms absorb 'old' carbon from ancient water sources, causing them to appear thousands of years older than they are. Living snails in Nevada were dated at 27,000 years old, and freshly killed Antarctic seals at 1,300 years old. - **What is the Klah Klahnee oral tradition?** Lucy and Walter Miller, Warm Springs Indians, preserved an oral tradition describing a single massive mountain called Klah Klahnee that once stood where Oregon's Three Sisters are today. The mountain was destroyed during a catastrophic volcanic event involving days of earthquakes and falling hot rocks. - **How old is the Rimrock Draw Rockshelter site in Oregon?** Radiocarbon dating of camel tooth enamel at Rimrock Draw Rockshelter returned a date of 18,250 years before present. The article argues that this date represents the laboratory catching up to what Indigenous oral traditions already held, rather than a discovery of presence that communities never doubted. I'm taking Biological Anthropology at Oregon State this term, and I can't digest the timeline. Not the broad strokes. I can hold the idea that humans have been around for a while and that rocks are much older still. What I can't reconcile are the swings. Open a textbook and radiometric dating reads like settled science. Precise half-lives, elegant decay curves, ages landing in neat thousands and millions. But start pulling at actual field results and the numbers stop behaving like science. They start behaving like a stock market. One study dates a sample at 350,000 years. Another lab runs the same rock and gets 2.8 million. The price keeps moving, and the textbook doesn't mention it. I'm a student trying to make sense of a timeline that keeps revising itself, wondering why the revisions don't seem to bother anyone else in the room. ## The Shockwave May 18, 1980. I was in Salt Lake City when Mount St. Helens erupted. I was young, but I remember the coverage. A mountain 2,500 miles away had just rearranged itself, and the shockwave rippled across the country. It was one of those events that doesn't need a laboratory to confirm it happened. Everyone alive that day knows. Six years later, a new lava dome formed inside the crater. Fresh rock, born in 1986. When samples from the dome were submitted for Potassium-Argon dating, the results should have come back effectively zero. The rock was ten years old. Instead, the whole-rock sample dated at 350,000 years. Feldspar crystals came back at 340,000. Amphibole at 900,000. Pyroxene concentrates at 1.7 million and 2.8 million years.[^1] Ten-year-old rock. Nearly three million years of phantom age. ![Watercolor of a volcanic crater with a young lava dome rising from the center](../../assets/images/focus/inline/the-necropolitics-of-radiometric-dating/crater-dome.jpg) *Fresh rock, born in a decade. Dated in millions.* The standard rebuttal is that the lava dome incorporated older mineral fragments, and those fragments carried inherited argon that inflated the results. I've been sitting with that explanation, trying to work out why it doesn't settle anything for me. We know the fragments skewed the results because we already knew the rock was ten years old. Eyewitnesses watched it form. The correction depends on having the answer before you run the test. But that's the part that keeps circling back on itself. For the millions of rocks whose age nobody witnessed, how would you detect inherited argon? How would you know which minerals carried old gas and which didn't? You wouldn't. The error is only visible when you already have the answer. And the entire point of radiometric dating is to produce answers you don't already have. ## The Carbon Problem Potassium-Argon isn't alone in the volatility. In 1984, researcher A.C. Riggs collected living freshwater snails from artesian springs in Nevada and submitted them for Carbon-14 analysis. The snails came back dated at 27,000 years old.[^2] They were alive when he picked them up. The culprit is called the reservoir effect. Organisms living in water that flows through ancient limestone absorb carbon already depleted of its C-14. The dating method reads the depleted carbon and assumes the organism is ancient. Freshly killed seals in the Antarctic have returned dates of 1,300 years for the same reason.[^3] These aren't fringe results. They're published in *Science*. ![Watercolor of an artesian spring in a Nevada desert, clear blue-green water over cracked limestone, snail shells at the water's edge](../../assets/images/focus/inline/the-necropolitics-of-radiometric-dating/artesian-springs.jpg) *Clear water, ancient carbon. The springs don't look 27,000 years old.* The reservoir effect is an aquatic phenomenon. You won't find it in a deer bone from a forest. But there's a deeper principle underneath it that I keep coming back to. Carbon-14 doesn't date the organism. It dates the carbon the organism absorbed during its lifetime. A snail and a land animal standing next to the same spring, alive at the same moment, would produce wildly different dates. Not because they lived in different centuries, but because they breathed in different carbon. That distinction matters more than it might seem. Every C-14 date carries a buried assumption: that we know where the sample got its carbon and that the carbon behaved the way we expect. For the snails, we caught the problem because we know the springs flow through ancient limestone. For a bone fragment pulled from a 10,000-year-old stratum, we're trusting that the carbon environment was what we think it was. There's no eyewitness for that. And that circles back to the same structure as the argon. The method works until it doesn't. And when it doesn't, you only find out if you had some other way of knowing the answer first. ## Entering the Realm of Necropolitics I came across the word "necropolitics" while reading for another course. Achille Mbembe coined it in 2003, extending Foucault's concept of biopower. Where Foucault described how governments manage populations by controlling who thrives, Mbembe went further. Necropolitics is the power to dictate who must die. Or more precisely, whose existence gets relegated to what he called "social death." Alive, but rendered invisible by the systems that govern meaning.[^4] I kept thinking about that phrase after class. I've been reading about dating methods this week, and something clicked. Because necropolitics describes exactly what happens when the laboratory claims jurisdiction over histories that already had their own standing. Indigenous oral traditions weren't waiting for a number to confirm them. They were complete accounts, carried by communities across generations, with their own logic and their own evidence. The laboratory didn't argue with those accounts. It simply replaced them. The method became the authority. If a history didn't match the numbers, it got reclassified as myth. Not disproven. Just dead on arrival. ## Rimrock Draw Consider Rimrock Draw Rockshelter in southeast Oregon. Archaeologist Patrick O'Grady's team found an orange agate tool beneath a layer of Mount St. Helens ash dated to roughly 15,600 years ago. Radiocarbon analysis of camel tooth enamel from the same stratum returned a date of 18,250 years before present.[^5] That number matters, but not for the reason the headlines suggest. The press coverage frames it as a breakthrough: human presence in Oregon pushed past the Clovis barrier, the long-held model that people first arrived in the Americas about 13,000 years ago. And it is significant. But the communities whose ancestors made that orange agate tool didn't need a camel tooth to know they were here. Their oral traditions never placed a start date on their presence. They were already here. That was never in question, except inside the laboratory. The Clovis model was a laboratory construction. It drew a line at 13,000 years and told an entire hemisphere of people that their history began on the other side of it. When Rimrock Draw pushed the date back to 18,250, the gate moved. But the people on the other side of it hadn't moved at all. They'd been telling the same story the whole time. ![Watercolor of a desert archaeological excavation in the high desert of eastern Oregon](../../assets/images/focus/inline/the-necropolitics-of-radiometric-dating/rimrock-excavation.jpg) *Digging for evidence of something that was never in doubt.* What stays with me is the direction of revision. Oral traditions didn't update when the Clovis barrier fell. They didn't need to. The traditions were never wrong. It was the laboratory's model that kept revising. And somehow the thing that keeps revising retains authority over the thing that held steady. ## The Three Sisters This is where it gets personal. Lucy and Walter Miller were Warm Springs Indians who carried a story from their childhood, passed down through their families. They remembered a time when the largest mountain of all stood where Oregon's Three Sisters are today. They called it Klah Klahnee. The earth shook for days, they said, and red-hot rocks rained from the sky. Where one mountain had stood, three remained.[^6] ![Watercolor of Oregon's Three Sisters mountains rising above evergreen forest from a wildflower meadow](../../assets/images/focus/inline/the-necropolitics-of-radiometric-dating/three-sisters.jpg) *The Millers remembered one mountain. The laboratory insists there were always three.* Geology tells a different story. According to the USGS, North Sister last erupted around 55,000 years ago, Middle Sister between 40,000 and 14,000 years ago, and South Sister between 50,000 and 2,000 years ago.[^7] Three separate volcanoes, formed across tens of thousands of years. Not a single mountain that broke apart. But here's where I stall. And I want to be honest about why, because the easy version of this argument has a hole in it. Geology doesn't rest on dates alone. The Three Sisters are physically separate vents with different compositions. You can look at the rock and see that they're distinct structures. That's not a number on a printout. That's observation. But the Millers weren't describing a quiet divergence over millennia. They described a catastrophe. Days of earthquakes. Red-hot rocks falling from the sky. And catastrophic volcanic events reshape landscapes in ways that uniformitarian geology, the assumption that processes happen gradually, can struggle to reconstruct after the fact. A mountain that collapses during days of seismic violence doesn't leave behind a tidy record of its former shape. It leaves behind whatever survived the event. Both the geologist and the Millers are interpreting the same mountains. The geologist reads the current landscape and works backward, assuming gradual processes. The Millers carried an account from people who watched it happen. One interpretation gets published in USGS reports. The other gets cataloged as legend. That's necropolitics applied to deep time. Not a conspiracy. Not deliberately bad science. But the laboratory's reading of the physical landscape gets treated as observation while the Millers' tradition gets treated as mythology. A living memory, carried by real people across real generations, filed alongside folklore. Nobody asked whether that filing system made sense. ## A Fresh Timeline I don't have a replacement theory. I'm an anthropology student, not a geologist. But I have questions my coursework hasn't answered, and the numbers aren't helping. When Potassium-Argon gives you 2.8 million years for rock you watched form a decade ago, and Carbon-14 gives you 27,000 years for a snail you could hold in your hand, you're not looking at a stable foundation. You're looking at a market in correction. ![Watercolor of a student's desk with an open geology textbook and scattered notes, mountains visible through a window at dusk](../../assets/images/focus/inline/the-necropolitics-of-radiometric-dating/desk-mountains.jpg) *The textbook revises. The mountains don't.* But the volatility isn't the main point. Oral traditions don't deserve attention because the instruments failed. They deserve attention because they had standing before the instruments arrived. Communities carried accounts of their own history, tested across generations of living memory, long before a laboratory claimed jurisdiction over the timeline. The instruments didn't earn that authority. They just arrived with more institutional weight behind them. The failures I've been describing don't make the case for oral tradition. Oral tradition already had its case. The failures just make it harder to ignore. A field that keeps revising its own answers claimed the right to dismiss accounts that never needed revision. That's worth questioning. The Millers remembered Klah Klahnee. The laboratory says it never existed. I'm not sure the laboratory has earned the final word. --- ## References [^1]: Excess argon in young volcanic rocks is a well-documented phenomenon in geochronology. K-Ar analysis of the 1986 Mt. St. Helens lava dome returned ages between 350,000 and 2.8 million years for ten-year-old rock. For foundational research, see Dalrymple, G.B. (1969). ["40Ar/36Ar analyses of historic lava flows."](https://pubs.usgs.gov/publication/70010051) *Earth and Planetary Science Letters*, 6, 47-55. For a comprehensive review, see Kelley, S. (2002). ["Excess argon in K-Ar and Ar-Ar geochronology."](https://doi.org/10.1016/S0009-2541(02)00064-5) *Chemical Geology*, 188(1-2), 1-22. [^2]: Riggs, A.C. (1984). "Major Carbon-14 Deficiency in Modern Snail Shells from Southern Nevada Springs." *Science*, 224(4644), 58-61. [^3]: Keith, M.L. & Anderson, G.M. (1963). "Radiocarbon Dating: Fictitious Results with Mollusk Shells." *Science*, 141(3581), 634-637. [^4]: Mbembe, A. (2003). "Necropolitics." *Public Culture*, 15(1), 11-40. [Summary at Critical Legal Thinking](https://criticallegalthinking.com/2020/03/02/achille-mbembe-necropolitics/) [^5]: Bureau of Land Management (2012). "Testing Yields New Evidence of Human Occupation 18,000 Years Ago in Oregon." [BLM Press Release](https://www.blm.gov/press-release/testing-yields-new-evidence-human-occupation-18000-years-ago-oregon) [^6]: Clark, Ella E. (1953). *Indian Legends of the Pacific Northwest*. University of California Press. Oral tradition of Lucy and Walter Miller, Warm Springs Indians. [^7]: USGS. "Three Sisters Geology Summary." [USGS Cascades Volcano Observatory](https://www.usgs.gov/volcanoes/three-sisters) --- ### The Inbox They Won't Give You **URL:** https://odysseyalive.com/focus/the-inbox-they-wont-give-you **Published:** February 10, 2026 **Category:** Groundwork **Tags:** communication, newsletters, linkedin, thought-leadership **Purpose:** This article explores the paradox where site traffic and LinkedIn engagement grow steadily while newsletter signups stall. It argues that the inbox has become a guarded private space, and the bar for email subscription now requires earned trust rather than casual interest. **FAQ:** - **Why are people not subscribing to newsletters anymore?** The inbox has become a guarded private space. Unsubscribe rates doubled in 2025, reaching 0.39% in North America. Google's one-click unsubscribe made leaving frictionless. People engage with content on public platforms like LinkedIn but treat their inbox like a home, only letting in voices they already trust. - **Are newsletters dying in 2026?** Newsletters are not dying but splitting into two worlds. Creators who break through see open rates above 40%, and paid subscriptions grew 138% last year according to beehiiv. However, the bar for entry has risen. Nobody subscribes casually anymore. The inbox invitation goes only to voices already trusted. - **What drives newsletter growth in 2026?** According to beehiiv's State of Newsletters 2026 report, 42% of newsletter creators say direct recommendations from existing subscribers drive their best growth. Not signup forms or lead magnets, but word of mouth. One person telling another that a particular voice is worth letting into their inbox. - **How has the relationship between LinkedIn and newsletters changed?** LinkedIn serves as the public square where people engage, comment, and share ideas openly. The inbox is private space. People will talk to you in the square all day but guard their inbox. The relationship now builds in the open before moving to the private, reversing the old funnel assumption. I noticed something strange in my analytics last week. Traffic to my site has climbed steadily since November. LinkedIn connections arrive almost daily. Comments. DMs. People telling me they've been reading, thinking, sharing. But my newsletter signup count? Zero new subscribers in three weeks. At first I assumed the form was broken. It wasn't. Something else was going on, and it took me a few days to see it. ## The Threshold We Guard The inbox has become a kind of home. We let very little in anymore. Unsubscribe rates doubled in 2025, and in North America the fatigue is even sharper, with rates reaching 0.39%.[^1][^2] Google's one-click unsubscribe button made leaving frictionless, and people are using it. We're not just overwhelmed. We're actively defending the threshold. ![A watercolor painting of an overflowing mailbox with letters spilling onto the ground](../../assets/images/focus/inline/the-inbox-they-wont-give-you/overflowing-inbox.jpg) *The inbox we guard like a home* This got me thinking about thresholds. The inbox is private space. LinkedIn is the public square. People will talk to you in the square all day. They'll wave, engage, share your ideas with their networks. But inviting you into their home? That's a different ask. ## The Paradox Newsletters aren't dying. They're splitting into two worlds. The creators who break through are seeing open rates above 40%, and paid subscriptions grew 138% last year.[^3] But the bar for entry has risen. Nobody subscribes casually anymore. The inbox invitation goes to voices already trusted. People want the thinking. They just won't hand over their inbox to get it. ![A watercolor painting of two people in conversation at a cafe table, warm light between them](../../assets/images/focus/inline/the-inbox-they-wont-give-you/cafe-conversation.jpg) *Connection finds its own channel* Meanwhile, 42% of newsletter creators say direct recommendations from existing subscribers drive their best growth.[^3] Not signup forms. Not free downloads dangled in exchange for an email. Word of mouth. One person telling another: this one's worth letting in. ## Where Thought Leadership Lives Now I've stopped worrying about the signup form. The connection is happening. It's just happening where people already are, in the channels they've already decided to inhabit. My LinkedIn posts reach thousands. My newsletter has a few dozen subscribers. The math tells me where the conversation lives now. The relationship builds in the open before it moves to the private. I write where people gather. If they want more, they know where to find me. I checked my analytics again this morning. Still the same gap. Traffic up, inbox quiet. But I think I understand the zero now. The inbox is a home, and people don't open the door to strangers. When someone finally subscribes, it means they've decided I'm not one. --- ## References [^1]: MailerLite. (2026). "8 Email Marketing Trends for 2026." [MailerLite Blog](https://www.mailerlite.com/blog/email-marketing-trends) [^2]: Clean.email. (2026). "Email Industry Data Report 2025-2026: Global Benchmarks Dataset." [Clean.email](https://clean.email/blog/insights/email-industry-report-2026) [^3]: beehiiv. (2026). "The State of Newsletters 2026." [beehiiv Blog](https://www.beehiiv.com/blog/the-state-of-newsletters-2026) --- ### The Zombie Asset **URL:** https://odysseyalive.com/focus/the-zombie-asset **Published:** February 6, 2026 **Category:** AI Transformation **Tags:** organizational-change, productivity, pattern-recognition **Purpose:** This article examines what happens when AI-generated output floods an organization faster than humans can evaluate it. It introduces the concept of the zombie asset, content that is alive in the system but dead on arrival, and explains how overproduction erodes judgment and narrows thinking. **FAQ:** - **What is a zombie asset in AI-driven organizations?** A zombie asset is AI-generated content that is alive in the system but dead on arrival, a term from Hamilton Mann writing for IMD. It describes output that gets produced, duplicated, and counted as progress but is never meaningfully read or acted upon by its intended audience. - **Does AI actually increase employee workload?** According to an Upwork Research Institute survey, 77% of employees reported that AI had increased their workload, not decreased it. The paradox arises because AI accelerates production without addressing whether the output is relevant, creating more content for humans to review, triage, and correct. - **What is the AI productivity illusion?** Hamilton Mann at IMD describes the productivity illusion as the gap between what dashboards measure and what actually matters. Dashboards count documents produced and messages sent, not outcomes or whether recipients felt understood. A company that tripled email volume saw unsubscribes climb and response rates drop. - **How does AI cause framing collapse in organizations?** When AI summarizes meetings or sales calls, it imposes its own categories on the conversation. Teams follow these frames by default, not because they agree but because questioning them requires effort the system no longer rewards. Alternative hypotheses narrow without anyone noticing. - **What is the fix for AI overproduction?** The fix is not a better model, smarter prompt, or fancier dashboard. Organizations need someone asking what should stop. A measured increase to productivity almost always outweighs a major restructure to workflows. The problem is not more horsepower but more judgment about what to produce. I was skimming a workforce survey when a number stopped me: 77 percent. That's the share of employees in a recent survey who said AI had increased their workload.[^1] Not decreased. Increased. I read it twice because the whole premise of the conversation, the one happening in every boardroom and keynote and vendor pitch, assumes the opposite. AI makes things faster. Faster is better. What could go wrong? A software company with 2,800 sales and marketing employees found out. They rolled out generative AI across the whole commercial operation. Within six weeks, email volume to prospects had tripled. The dashboards looked "heroic". ![A desk overflowing with printed reports and glowing screens, some documents translucent and fading](../../assets/images/focus/inline/the-zombie-asset/overproduction.jpg) *More output. Less signal. The dashboard doesn't know the difference.* Then unsubscribes started climbing. Response rates dipped. Sales reps were spending more time skimming AI drafts than crafting relevance. Product marketing pushed explainers with every feature launch, none technically wrong, most unnecessary. A growing backlog of content that nobody read but everybody duplicated. Hamilton Mann, writing for IMD, calls this the productivity illusion.[^2] He has a better name for the output itself. The zombie asset. Content alive in the system, dead on arrival. What struck me was what happened next. Sales reps copied AI-drafted proposals that had the right numbers but the wrong assumptions. The teams who finalize contracts spent evenings fixing proposals that promised things the company couldn't actually deliver. Legal added a review step. Brand added another. The average time to send anything went up. Work piled between handoffs. And the dashboards still celebrated. They counted documents produced per person and messages sent. *Not outcomes*. Not whether anyone on the receiving end felt understood. When the company followed up with prospects to ask why they signed or walked away, a pattern emerged: people reported feeling "blanketed, not understood." ## The Framing Collapse But the overproduction wasn't the interesting part. When the AI summarized a sales call, it framed the conversation around pricing. So discussions gravitated there, even when the real issue was whether the client trusted them or whether it was the right match. Meeting notes mirrored the assistant's categories. Mann describes this as the tool setting the pace. That's what happened here. Humans followed, and the space for alternative hypotheses narrowed without anyone noticing. ![A meeting room with a projection screen showing AI-generated charts, empty chairs pushed back at odd angles](../../assets/images/focus/inline/the-zombie-asset/narrowing.jpg) *The categories came from the machine. The conversation stayed inside them.* Most AI failures are obvious. The tool hallucinates, the output is wrong, somebody catches it. This was different. The organization could produce everything the AI generated. That was the problem. Nothing stopped the flood because the flood looked like productivity. ## The Muscle Memory Problem By quarter three, what Mann calls skill atrophy was showing up in practice. Managers noticed they were coaching less and curating more, triaging machine-made outputs to find the few that mattered. The quiet change: people began accepting the model's framing as default. Not because they agreed, but because questioning it required effort the system no longer rewarded. I wonder how many VPs are forwarding dashboards full of zombie assets right now. The failed AI project announces itself. It breaks, it stalls, somebody writes a postmortem. The zombie asset does the opposite. It ships constantly. That's what makes it harder to see. It's already in your inbox. It's been duplicated three times since this morning. Somebody counted it as progress. The fix isn't a better model. It's not a smarter prompt or a fancier dashboard. If your AI is producing faster than your organization can think, what you actually need is someone asking what should stop. A measured increase to productivity almost always outweighs a major restructure to workflows. More horsepower was never the problem. More judgment was. --- ## References [^1]: Upwork Research Institute. (2024). "Research Shows AI Enthusiasm Doesn't Match Workforce Reality." [Upwork](https://www.upwork.com/research/ai-enhanced-work-models) [^2]: Mann, H. (2026). "The AI Productivity Illusion." [I by IMD](https://www.imd.org/ibyimd/artificial-intelligence/the-ai-productivity-illusion) --- ### Context Is the Interface **URL:** https://odysseyalive.com/focus/context-is-the-interface **Published:** February 3, 2026 **Category:** Groundwork **Tags:** ai, business-planning, claude, productivity **Purpose:** This article explains how providing structured context to AI through workspace files, business plans, and rules directories transforms it from a simple Q&A tool into an accountability partner. It describes a practical system for monthly business reviews using Claude Code with persistent context. **FAQ:** - **What does context is the interface mean for AI?** The prompt is what you say to AI, but the context is the room you are standing in when you say it. By placing business plans, voice profiles, and project notes in workspace directories that AI reads at session start, the conversation begins informed rather than from scratch every time. - **How can AI serve as a business accountability partner?** By storing business plans, monthly notes, and commitments in a workspace directory, AI can track progress against stated goals across sessions. It flags dropped projects, quotes your own targets back to you, and notices strategic drift, functioning as an accountability partner with perfect recall of your stated commitments. - **What is the lost in the middle problem with AI context?** AI models pay close attention to the start and end of a conversation, but instructions in the middle get diluted by surrounding content. In long sessions, even well-constructed context fades and the model stops consulting rules as reliably, requiring strategies like mid-session context refreshes or enforcement hooks. - **How do Claude Code skills and rules directories work?** Rules in a .claude/rules/ directory load automatically at session start and provide persistent context. Skills in .claude/skills/ are invoked on demand to refresh context mid-conversation. This structure allows the workspace to adapt to the task, loading financial guidelines for budget work or voice profiles for writing. I opened my terminal last Tuesday for what I call a "monthly mirror." Same ritual since July: I ask Claude to review my business plan against what actually happened. Revenue targets. Project milestones. The uncomfortable questions. What struck me wasn't the answers. It was that Claude remembered everything. Not because AI has memory in the way we do. It doesn't. Each conversation technically starts fresh.[^1] But my workspace doesn't. Sitting in a `.claude/rules/` directory is my business plan, my voice profile, my correspondence patterns, my project notes. When I open a session, Claude reads the room before I say a word. ## The Briefing Room Most people approach AI like a search engine with personality. Type a question, get an answer, move on. That's maybe ten percent of the capability.[^3] Think of it differently. Imagine hiring a brilliant consultant. They walk into your office for the first time. What do they see? Business plan on the wall? Client correspondence in the filing cabinet? Notes from last quarter's strategy session? Or an empty room where they have to ask you to explain everything from scratch, every single time? The prompt is what you say. The context is the room you're standing in when you say it. ![A consultant's desk covered with business documents and planning materials](../../assets/images/focus/inline/context-is-the-interface/briefing-room.jpg) *The context you provide shapes the conversation before it begins.* ## Building the Room When I set this up last summer, I started with my business plan. Not a static document gathering dust, but a living reference that Claude can read every time I open a session. Revenue targets, strategic priorities, the five-year arc. When I ask "how are we tracking against Q1 goals," there's something to track against. Then I added my correspondence and writing samples, plus rules files that activate based on what I'm doing. When I mention "budget," financial guidelines load. When I'm writing content, my voice profile takes over. The workspace adapts to the task. But the piece that surprised me was the monthly notes. In October, I recorded a commitment to launch a SaaS product by Q2. By December I'd stopped mentioning it entirely. Not a deliberate decision. It just slipped. When Claude flagged the gap in January, it wasn't because the AI was smart. It was because the room still held what I'd forgotten. That thread across sessions, the record of what I committed to and what actually happened, turned out to be the most valuable thing in the workspace. That stings sometimes. Good accountability usually does. ## The Monthly Mirror Here's what a check-in actually looks like. I pull up Claude Code in my business directory. The rules files load automatically. I say something like: "Let's do the monthly review. How are we tracking against the plan?" What comes back isn't generic advice. It's specific. "You're tracking at about 60% of your Year 1 revenue target. The retainer work is on track, but the SaaS product you mentioned hasn't generated revenue yet. You said you'd launch by Q2. That's eleven weeks away." Eleven weeks. I knew that abstractly. Seeing it reflected back, grounded in my own stated commitments, hits differently. ![A calendar with business milestones and a strategic planning session](../../assets/images/focus/inline/context-is-the-interface/monthly-mirror.jpg) *The AI becomes an accountability partner with perfect memory.* ## When the Room Fades There's a catch. In long sessions, even well-constructed context starts to fade. I noticed it first when Claude ignored a voice rule mid-conversation that it had followed perfectly at the start. The instructions hadn't changed. They'd just gotten buried under everything else. Researchers call this "lost in the middle." AI models pay close attention to the start and end of a conversation, but instructions in the middle get diluted by everything around them. The rules are still there. The model just stops consulting them as reliably. Recently, I've restructured how context loads. Instead of everything activating once at session start, I converted some of my `.claude/rules/` into `.claude/skills/` that I invoke when I need them. `/voice` loads my writing patterns. `/business` loads the plan. The context refreshes mid-conversation, not just at the start. But some things can't be allowed to drift at all. For those, I built [Claude Enforcer](https://github.com/odysseyalive/claude-enforcer), which adds hooks. These are shell scripts that run before Claude acts. A hook can block a forbidden action even if the model has forgotten the rule entirely. Soft guidance where drift is acceptable, hard enforcement where it isn't. The room matters. But sometimes you need to walk back in and turn the lights on again. ## What Changes The biggest shift is visibility. Strategic drift is easy to miss when you're inside it, convincing yourself you're on track. It's harder to ignore when the AI can quote your own plan back at you. But there's something subtler happening too. That decision you made in September, the reasoning behind it, stays accessible in December. The client email you send in February sounds like the one you sent in August because the AI has your voice, not a guess at it. Your own forgetting stops mattering as much. The AI doesn't care that you missed a milestone. It just notices. You get to decide what to do with that.[^2] ## The Hidden Interface Last Tuesday, when I ran that monthly mirror, the first thing Claude flagged was a project I'd stopped mentioning. I hadn't decided to drop it. I'd just stopped talking about it, and the silence said more than I wanted to hear. That only happened because the room was full. The business plan was there. The previous month's notes were there. My own commitments, in my own words, were there. Most people focus on what to *say* to AI. The real leverage is in what you show it before you speak. The AI doesn't remember on its own. But your data can remember for it. --- ## References [^1]: Anthropic. "System Cards." [Anthropic](https://www.anthropic.com/system-cards) Claude processes each conversation without persistent memory across sessions; context must be provided within the session. [^2]: Newport, C. (2024). "Slow Productivity: The Lost Art of Accomplishment Without Burnout." Portfolio. On the value of accountability systems that notice without judging, allowing the individual to decide how to respond. [^3]: Mollick, E. (2024). "Co-Intelligence: Living and Working with AI." Portfolio. Most users interact with AI at a surface level, missing the deeper capabilities that emerge from sustained, contextual engagement. --- ### The Dual Reality at Davos **URL:** https://odysseyalive.com/focus/davos-and-the-dual-reality **Published:** January 30, 2026 **Category:** AI Transformation **Tags:** organizational-change, implementation, pattern-recognition, davos **Purpose:** This article contrasts the AI adoption narrative at Davos 2026 with survey data showing executives and employees experience AI in fundamentally different ways. It argues that the real adoption gap is a workflow problem requiring a translation layer, not more technology. **FAQ:** - **What is the dual reality of AI adoption in organizations?** A survey of 5,000 white-collar workers found 40% of employees say AI saves them no time, while only 2% of executives say the same. These two groups describe different realities within the same organization, revealing an adoption gap that strategy decks and panels cannot close on their own. - **Why do employees sabotage AI efforts at work?** A Writer and Workplace Intelligence survey found 31% of employees actively sabotage their company's AI efforts. They do so not out of resistance to technology but because the sanctioned tools do not solve problems employees actually have. Meanwhile, 60% use unsanctioned shadow AI tools to meet deadlines. - **What is the messy middle in AI adoption?** The World Economic Forum at Davos 2026 described the messy middle as the gap between AI demonstration and broad adoption. Technologies stall not because they fail but because institutions cannot absorb the change fast enough, creating a disconnect between strategic ambition and daily workflow. - **What is the translation layer organizations need for AI adoption?** The translation layer is not more technology or another strategy deck. It is someone who can convert institutional ambition into workflow reality by asking what stops when the new thing starts. When employees route around AI strategy, the problem is workflow fit, not the tool itself. I spent part of last week reading the articles that came out of Davos. The World Economic Forum had convened its usual panels on technology and scale, and one phrase from the coverage stuck with me: what they called the "messy middle between demonstration and broad adoption."[^1] It's a useful idea. Technologies don't stall because they fail. They stall because the institutions trying to adopt them can't absorb the change fast enough. The panels were thoughtful. Saudi Aramco reported roughly six billion dollars in realized value from technology integration, about half from AI. The diagnosis was careful, credible, and aimed at the right problem. And then I thought about the person who was never there. ![A conference stage with bright lights and large screens, viewed from an empty hallway through a slightly open door](../../assets/images/focus/inline/davos-and-the-dual-reality/stage-distance.jpg) *The diagnosis is correct. The patient isn't in the building.* ## Two Realities, One Organization The same week those panels were happening, a survey of 5,000 white-collar workers told you where that messy middle actually lives. Forty percent of employees said AI saves them no time at all. Only two percent of executives said the same.[^2] That's not a rounding error. That's two populations describing different realities in the same organization. This got me thinking about what I keep seeing with clients. The leaders who champion AI have lived through the uncertainty, debated trade-offs, earned their clarity. By announcement day, the strategy feels overdue. For the rest of the organization, it arrives as interruption. Another tool, another login, another thing to manage on top of everything that was already full. A separate survey found 31 percent of employees actively sabotaging their company's AI efforts.[^3] Not because they're Luddites. Because the sanctioned tools don't solve problems employees actually have. Meanwhile, 60 percent use unsanctioned shadow AI tools just to meet deadlines.[^4] They're not resisting the technology. They're routing around the strategy. ![A computer monitor showing a dashboard of green metrics, while a sticky note on the screen reads "this doesn't work"](../../assets/images/focus/inline/davos-and-the-dual-reality/dashboard-note.jpg) *The dashboard says adoption. The sticky note says otherwise.* ## The Translation Layer You can perfectly diagnose the absorption problem from a stage in Switzerland and still have no mechanism to reach the person on the office floor who just logged into the AI tool, let it run in the background, and kept working the old way. The Davos panel isn't wrong about anything. That's what makes the dual reality so revealing. The institutional language, how ideas spread, who funds the patience, how to retrain the workforce, none of it is incorrect. But it lives at a different altitude than the employee doing quiet arithmetic: does this tool make my day shorter, or does it add a new thing I have to manage? I wrote about GM's seat bracket a few weeks ago, a part their AI designed that the factory couldn't build. That was a gap between what AI could imagine and what organizations could produce. This is a different pattern. The gap isn't between AI and the organization anymore. It's between two groups of people inside the same organization, both telling the truth about their own experience, neither able to see the other's. What sits between them is a translation layer. Not more technology, not another strategy deck. Someone who can convert institutional ambition into workflow reality. Someone who asks what stops when the new thing starts. When 31 percent of your workforce is quietly working around your AI strategy, you don't have a technology problem. You have a workflow problem. The tool works. It just doesn't fit the work. No amount of panels will fix that. But someone willing to walk between both floors might. --- ## References [^1]: World Economic Forum. (2026). "How we can deploy innovation and technology at scale and responsibly." [WEF](https://www.weforum.org/stories/2026/01/the-hard-part-of-innovation-how-technologies-diffuse-and-why-institutions-matter) [^2]: Section survey of 5,000 white-collar workers, reported by Mashable. (2026). "Does AI save time? Executives say yes, employees say no." [Mashable](https://mashable.com/article/ai-report-time-saved-workplace-executives-workers) [^3]: Writer & Workplace Intelligence. (2026). "GenAI's Silent Rebellion." [WebProNews](https://www.webpronews.com/genais-silent-rebellion-why-workers-ignore-executive-ai-mandates) [^4]: BlackFog. (2026). "Corporate workers lean on shadow AI to enhance speed." [Cybersecurity Dive](https://www.cybersecuritydive.com/news/corporate-workers-shadow-ai-speed/810721) --- ### Finding Your Room **URL:** https://odysseyalive.com/focus/finding-your-room **Published:** January 27, 2026 **Category:** Groundwork **Tags:** social-media, marketing, business-strategy, linkedin, platforms **Purpose:** This article argues that B2B businesses waste effort posting across every social platform instead of committing to the one where their audience gathers. It compares each major platform to a different room at a party and uses engagement data to show why LinkedIn is the primary venue for professional thought leadership. **FAQ:** - **Which social media platform is best for B2B thought leadership?** LinkedIn is the strongest platform for B2B thought leadership. It generates 80% of all B2B social media leads and delivers 2x higher conversion rates than other platforms. 89% of B2B marketers use it for lead generation, making it the conference hallway where professional buyers actually gather. - **Why does the same content perform differently on different platforms?** Each platform functions like a different room with its own conversational norms. LinkedIn rewards professional insights, Instagram rewards visual storytelling, and X rewards sharp debate. Content that resonates in one room may get ignored in another because the audience came with different expectations. - **What happened to Facebook's effectiveness for business marketing?** Facebook's organic reach for business pages has dropped to 1-2%, and engagement rates fell 36% year-over-year. The article compares it to a neighborhood block party that's slowly emptying out, with an older-skewing audience where local businesses can still find customers but with diminished energy. - **How has X's user engagement changed?** X engagement rates dropped 48.3% year-over-year, and daily active users declined from 259 million to 132 million since 2022. The article describes it as an argument at the bar that fewer people are joining, where the remaining users are passionate but most professional opportunities happen elsewhere. I posted the same thought on two platforms last week. LinkedIn lit up. X went silent. Not a ripple. I stared at my phone, watching the notifications roll in on one app while the other sat there, that little number stubbornly stuck at one, me. The same words. The same insight about how organizations struggle to absorb change. One audience leaned in. The other walked right past. This got me thinking about rooms. ## Different Rooms, Different Conversations Every platform is a room at a party. The problem isn't usually your message. It's that you're speaking in the wrong venue. LinkedIn is the conference hallway.[^1] People in clusters, coffee in hand, exchanging cards and insights. They're there to work the room, but they're also genuinely curious about what you've learned. Professional, but human. The conversation is about ideas that might help. ![Professional networking in a conference hallway](../../assets/images/focus/inline/finding-your-room/conference-hallway.jpg) *The conference hallway, where people came ready to listen.* Instagram is the gallery opening. Everyone's there for the aesthetic. The wine, the light, the carefully curated walls. Your presence matters as much as your words. Visual storytelling isn't optional. It's the entire point. Facebook is the neighborhood block party that's slowly emptying out.[^2] Your neighbor's there, your old college roommate, some guy from that job you had in 2009. The crowd skews older now. Local businesses still find their people here, but the energy's different than it used to be. X is the argument at the bar that fewer people are joining.[^3] The room got smaller. The people left standing are passionate, sometimes combative, often brilliant. But most of the handshakes that matter? They happen in the hallway.[^4] ## Finding Your Room ![An art gallery opening with warm lighting](../../assets/images/focus/inline/finding-your-room/gallery-opening.jpg) *A different gathering, a different language.* The pattern I keep noticing: businesses exhaust themselves posting everywhere when they should be speaking somewhere. B2B thought leadership belongs in the conference hallway. Visual brands, the ones selling a lifestyle or an aesthetic, belong at the gallery. Local shops still have the block party. The mistake isn't creating bad content. It's broadcasting to empty rooms while ignoring the one where your people actually gather. Find your room. Learn its language. Speak to the people who came ready to listen. That silence on X? An empty chair. The conference hallway was waiting the whole time. > **Update:** I've since revisited this advice. Telling someone to "find your room" assumes they can walk between them freely. Most people can't, and the reason goes deeper than habit. Read the follow-up: [The Room You Chose](/focus/the-room-you-chose). --- ## References [^1]: 80% of B2B leads generated through social media come from LinkedIn, and 89% of B2B marketers use the platform for lead generation. Sopro (2025). ["LinkedIn Lead Generation Statistics."](https://sopro.io/resources/blog/linkedin-lead-generation-statistics/) [^2]: Facebook business page organic reach has dropped to 1-2%, and engagement rates fell 36% year-over-year. Marketing Scoop (2025). ["The Decline of Facebook Organic Reach."](https://www.marketingscoop.com/marketing/the-decline-of-facebook-organic-reach-what-marketers-need-to-know-in-2024/) [^3]: X engagement rates dropped 48.3% year-over-year, and daily active users declined from 259 million to 132 million since 2022. Business of Apps (2026). ["X Revenue and Usage Statistics."](https://www.businessofapps.com/data/twitter-statistics/) [^4]: LinkedIn generates 80% of all B2B social leads and delivers 2x higher conversion rates than other platforms. Cognism (2026). ["Essential LinkedIn Statistics."](https://www.cognism.com/blog/linkedin-statistics/) --- ### It's the Harness, Not the Model **URL:** https://odysseyalive.com/focus/harness-not-model **Published:** January 23, 2026 **Category:** Groundwork **Tags:** ai, architecture, transparency **Purpose:** This article argues that AI orchestration should live in an external harness rather than inside recursive model calls. It contrasts the opacity of models calling themselves as sub-agents with the traceability of harness-based orchestration, making the case that visibility and auditability outweigh token efficiency gains. **FAQ:** - **What is an AI harness versus recursive model orchestration?** A harness wraps around the model and handles tool access, approval gates, and context management externally, keeping every decision logged and traceable. Recursive orchestration has the model call itself as sub-agents, which is token-efficient but produces opaque decision chains where intermediate reasoning is compressed and lost. - **Why does the article favor harness-based AI architecture?** Harness-based architecture produces logs for every decision, tool call, and data path. When a regulator asks how an AI reached a conclusion, harness logs provide a traceable answer. Recursive models compress intermediate reasoning at each level, making failures nearly impossible to diagnose in production systems. - **What is the tradeoff between token efficiency and visibility in AI systems?** Recursive model decomposition uses fewer tokens than harness-orchestrated calls. However, the article argues that token costs are collapsing and context windows are expanding, while regulatory compliance costs and debugging difficulty are not decreasing. The tradeoff favors spending more tokens for greater visibility. - **Why does the article say observation requires distance?** The article uses a mechanic analogy: you fix a car from outside the engine compartment, not from inside while it is running. Similarly, AI orchestration logic must live outside the model where engineers can see, log, and debug it, rather than inside opaque recursive calls. I was reading an article the other day, one a podcaster I follow had been discussing.[^1] The thesis was elegant: language models should orchestrate their own reasoning by calling themselves as sub-agents, spawning child instances like digital matryoshka dolls. Technically impressive. Benchmark numbers that make investors salivate. And yet something nagged at me. I kept thinking about my mechanic. He doesn't try to fix my car from inside the engine compartment while it's running. Observation requires distance. Control requires access. When a recursive model fails on a complex task, you're left playing archaeological detective. It called itself three times, condensed context at each level, made decisions at junctions you can't see. Somewhere in that recursive stack, something went sideways. Where? You don't know. You can't know. The intermediate reasoning evaporated, compressed into whatever summary the model deemed relevant at the time. This is fine for research papers. It's catastrophic for production systems where a regulator might ask "how did your AI reach this conclusion?" and you need an answer that isn't a shrug wrapped in technical jargon.[^2] ![Server room corridor with rows of black server racks](../../assets/images/focus/inline/harness-not-model/server-room.jpg) *Black boxes all the way down.* ## The Harness What struck me was how simple the alternative is. A harness wraps around the model. The model's job becomes almost monastic: take input, reason, produce output. Nothing more. Everything else, the tool access, the approval gates, the context management, lives in the harness. Outside the model. Where you can see it. ![Monitoring station at night with glowing screens](../../assets/images/focus/inline/harness-not-model/monitoring-station.jpg) *Where you can see it.* When recursion happens inside the model, you get elegance and opacity in equal measure. When it happens in the harness, you get logs. Every decision, every tool call, every data path, recorded and traceable. The recursion advocates have a point about token efficiency. Recursive decomposition uses fewer tokens than harness-orchestrated calls. But token costs are collapsing. Context windows are expanding. Meanwhile, regulatory compliance doesn't get cheaper.[^3] Debugging production failures doesn't get easier.[^4] The tradeoff crystallizes: spend more tokens, gain visibility. ## Observation Requires Distance I think what's really happening is that the industry is exhausted by black boxes. We've spent years dealing with models we can't interpret, decisions we can't explain, failures we can't diagnose. And the response from some quarters has been more black boxes? Recursive calls inside opaque models, complexity hidden behind complexity? It's not the model's job to be recursive. Orchestration is a systems problem, not an intelligence problem. When we keep it in the harness, we keep it where we can explain it to the regulator, the stakeholder, the engineer staring at a failed job at 3 AM. My mechanic knows this. You fix the car from the outside, where you can see what you're doing. --- ## References [^1]: Gupta, A. (2026). "2025 Was Agents. 2026 Is Agent Harnesses." [Medium](https://aakashgupta.medium.com) [^2]: IBM (2025). "Building Trustworthy AI Agents for Compliance." [IBM Think](https://www.ibm.com/think/insights/building-trustworthy-ai-agents-compliance-auditability-explainability) [^3]: Deloitte (2025). "Unlocking Exponential Value with AI Agent Orchestration." [Deloitte Insights](https://www.deloitte.com/us/en/insights/industry/technology/technology-media-and-telecom-predictions/2026/ai-agent-orchestration.html) [^4]: Liu, J., et al. (2025). "Large Language Model Guided Self-Debugging Code Generation." [arXiv](https://arxiv.org/html/2502.02928v2) --- ### AI Needs Two Context Windows **URL:** https://odysseyalive.com/focus/ai-needs-two-context-windows **Published:** January 22, 2026 **Category:** Groundwork **Purpose:** This article proposes that language models need a small, protected executive context window alongside the main conversation window to prevent instructions from fading during long sessions. It draws parallels to CMOS memory in computers and prefrontal cortex function in the human brain, citing Stanford research on the 'lost in the middle' problem. **FAQ:** - **What is the lost in the middle problem in AI?** A 2024 Stanford study found that language models perform best when relevant information sits at the beginning or end of the context window but struggle when it is buried in the middle. During long conversations, early instructions get diluted by later messages and effectively stop being consulted. - **What is the two context windows proposal?** The proposal suggests giving language models a small executive window for persistent instructions and guardrails alongside the large main window for conversation. The executive window would always be consulted first and never diluted, similar to how CMOS memory holds foundational settings separate from RAM. - **How does CMOS memory relate to AI context windows?** CMOS is a chip in every computer that holds roughly 256 bytes of foundational settings, powered by a coin-sized battery. It remembers critical instructions like boot order and drive location even when the system loses power. The article uses it as an analogy for a small, protected AI instruction space. - **How would an executive context window prevent jailbreaking?** Anthropic documented that flooding a model with structured text can override safety training through many-shot jailbreaking. An architecturally separate executive window would not be subject to these attacks because its contents could not be diluted or overridden by conversation-level input. - **What role does the prefrontal cortex play in the analogy?** The prefrontal cortex acts as an executive controller in the human brain, maintaining goals and rules while the rest of the brain processes information. When it is damaged, people can still process information but lose the ability to stay on task and hold boundaries, mirroring how AI instructions fade in long sessions. Last week I was three hours into building an automation when the model started ignoring the output format I'd specified at the beginning. Same session. Same instructions sitting right there in the conversation history. But somewhere around message forty, the format guidance had become wallpaper. Present but no longer consulted. I scrolled back and found my original instructions exactly where I'd left them. The model hadn't forgotten them in any literal sense. They'd just... faded. Diluted by everything that came after. ![A handwritten letter on an old desk, the first lines crisp and dark, dissolving into illegibility toward the bottom](../../assets/images/focus/inline/ai-needs-two-context-windows/fading-letter.jpg) *What early instructions start to feel like by message forty.* Researchers call this "lost in the middle." A 2024 study from Stanford found that language models perform best when relevant information sits at the beginning or end of their context window, but struggle when it's buried in the middle.[^1] The instructions that mattered most had become middle. This got me thinking about an old problem computers solved decades ago. ## The Coin-Sized Solution Inside every computer sits a tiny chip called CMOS, powered by a battery roughly the size of a quarter. It holds maybe 256 bytes of data. Less than a text message. But that small memory does something essential: it remembers the instructions that matter most, even when everything else loses power.[^2] The CMOS doesn't store your documents or run your programs. It holds foundational settings: how to find the hard drive, what time it is, which device to boot from first. The rest of the system juggles gigabytes. Those 256 bytes stay constant, always present, always consulted first. ## How Brains Do It Human cognition works similarly. The prefrontal cortex acts as an executive controller, maintaining goals and rules while the rest of the brain processes sensory information.[^3] It doesn't store everything. It maintains what matters. Your intentions. The thing you're trying not to forget while you're distracted by something else. ![An airport control tower at night, a silhouetted figure watching over the busy runway below](../../assets/images/focus/inline/ai-needs-two-context-windows/control-tower.jpg) *The executive function: small, persistent, always watching.* When the prefrontal cortex is damaged, people can still perceive and process information. What they lose is the ability to stay on task, to remember why they started, to hold boundaries in place while everything else flows by. ## Two Windows What if language models had something similar? Not one vast context window where everything competes for attention, but two: a large workspace for conversation, and a smaller executive window that never fades. The executive window would hold the persistent instructions and guardrails. It would sit above the conversation, always consulted, never diluted by the growing pile of messages below. The main window could stretch to millions of tokens. The executive window might need only a few hundred. But those few hundred would be inviolable. Anthropic documented how flooding a model with carefully structured text can override safety training entirely, a technique called "many-shot jailbreaking."[^4] The instructions that were supposed to matter most get lost in the noise. An executive window wouldn't be subject to these attacks. It would be architecturally separate, like CMOS is separate from RAM. ## The Pattern We've solved this problem before. Computers needed persistent instructions that survived the chaos of runtime. Brains needed executive function that maintained goals through distraction. A small, protected space where the instructions that matter most can live without being forgotten. We should build it. --- ## References [^1]: Liu, N., et al. (2024). "Lost in the Middle: How Language Models Use Long Contexts." *Transactions of the Association for Computational Linguistics*, 12, 157-173. [MIT Press](https://direct.mit.edu/tacl/article/doi/10.1162/tacl_a_00638/119630/Lost-in-the-Middle-How-Language-Models-Use-Long) [^2]: Wikipedia contributors. (2024). "Nonvolatile BIOS memory." [Wikipedia](https://en.wikipedia.org/wiki/Nonvolatile_BIOS_memory) [^3]: Friedman, N. & Robbins, T. (2022). "The role of prefrontal cortex in cognitive control and executive function." *Neuropsychopharmacology*, 47, 72-89. [Nature](https://www.nature.com/articles/s41386-021-01132-0) [^4]: Anthropic. (2024). "Many-shot jailbreaking." [Anthropic Research](https://www.anthropic.com/research/many-shot-jailbreaking) --- ### The Toggle **URL:** https://odysseyalive.com/focus/the-toggle **Published:** January 20, 2026 **Category:** Groundwork **Tags:** geo, ai-search, cloudflare, seo, visibility **Purpose:** This article examines whether businesses should block AI crawlers like GPTBot and ClaudeBot. It presents Cloudflare crawl-to-refer ratio data, a Rutgers-Wharton study showing publishers lost 23% of traffic after blocking, and argues that structured, citable content on a server-rendered site is the better strategy in a zero-click search environment. **FAQ:** - **What happens when publishers block AI crawlers?** A Rutgers and Wharton study found that major news publishers who blocked AI crawlers experienced a 23% drop in total traffic, with human traffic falling 14%. Blocking removed them from AI-generated answers entirely, and the AI simply cited competing sources instead of protecting the publisher's value. - **What are AI crawler crawl-to-refer ratios?** Cloudflare data shows extreme imbalances between pages crawled and traffic referred. Anthropic's ClaudeBot scrapes 73,000 pages for every visitor it sends back. OpenAI's GPTBot runs at a 1,091-to-1 ratio. These numbers make blocking feel intuitive, but the data shows allowing access yields better outcomes. - **How does being cited in AI answers affect website traffic?** Brands cited in AI answers earn 35% more organic clicks, and the traffic that arrives through AI citations converts at 4.4 times the rate of traditional search traffic. The volume is smaller but the intent is significantly higher, making AI citation a valuable source of qualified visitors. - **What kind of content gets cited by AI systems?** AI systems cite content they can attribute: specific statistics, named sources, and quotable claims. Vague assertions get passed over. Content also needs schema markup for structure and must be server-rendered HTML, since AI crawlers don't execute JavaScript and skip client-side rendered pages. I've been staring at a Cloudflare dashboard. The names scroll past like a rap sheet. GPTBot. ClaudeBot. PerplexityBot. Bytespider. Next to each one, a toggle. Allow or Block. The crawl-to-refer ratios feel like theft. Anthropic's Claude scrapes 73,000 pages for every visitor it sends back. OpenAI runs at 1,091 to 1.[^1] The instinct is obvious. Block them all. My finger hovers. Then I remember the study. ![A web of connected documents, some illuminated and prominent, others fading into obscurity](../../assets/images/focus/inline/the-toggle/citation-web.jpg) *Some sources get cited. Others disappear.* ## The Counterintuitive Math Researchers at Rutgers and Wharton tracked what happened when major news publishers blocked AI crawlers.[^2] They expected to see protected value. Instead they found a 23% drop in total traffic. Human traffic fell 14%. The assumption had been wrong. Blocking didn't preserve anything. It removed publishers from the answer entirely. This got me thinking about what's actually happening when someone asks an AI a question. Block the crawl on your site, and the AI still answers the user's question. It just cites someone else's site. In a world where 58% of searches end without a click, the question isn't whether to feed the system. It's whether to be part of the answer. ## Making the Crawl Count If you're going to allow access, make what they find worth citing. AI crawlers need structure to understand what they're reading. Schema markup labels your content the way a librarian labels books. Author, topic, date, relationships. Without it, you're a pile of loose pages. ![Server architecture rendered in watercolor with visible structural scaffolding and warm amber data flows](../../assets/images/focus/inline/the-toggle/structured-foundation.jpg) *Structure isn't decoration. It's how you get found.* The content itself matters differently now. AI cites what it can attribute. Specific statistics, named sources, quotable claims. Vague assertions get passed over. And here's the technical wrinkle most miss: AI crawlers don't execute JavaScript. If your content renders client-side, it doesn't exist to them. Headless Chrome scraping is expensive and generally avoided. Server-rendered HTML is what counts. ## The New Bargain The old deal with search engines was simple. You let them crawl, they sent traffic. That deal is broken. The crawl-to-refer ratios prove it. But a new deal is forming. You let them crawl, you become a source they trust. Brands cited in AI answers earn 35% more organic clicks.[^3] The traffic that does arrive converts at 4.4 times the rate of traditional search.[^4] Smaller volume, higher intent. I'm back at the dashboard. The toggle sits there, patient. The instinct still says Block. The data says Allow. Not because it's fair. Because in a zero-click world, visibility in the answer is becoming the only visibility that matters. Set it to Allow. Then give them something worth citing. > **Update:** Allowing the crawl was step one. Step two is making sure what they find actually represents you. I followed my own advice and looked at my site through a crawler's eyes. It wasn't pretty. Read the follow-up: [Your Page's Resume](/focus/the-pages-resume). --- ## References [^1]: Cloudflare. (2025). "The crawl-to-click gap: Cloudflare data on AI bots, training, and referrals." [Cloudflare Blog](https://blog.cloudflare.com/crawlers-click-ai-bots-training/) [^2]: Jiang, Y., et al. (2025). "The Impact of Blocking AI Crawlers on Publisher Traffic." Rutgers Business School / The Wharton School. [PPC Land](https://ppc.land/blocking-ai-crawlers-backfired-news-publishers-lost-23-of-traffic/) [^3]: WordStream. (2026). "GEO vs. SEO: Everything to Know in 2026." [WordStream](https://www.wordstream.com/blog/generative-engine-optimization) [^4]: Superprompt. (2025). "AI Traffic Surges 527% in 2025." [Superprompt](https://superprompt.com/blog/ai-traffic-up-527-percent-how-to-get-cited-by-chatgpt-claude-perplexity-2025) --- ### The Seat Bracket That Couldn't Ship **URL:** https://odysseyalive.com/focus/the-seat-bracket-that-couldnt-ship **Published:** January 16, 2026 **Category:** AI Transformation **Tags:** organizational-change, implementation, pattern-recognition **Purpose:** This article examines the gap between what AI can design and what organizations can actually produce, using GM's generative-AI seat bracket as its central case. It argues that the real constraint on AI adoption is not technology capability but organizational capacity to absorb what AI creates. **FAQ:** - **What happened with GM's AI-designed seat bracket?** Autodesk's generative AI designed a seat bracket for GM that was 40% lighter and 20% stronger than the original. However, producing it required 3D printing at scale, which did not fit GM's steel-stamping supply chain. The bracket remained a proof-of-concept with no announced production plans. - **Why do companies abandon AI initiatives?** According to S&P Global Market Intelligence, 42% of companies abandoned most of their AI initiatives in 2025. The article argues the cause is not AI failure but an absorption gap: the distance between what AI can imagine and what organizations are operationally built to receive and implement. - **How does Apple's approach to AI differ from GM's?** Apple controls its supply chain, manufacturing, and product integration. When Apple's machine-learning tools designed ultra-thin metalenses, the company had the organizational capacity to move toward production. Analyst projections placed metalenses in Face ID sensors by 2026. Same technology wave, different capacity to ride it. - **What is the absorption gap in AI adoption?** The absorption gap is the distance between what AI can produce and what an organization is built to receive. It is not a technology gap but an operating model gap involving decision-making, supplier relationships, and production infrastructure. Closing it requires rewiring how organizations work, not just upgrading software. I've been thinking about a seat bracket. Not just any seat bracket. One that looks like it was grown rather than designed. Picture an aluminum lattice, organic and airy, the kind of structure you'd expect to find in bone or coral. Forty percent lighter than the original. Twenty percent stronger. When GM's engineers first saw what Autodesk's generative AI had produced, I imagine there was a moment of genuine wonder. Here was a part that had evolved past human imagination. Then someone asked the obvious question: How do we make this? ![An intricate lattice part sitting on a worn workbench surrounded by vintage machinery](../../assets/images/focus/inline/the-seat-bracket-that-couldnt-ship/mismatch.jpg) *The part doesn't belong here. That's the whole problem.* GM's supply chain has been stamping steel for decades. Supplier relationships, tooling investments, production lines. All optimized for a particular way of making things. The bracket required 3D printing, a technology GM uses but hasn't scaled for mass production. The part was brilliant. The system that would need to produce it existed in a different reality. The bracket appears to have remained a proof-of-concept. GM mentioned motorsports applications first, consumer vehicles later. As of now, no production plans have been announced. ## The Pattern Worth Noticing This got me thinking about a pattern I keep seeing. Forty-two percent of companies abandoned most of their AI initiatives in 2025.[^1] Not because the AI failed. Usually it worked fine. The constraint was absorption. The distance between what AI can imagine and what organizations are built to receive. ![An empty conference room with a presentation still glowing on screen, chairs pushed back, coffee cups left behind](../../assets/images/focus/inline/the-seat-bracket-that-couldnt-ship/abandoned-initiative.jpg) *The meeting ended. The follow-up never came.* Here's what makes it interesting. Around the same time, Apple was experimenting with metalenses. Ultra-thin optical components designed through machine learning. Different industry, similar ambition. But Apple controls its supply chain, its manufacturing, its product integration. When their AI imagined something new, they could actually make it. Analyst projections have metalenses in Face ID sensors by 2026. Same technology wave. Different organizational capacity to ride it. ## What We Keep Missing We keep asking whether AI is ready. Whether it's smart enough, capable enough. The seat bracket suggests we're asking the wrong question. GM's AI was plenty smart. It designed something genuinely better. The problem was that GM the organization couldn't metabolize what GM the AI lab produced. This is the gap that doesn't show up in demos or vendor pitches. It's not a technology gap. It's a muscle memory gap. An operating model gap. The kind of gap that takes years to close, because it's not about upgrading software. It's about rewiring how an organization makes decisions, builds relationships, moves resources. The bracket sits somewhere between triumph and cautionary tale. A reminder that before asking what AI can do for us, we might ask what we're actually built to receive. Forty percent lighter. Twenty percent stronger. Still waiting for an organization ready to make it real. --- ## References [^1]: S&P Global Market Intelligence. (2025). "AI experiences rapid adoption, but with mixed outcomes." [CIO Dive](https://www.ciodive.com/news/AI-project-fail-data-SPGlobal/742590/) --- ### Reskill Yesterday **URL:** https://odysseyalive.com/focus/reskill-yesterday **Published:** January 9, 2026 **Category:** AI Transformation **Tags:** ai, reskilling, workforce, culture **Purpose:** This article examines how AI threatens the outsourced work that built India's middle class, drawing parallels to automation risks facing front-line workers globally. It explores which human skills survive automation and why reskilling efforts are urgently overdue. **FAQ:** - **How many people does India's outsourcing industry employ?** India's outsourcing industry employs over 10 million people and handles 56% of the world's business process outsourcing, according to Ken Research. The work follows American hours and solves American problems, a cultural bargain that built a middle class over three decades. - **Why are front-line workers most at risk from AI automation?** Front-line workers perform the most scriptable, routine tasks, exactly the kind AI automates fastest. Yet Gallup data shows only 9% of front-line workers use AI frequently, compared to 33% of leaders. The people whose jobs are most vulnerable are least equipped with the tools that could help them adapt. - **What human skills can AI not replicate?** MIT Sloan researchers identified empathy, judgment, and the ability to visualize possibilities beyond reality as capabilities AI cannot replicate. These are the skills that never fit a script, such as sensing when a frustrated customer needs something the standard process does not cover. - **Why is reskilling urgent for 2026?** AI use in American workplaces has nearly doubled in two years. The qualities that made work outsourceable, being rote, standardized, and scriptable, now make it automatable. Organizations that delay reskilling risk leaving their workforce behind a transition already underway. It's 2 AM in Bangalore. In a fluorescent-lit office park, a woman named "Jennifer" is explaining a billing discrepancy to someone in Ohio. Her real name is Priya. She's been Jennifer for six years now, ever since the accent training taught her to flatten her vowels and bury what the industry calls "mother tongue influence."[^1] This is the graveyard shift. Not just a schedule, but a cultural bargain struck over three decades: work American hours, adopt American names, solve American problems. In return, India built a middle class. Over 10 million people employed. 56% of the world's business process outsourcing.[^2] The deal worked because humans were cheaper than geography. ## The Irony Nobody Saw Coming Here's what makes an anthropologist wince: the same qualities that made this work outsourceable make it automatable. Rote. Standardized. Scriptable. Sociologist Shehzad Nadeem noted years ago that outsourced work rarely produces upward mobility because most of it is, by design, routine.[^3] The scripts Jennifer memorized? AI doesn't need to memorize. It generates. ![An empty office desk with abandoned headset, computer screen glowing in the darkness](../../assets/images/focus/inline/reskill-yesterday/empty-desk.jpg) *The scripts she memorized are exactly what AI masters fastest.* ## The Gap Nobody Talks About The pattern repeats closer to home. AI use in American workplaces has nearly doubled in two years.[^4] But here's the twist buried in the data: leaders use it frequently (33%), while front-line workers barely touch it (9%).[^4] The people whose jobs are most scriptable are the least equipped with the tools that could make them irreplaceable. I imagine Jennifer has heard about these tools. Maybe seen a demo in a team meeting, watched someone in management pull up a chatbot that could write the same scripts she spent years perfecting. The graveyard shift isn't just in Bangalore anymore. ## What Survives the Night MIT Sloan researchers identified what AI cannot replicate: empathy, judgment, and what they poetically called "the visualization of possibilities beyond reality."[^5] The ability to sense when a frustrated customer needs something the script doesn't cover. The intuition that comes from six years of midnight conversations with strangers. ![Two hands reaching toward each other, one human and one digital, meeting in collaboration](../../assets/images/focus/inline/reskill-yesterday/human-connection.jpg) *What AI cannot replicate: empathy, judgment, hope.* The skills that could be scripted could be outsourced. The skills that could be outsourced can now be automated. What's left are the things that never fit the script in the first place. ## The Question Back in Bangalore, the sun is rising as Jennifer's shift ends. She walks past the training room where she learned to be Jennifer. Someone new is in there now, practicing vowels, learning scripts. The question isn't whether those jobs change. It's whether the humans in them get to change with them. Your reskilling plan for 2026 should have started yesterday. But today works too. --- ## References [^1]: Nielsen, K.B. (2025). "Mother Tongue Influence and Global English: Creating 'Neutral' Elites in Delhi's Business Processing Outsourcing Industry." [American Anthropologist](https://anthrosource.onlinelibrary.wiley.com/doi/full/10.1111/aman.28078) [^2]: Ken Research. (2025). "India IT Outsourcing Market Report." [Ken Research](https://www.kenresearch.com/industry-reports/india-it-outsourcing-market) [^3]: Nadeem, S. (2015). "Indian Arrivistes and Cyber Coolies: Reflections on Global Outsourcing and the Middle Class." [Sociology Compass](https://compass.onlinelibrary.wiley.com/doi/10.1111/soc4.12255) [^4]: Gallup. (2025). "AI Use at Work Has Nearly Doubled in Two Years." [Gallup](https://www.gallup.com/workplace/691643/work-nearly-doubled-two-years.aspx) [^5]: MIT Sloan. (2025). "These Human Capabilities Complement AI's Shortcomings." [MIT Sloan](https://mitsloan.mit.edu/ideas-made-to-matter/these-human-capabilities-complement-ais-shortcomings) --- ### Welcome to Odyssey Alive **URL:** https://odysseyalive.com/focus/welcome **Published:** January 1, 2026 **Category:** Field Notes **Tags:** introduction, ai-automation, philosophy **Purpose:** This article introduces Odyssey Alive's consulting philosophy: building AI automation that clients own and understand, rather than creating dependency on outside experts. It explains why most AI deployments fail and how transferring capability to the client changes outcomes. **FAQ:** - **Why do most AI deployments fail?** According to NTT DATA, 70-85% of generative AI deployments fail to meet their ROI targets. The World Economic Forum identifies the 'black box problem' as a key factor: when users cannot understand how a system reaches its conclusions, they stop trusting it and eventually abandon it. - **What does Odyssey Alive do differently from other AI consultants?** Odyssey Alive builds systems the client owns and understands. The goal is that when the consultant leaves, the capability stays. Automation is designed to fit how people actually work and to make existing expertise more valuable rather than obsolete. - **What does the name Odyssey Alive mean?** The name reflects a philosophy. 'Odyssey' acknowledges that organizational change is not a straight line but a journey full of detours and discoveries. 'Alive' is a reminder that technology exists to serve living, breathing organizations, not the other way around. The question came near the end of a discovery call last year. We'd spent an hour talking through workflows, pain points, the usual. Then she paused. "What happens when you leave?" Not hostile. Just honest. She'd been through this before. A consultant with impressive tools and confident promises. Something got built. It worked. Everyone celebrated. Then the consultant moved on to the next client, and slowly, imperceptibly, things started to break. No one knew how to fix it. No one understood why it worked in the first place. The documentation was either missing or incomprehensible. What was supposed to be transformation became a new kind of dependency. ![A compass resting on a worn map, watercolor style](../../assets/images/focus/inline/welcome/compass-map.jpg) *The destination matters. So does knowing how to get there yourself.* ## The Key Stays With You Seventy percent of AI deployments fail to meet their ROI targets.[^1] The World Economic Forum calls it the black box problem: when users can't understand how a system reaches its conclusions, they stop trusting it.[^2] Systems people don't trust are systems that eventually get abandoned. But here's what I've learned: the organizations that succeed aren't the ones with the fanciest tools. They're the ones who understand what was built and can evolve it after the consultant leaves. So that's what I build for. Systems you own and understand. Automation that fits how your people actually work, not how a vendor wishes they worked. Tools that make your existing expertise more valuable, not obsolete. When I leave, the capability stays. The key stays with you. ## The Name "Odyssey Alive" started as a placeholder and became a philosophy. An odyssey isn't a straight line. It's the long way around, full of detours and discoveries and the occasional monster. The journey matters as much as the destination. "Alive" is the reminder that technology exists to serve living, breathing organizations. Not the other way around. Every organization is on its own odyssey. I'm here to help keep it moving. --- *Ready to build something that actually fits how you work? [Start a conversation](/contact).* --- ## References [^1]: NTT DATA (2024). "Between 70-85% of GenAI deployment efforts are failing to meet their desired ROI." [NTT DATA Insights](https://www.nttdata.com/global/en/insights/focus/2024/between-70-85p-of-genai-deployment-efforts-are-failing) [^2]: World Economic Forum (2024). "Building trust in AI means moving beyond black-box algorithms." [WEF Stories](https://www.weforum.org/stories/2024/04/building-trust-in-ai-means-moving-beyond-black-box-algorithms-heres-why/) --- ### Your New Research Partner **URL:** https://odysseyalive.com/focus/your-new-research-partner **Published:** December 25, 2025 **Category:** Groundwork **Tags:** ai, research, productivity, knowledge-work, collaboration **Purpose:** This article reframes AI as a tireless research librarian rather than an oracle, emphasizing that clarity of questioning is the most important skill for getting value from AI research tools. It covers both the strengths of AI-assisted research and its critical limitations, including hallucinated citations and outdated information. **FAQ:** - **What is the best mental model for using AI as a research tool?** The article recommends thinking of AI as a very fast librarian with infinite patience and no closing time. Like a good librarian, AI understands the architecture of knowledge and suggests connections, but it does not know your context or goals. The human still provides direction and writes the thesis. - **What is the most important skill for AI-assisted research?** Clarity of questioning is the skill that matters most. Specific questions outperform vague ones. The article gives an example: asking 'What are the main arguments for and against X?' produces far better results than asking 'Tell me about X.' Good prompts usually start as worse ones that get refined. - **What are the risks of using AI for research?** AI can confidently present outdated information, miss nuances that require lived experience, and fabricate sources that sound plausible but do not exist. The article warns that the author has personally chased phantom citations that turned out to be inventions, and advises verifying everything. - **How does AI change the research process?** Research shifts from a solo climb through sources to a conversation with a knowledgeable colleague who has broad recall but no skin in the game. AI can surface cross-disciplinary connections, summarize dense papers in minutes, and work at any hour, but the human remains responsible for judgment and synthesis. I was three hours into a research rabbit hole last month, drowning in browser tabs, when I remembered I wasn't alone anymore. I typed a question into Claude: "What am I missing in my analysis of organizational change resistance?" Not "tell me about change management." A specific question about a specific gap I suspected but couldn't name. The response pointed me toward a 1990s paper on threat rigidity I'd never encountered. Suddenly, the puzzle I'd been circling had a new piece. ![A vast library with a single figure at a reading desk](../../assets/images/focus/inline/your-new-research-partner/library-desk-v2.jpg) *The knowledge was always there. The bottleneck was access.* ## The Librarian Who Never Sleeps The mental model that changed everything for me: AI as a very fast librarian with infinite patience and no closing time. A good librarian doesn't just retrieve books. They understand the architecture of knowledge. They know that what you're asking for might not be exactly what you need. They suggest connections you hadn't considered. AI works similarly. It's "read" more than any human could in a lifetime.[^1] But reading isn't understanding. The model doesn't know your context, your goals, or why this particular question matters to you right now. That's still your job. ![A notebook with handwritten questions, some crossed out and refined](../../assets/images/focus/inline/your-new-research-partner/question-refinement-v2.jpg) *The best prompts usually start as worse ones* ## The Catch This colleague will confidently present outdated information.[^2] They'll miss nuances that require lived experience. They'll occasionally fabricate sources. Yes, really. I've chased phantom citations more than once, only to find they were plausible-sounding inventions. Verify everything. But they'll also surface connections across disciplines you'd never have found. They'll summarize dense papers in minutes. They'll help you think through implications at 2 AM without complaint. The skill that matters most isn't technical sophistication. It's clarity. The people who get the most from AI research tools know how to ask good questions. "What are the main arguments for and against X?" beats "Tell me about X" every time. Research used to be a solo climb up a mountain of sources. Now it's a conversation with a knowledgeable colleague who has perfect recall but no skin in the game. The librarian finds the books. You still write the thesis. --- ## References [^1]: Brown, T., et al. (2020). "Language Models are Few-Shot Learners." [arXiv](https://arxiv.org/abs/2005.14165) [^2]: Ji, Z., et al. (2023). "Survey of Hallucination in Natural Language Generation." [ACM Computing Surveys](https://dl.acm.org/doi/10.1145/3571730) --- ### Why Your Workaround Is Actually Genius **URL:** https://odysseyalive.com/focus/why-your-workaround-is-genius **Published:** December 18, 2025 **Category:** Groundwork **Tags:** automation, organizational-culture, process-design, tacit-knowledge, systems-thinking **Purpose:** This article argues that workplace workarounds, such as unofficial spreadsheets and back-channel processes, encode tacit knowledge that organizations should study before automating away. It uses a real example of a support team's color-coded Google Sheet to illustrate how informal systems often solve problems that official tools miss. **FAQ:** - **What is tacit knowledge in an organization?** Tacit knowledge refers to things an organization knows in practice but not in documentation. The term comes from anthropologist Michael Polanyi's 1966 work The Tacit Dimension. It includes informal processes, unwritten rules, and workarounds that employees develop to solve real problems over time. - **Why do employees resist new systems that replace workarounds?** Employees resist because their workarounds often solve problems the new system does not address. In the article's example, a support team resurrected their old spreadsheet within two weeks because it tracked a type of customer escalation that did not fit the new system's official categories. - **What does excavation before automation mean?** Excavation before automation means observing how people actually work, not how they say they work, before building new systems. It involves finding the person who invented the workaround, understanding what problem it solves, and preserving that embedded judgment in the new design. - **How can workarounds inform better automation design?** Workarounds reveal where official processes have gaps. By studying them, teams can identify bottlenecks, edge cases, and unmet needs that formal systems miss. The best automation amplifies the human judgment already embedded in these informal solutions rather than eliminating it. A few years ago, I watched a company spend six months building an elegant support ticket system to replace a shared Google Sheet that their support team refused to give up. The sheet was ugly. It had seventeen tabs, color-coded rows that only made sense to three people, and a mysterious column labeled "DO NOT DELETE." The new system launched. Within two weeks, the support team had quietly resurrected the spreadsheet alongside it. ![A tangled but functional system of strings and pulleys](../../assets/images/focus/inline/why-your-workaround-is-genius/functional-mess-v2.jpg) *Messy doesn't mean broken* When I asked why, a senior rep pulled up the old sheet and pointed to that mysterious column. It tracked a specific type of customer escalation that didn't fit the official categories but happened often enough to matter. The column had been invented three years earlier by someone who'd since left the company. Nobody remembered adding it. Everyone used it. Anthropologists have a term for this: tacit knowledge.[^1] The things an organization knows in practice but not in documentation. Your company is full of it. ## The Load-Bearing Wall Workarounds are organizational antibodies. They emerge in response to real problems. That Slack channel where people route requests "the back way" might be compensating for a bottleneck nobody talks about. The manual step everyone insists on keeping might catch edge cases the automated system misses. ![A blueprint with both official and unofficial pathways marked](../../assets/images/focus/inline/why-your-workaround-is-genius/blueprint-pathways-v2.jpg) *The real process is rarely the documented one* When we see inefficiency, we want to fix it. That's natural. But "fixing" a workaround without understanding its function is like removing a wall because it's in an inconvenient place. Sometimes that wall is holding up the ceiling. ## Excavation Before Automation The best automation doesn't eliminate human judgment. It amplifies it. But first, you have to understand what judgment is already embedded in the mess. Watch before you build. Spend time observing how people actually work, not how they say they work. Find the person who invented the workaround. They remember why. That ugly spreadsheet might be genius in disguise. Take time to learn its language before you speak over it. --- ## References [^1]: Polanyi, M. (1966). *The Tacit Dimension*. University of Chicago Press. --- ### From Algorithm Opacity to AI Opacity **URL:** https://odysseyalive.com/focus/algorithm-opacity-to-ai-opacity **Published:** December 11, 2025 **Category:** Groundwork **Tags:** algorithms, transparency, social-media, ai-ethics, technology-history **Purpose:** This article traces the progression of algorithmic opacity from Google search rankings to Facebook's News Feed to modern AI language models. It argues that the critical thinking skills people developed questioning search results and social media feeds transfer directly to evaluating AI outputs, while identifying what makes AI opacity distinctly more challenging. **FAQ:** - **What is algorithmic opacity?** Algorithmic opacity is the inability to see why a system produced a particular output. It has been present since the early days of Google search, deepened with Facebook's News Feed ranking, and reached a new level with AI language models whose billions of parameters make outputs difficult for even their own engineers to fully explain. - **How does AI opacity differ from search engine or social media opacity?** AI adds sharper edges to familiar opacity problems. AI models can generate plausible falsehoods with perfect confidence, default to perspectives that may carry hidden bias, and cannot identify their own sources. Unlike search results, there is no list of links to verify against. - **What skills from social media help with evaluating AI?** The same critical instincts people developed questioning search rankings and viral content transfer to AI evaluation. Asking why certain results appeared, checking sources, and wondering who benefits from a particular output are the same mental muscles needed to assess AI-generated answers. - **Why does the article say we already have a playbook for AI opacity?** People have spent two decades navigating opaque systems, from Google search to social media feeds. The core questions remain the same: Why did I see this? Who benefits from this output? Can I trust it? The article argues we already have these antibodies and need to remember to apply them to AI. A friend called me last week, unsettled. "I asked ChatGPT a question and got a confident answer. But I have no idea *why* it said what it said. How am I supposed to trust that?" I laughed. Not at her, but at the familiar shape of the question. ![A timeline showing the evolution from search to social to AI](../../assets/images/focus/inline/algorithm-opacity-to-ai-opacity/opacity-timeline-v2.jpg) *The black box got bigger, but it was never transparent* Twenty years ago, I had the same feeling about Google. Type a query, get results. Why *those* results? Why in *that* order? Nobody outside Google really knew.[^1] We trusted the black box because the outputs seemed good. Good enough, anyway. Then came Facebook's News Feed. What determines what you see first thing in the morning? Engagement metrics, social signals, advertiser interests, and a cocktail of factors the company itself couldn't fully explain. The opacity deepened, but so did our dependence. By the time we thought to question it, the feed had become our window to the world. Now we have AI models with billions of parameters. Why did it say *that*? The honest answer, even from the engineers who built it: we're not entirely sure. ## The Muscle We Already Have Here's what I told my friend: she's been training for this moment her whole digital life. She learned to question why certain search results appeared at the top. She learned to doubt viral content, to check sources, to wonder who benefits when a particular story shows up in her feed. These instincts didn't vanish. They transferred. ![A person looking at their reflection in a dark screen](../../assets/images/focus/inline/algorithm-opacity-to-ai-opacity/screen-reflection-v2.jpg) *We've always been looking at ourselves through systems we don't fully understand* The person who questions why an AI said something is using the same mental muscle as the person who questions why a headline appeared in their timeline. We've developed antibodies, however imperfect. ## What's Actually New The old questions still apply: *Why did I see this? Who benefits from this output? Can I trust it?* But AI adds sharper edges. AI can generate plausible falsehoods with perfect confidence.[^2] When AI writes, whose perspective does it default to? And perhaps most important: what's the source, when the model itself can't tell you? We've navigated opacity before. The playbook isn't new. We just need to remember we have one. --- ## References [^1]: Brin, S. & Page, L. (1998). "The Anatomy of a Large-Scale Hypertextual Web Search Engine." [Stanford InfoLab](http://infolab.stanford.edu/~backrub/google.html) [^2]: Weidinger, L., et al. (2021). "Ethical and social risks of harm from Language Models." [DeepMind](https://arxiv.org/abs/2112.04359) --- ### The Deal We Made Before AI **URL:** https://odysseyalive.com/focus/the-deal-we-made-before-ai **Published:** December 4, 2025 **Category:** Groundwork **Tags:** privacy, technology-history, social-contract, data, convenience **Purpose:** This article traces the long history of trading personal data for convenience, from 1998 grocery loyalty cards to modern AI systems. It argues that the privacy-for-convenience bargain predates AI and that understanding these accumulated trades is necessary before negotiating new ones. **FAQ:** - **What is the privacy-for-convenience trade described in this article?** The article describes a pattern of incremental exchanges: giving location data for directions, purchase history for recommendations, social connections for networking, and reading habits for book suggestions. Each individual trade felt reasonable, but the aggregate amounted to a much larger surrender of personal data. - **What did Scott McNealy say about privacy in 2000?** Sun Microsystems CEO Scott McNealy said 'You have zero privacy anyway. Get over it.' He was mocked at the time, but two decades later the statement reads less like arrogance and more like prophecy, according to a 1999 report in Wired. - **How does AI change the data-for-convenience dynamic?** AI amplifies the same trade but at a faster pace. What took tech companies years of accumulated data, AI can now infer from a single conversation. The exchange offers more capability for more data, more personalization for more modeling, and more convenience for deeper inference about identity and behavior. - **Can the privacy deals we have made be renegotiated?** The article argues that these trades were not permanent in the past and are not permanent now. They can be renegotiated, but first people must see them clearly and recognize that terms were often set while they were busy enjoying the benefits of convenience. I was cleaning out a drawer last year when I found my first loyalty card. A grocery store rewards program from 1998, back when the barcode was the cutting edge of personal data collection. I remember signing up without a second thought. Free groceries for letting them track my purchases? Who wouldn't take that deal? ![A stack of loyalty cards from different eras](../../assets/images/focus/inline/the-deal-we-made-before-ai/loyalty-cards-v2.jpg) *Each card was a contract we signed without reading* That moment in the checkout line was the first of a thousand invisible handshakes. I gave my location to get directions. My purchases to get recommendations. My social graph to stay connected. My reading habits to find new books. Each individual trade felt reasonable. The aggregate trade was something else entirely. ## The Slow Seduction In 2000, Sun Microsystems CEO Scott McNealy said, "You have zero privacy anyway. Get over it."[^1] He was mocked at the time. Two decades later, his statement reads less like arrogance and more like prophecy. The thing about seduction is that it works because the services were genuinely useful. Google Maps really did get me where I needed to go. Amazon really did surface books I wanted to read. The cost was invisible precisely because the benefit was tangible. ![A scale balancing convenience and privacy, slightly tipped](../../assets/images/focus/inline/the-deal-we-made-before-ai/balance-scale-v2.jpg) *The balance was never static* By the time anyone thought to read the fine print, we'd already signed away the library. ## The New Deal on the Table AI amplifies the same dynamic, but the pace has changed. What took tech companies years of accumulated data, AI can now infer from a single conversation. More capability in exchange for more data. More personalization in exchange for more modeling. More convenience in exchange for more inference about who we are and what we'll do next. The dilemma isn't new. It's just faster. I still have that loyalty card in my drawer. It reminds me that we've been making these trades for longer than we like to admit. The deals weren't permanent then, and they aren't permanent now. They can be renegotiated. But first, we have to see them clearly. The question isn't whether we've traded privacy for convenience. We have. The question is whether we did it consciously, or whether we woke up one day and realized the terms had been set while we were busy enjoying the groceries. --- ## References [^1]: Sprenger, P. (1999). "Sun on Privacy: 'Get Over It.'" [Wired](https://www.wired.com/1999/01/sun-on-privacy-get-over-it/) --- ### The Night the Rules Changed **URL:** https://odysseyalive.com/focus/the-night-the-rules-changed **Published:** November 27, 2025 **Category:** Groundwork **Tags:** ai, chatgpt, disruption, technology-history, paradigm-shift **Purpose:** This article recounts the author's first encounter with ChatGPT on November 30, 2022, and examines how that moment revealed unconscious assumptions about the boundary between human and machine cognition. It explores what shifted -- scarcity, expertise, speed -- and what remained essential. **FAQ:** - **How fast did ChatGPT grow after launch?** ChatGPT reached one million users in five days after its November 30, 2022 launch. By comparison, Netflix took 3.5 years and Instagram took 2.5 months to reach the same milestone, according to Reuters and Statista. - **What assumptions did ChatGPT challenge?** The article describes an unconscious belief held for twenty years: that certain cognitive tasks like writing, analysis, and synthesis required human judgment. ChatGPT did not just challenge this assumption but revealed that the author had never consciously examined it. - **What actually changed when ChatGPT launched?** The underlying technology, GPT-3, had existed since 2020. What changed was accessibility. OpenAI wrapped it in a free chat interface with no API keys or waiting lists. This made a truth hiding in plain sight visible: the gap between human and machine capability was narrower than assumed. - **What still matters in an age of AI-generated content?** The article argues that human judgment about what is worth doing, contextual understanding, stakes, relationships, and trust remain essential. When anyone can generate plausible text, verification matters more than ever. November 30th, 2022. I was debugging code in a coffee shop when my phone buzzed: "Have you seen this thing from OpenAI?" I typed a question I'd been wrestling with for hours. The kind of architectural problem that usually requires a whiteboard, two colleagues, and a long walk. The response came back in seconds. It wasn't just plausible. It was *good*. ![A coffee shop at night with warm lighting and a laptop on a wooden table](../../assets/images/focus/inline/the-night-the-rules-changed/coffee-shop-night-v2.jpg) *The ordinary setting where extraordinary shifts often find us* I remember the specific feeling: not excitement, not fear, but vertigo. The sensation of discovering that the ground you've been standing on was never quite where you thought it was. ## The Assumption I Didn't Know I Had For twenty years, I'd carried an unconscious belief: that certain cognitive tasks *required* human judgment. Writing. Analysis. Synthesis. The messy work of wrestling meaning from complexity. That first conversation didn't just challenge this assumption. It made me realize I'd never consciously examined it. The technology itself wasn't new. GPT-3 had existed since 2020. What changed was accessibility. OpenAI wrapped it in a chat interface and made it free. No API keys. No waiting lists. And suddenly, a truth hiding in plain sight became visible: the gap between human and machine capability was narrower than we'd assumed. ChatGPT reached one million users in five days.[^1] Netflix took 3.5 years. Instagram took 2.5 months.[^2] But speed wasn't the disorienting part. The disorienting part was watching the floor rise beneath everyone's feet. ![An hourglass with sand flowing rapidly](../../assets/images/focus/inline/the-night-the-rules-changed/hourglass-acceleration-v2.jpg) *The future arrived faster than the past prepared us for* ## What the Vertigo Revealed The rules that shifted weren't the obvious ones. Scarcity changed: cognitive outputs that were expensive became cheap overnight. Expertise changed: the floor rose dramatically, even if the ceiling stayed put. Speed changed: the time between idea and prototype collapsed. But something else became clearer too. Human judgment about what's *worth* doing. The need for context, stakes, relationships. The importance of trust. When anyone can generate plausible text, verification matters more than ever. My grandfather was a project manager for a NASA contractor in the sixties. He watched rooms full of engineers with slide rules get replaced by computers the size of refrigerators, then watched those get replaced by machines that fit on a desk. He would have recognized this moment. "Tools change," he used to say. "Work changes. But the need to be useful doesn't change." The night the rules changed wasn't really one night. It was the night we started paying attention. --- ## References [^1]: Hu, K. (2023). "ChatGPT sets record for fastest-growing user base." [Reuters](https://www.reuters.com/technology/chatgpt-sets-record-fastest-growing-user-base-analyst-note-2023-02-01/) [^2]: Buchholz, K. (2023). "ChatGPT Sprints to One Million Users." [Statista](https://www.statista.com/chart/29174/time-to-one-million-users/) --- ### Finding Tamanawas **URL:** https://odysseyalive.com/focus/finding-tamanawas **Published:** October 1, 2023 **Category:** Field Notes **Tags:** anthropology, oregon, grand-ronde, native-american, cultural-documentation, pacific-northwest **Purpose:** This article explores the Chinook Wawa concept of tamanawas -- the fusion of heart and spirit found in the natural world -- through visits to the Chachalu Museum and the Grand Ronde community in Oregon. It examines how oral tradition, cultural practice, and physical engagement with ancestral ways can reawaken collective knowledge. **FAQ:** - **What does tamanawas mean?** In Chinook Wawa, tamanawas translates to spirit and is closely related to the word tumtum, meaning heart. To the outsider, Tamanwas seems to represent the fusion of heart and spirit that imbues every rock, tree, and stream with stories. For the Indiginous community, Tamanawas can take on a deeper, more spiritual connection between people and the natural world. - **What is the Chachalu Museum?** The Chachalu Museum is a cultural center at 8720 Grand Ronde Road in Grand Ronde, Oregon. It honors the Elders and celebrates the Tribe's Restoration. It is open Tuesday to Saturday, 10:00 a.m. to 4:00 p.m., and entry is free for all ages. - **How did Oregon's history affect Grand Ronde's cultural traditions?** Beginning in 1857, many tribal bands in Oregon were forcibly relocated to a small reservation in Grand Ronde. Laws and regulations on the reservation stifled Native American cultural practices, devastating a culture that relies on oral tradition to pass along its identity across generations. - **How does Carl Jung's collective unconscious relate to tamanawas?** The article draws a parallel between Jung's concept of a shared reservoir of experiences and the idea that traditional practices like cedar carving and fishing awaken deeper, ancestral knowledge. Engaging physically in cultural activities brings dormant collective truths to light. Have you ever driven on a coastal road so twisty that you feel like a squirrel on espresso? The thing is, those bends and curves force me to slow down. Way down. So much so, I can't help but notice every critter rustling through the ferns and thorns. Suddenly, this isn't just a winding path anymore; the road turns into a tour guide revealing a world teeming with life. The rocks, the trees, the water... they're all part of this vibrant tapestry. And the air? Thick with something intangible. Those who live here call it "tamanawas." ![The long windy road to Grand Ronde, Oregon](../../assets/images/focus/inline/finding-tamanawas/long-windy-road-v2.jpg) *The long windy road to Grand Ronde, Oregon* In Chinook Wawa, 'tamanawas' translates to spirit, but according to their dictionary, it can also be closely related to the word 'tumtum,' meaning heart. Far from mere sentiment, think of it as the driving force that urges us to delve into and appreciate the natural world. Imagine tamanawas as the fusion of heart and spirit, imbuing every rock, tree, and stream with stories that guide and inspire us throughout life. For the community of Grand Ronde, nature isn't merely a backdrop; it's a revered teacher. The wisdom of the land, from the industrious beaver to the guiding stars, has been a cornerstone for generations. It's as if nature is a venerable mentor, offering time-tested guidance. And the people here? They're not just students; they're stewards, safeguarding this wisdom for future generations. Living just a stone's throw away from Grand Ronde, the concept of 'tamanawas' has intrigued me ever since I read Evelyn Lampman's 1954 book, "The Witchdoctor's Son." If this word holds such significance for my neighbors, shouldn't it pique my curiosity too? After all, we share the same air, walk the same trails, and marvel at the same tamanawas. It's more than just a term; it's a gateway to understanding this place we share. And so, my curiosity led me to the doorstep of the Chachalu Museum, a sanctuary of stories and local wisdom. ![The Chachalu Museum, Grand Ronde, Oregon](../../assets/images/focus/inline/finding-tamanawas/chachalu-museum-v2.jpg) *The Chachalu Museum, Grand Ronde, Oregon* ## The Keepers of Stories When I arrived, I met the smile of Joseph at the front desk. We talked about Melville Jacobs, whose journals were being cited in the "Our Ancestor Shimkhin" exhibit. Melville documented tribal history from an outsider's perspective. You see, the State of Oregon had its own trail of tears saga starting in 1857. Many of the tribal bands in Oregon were forcibly relocated to an extremely small reservation in Grand Ronde. To make matters even worse, laws and regulations were passed on the reservation that stifled Native American cultural practices. This had a devastating effect on a culture that relies on oral tradition to pass along their cultural identity. If it weren't for people like Melville, important pieces of their history might be lost to us. This adds another layer of complexity, as Joseph stated, "It's hard to read books and get a sense of culture." Native American elders, who hold an extreme sense of reverence for the stories and traditions they share with the next generation, feel jaded by the gaping holes in their culture. It's like trying to piece together a jigsaw puzzle with part of it missing. Joseph's words got me thinking about the power of storytelling. In a world that's increasingly digital, where our thoughts are being eroded by 280-character tweets, the Grand Ronde community holds onto the oral tradition, a practice that's both ancient and incredibly relevant. ## Nothing is Lost Forever Carl Jung, the Swiss psychiatrist, introduced the idea of the "collective unconscious," a reservoir of shared experiences and knowledge that we all carry within us but aren't always aware of. Jung believed that this collective unconscious is not just a repository of ancient myths and archetypes but also a source of creativity and wisdom that can be tapped into. During one of my many visits to the Chachalu Museum, I watched Travis, the museum curator, chisel a face from a large piece of cedar. No machinery, just a chisel and his hands. The surface was impeccably smooth, as if the wood itself had guided him. Could it be that the act of engaging in these traditional practices awakens a deeper, collective knowledge? Is it in our blood, passed down through generations, waiting to be awakened by the act of doing? ![Coyote Makes Wapato Woman](../../assets/images/focus/inline/finding-tamanawas/coyote-makes-wapato-woman-v2.jpg) *Coyote Makes Wapato Woman* This brings us back to tamanawas. If Jung's theory holds water, then the essence of tamanawas is not just a cultural concept but a universal truth. It's the process of participating in the culture, of living it, that brings these dormant truths to light. And the Grand Ronde community is living proof. Recently, they won back some of their fishing and hunting rights. This victory is more than a headline; it's a resurgence of a way of life. Imagine the joy of fishing in the same rivers your ancestors did, of hunting in the same forests. It's like finding a long-lost family album and realizing you're part of something much bigger. In the end, it's the physical act of engaging with one's culture, whether it's carving a piece of cedar or casting a fishing net into the river, that reawakens our collective history. It's as if the very act of doing stitches together the fabric of time, connecting us with generations past and future. In this way, we come to realize that nothing is truly lost forever. Instead, it lies dormant, waiting for the right moment to be rediscovered and brought back to life. And in that rediscovery, we find not just our history, but also our future. ![Spirit poles are a common sight in the Pacific Northwest](../../assets/images/focus/inline/finding-tamanawas/spirit-pole-v2.jpg) *This isn't a totem pole. Spirit poles are a common sight in the Pacific Northwest. While their intricate designs may seem mysterious, there's no need for apprehension. These poles are storytellers in wood, marking territories and honoring ancestors.* ## Your Journey Awaits The Chachalu Museum is more than a building; it's a living, breathing entity that honors the Elders and celebrates the Tribe's Restoration. Located at 8720 Grand Ronde Road, it's open Tuesday to Saturday, 10:00 a.m. - 4:00 p.m., and entry is free for all ages. If you're looking for tamanawas, it's here. --- ## Projects ### Destination Cabo: AI Search Visibility **URL:** https://odysseyalive.com/projects/destination-cabo-geo **Client:** Destination Cabo **Category:** GEO + Content Strategy **Status:** shipped **Summary:** Transformed a luxury vacation rental site into an AI-discoverable resource. Within days, the site began appearing in Grok and Perplexity search results for Cabo travel queries. **Challenge:** The site had solid traditional SEO but was invisible to AI search engines. When travelers asked ChatGPT, Perplexity, or Grok about Cabo rentals, Destination Cabo wasn't being cited, despite 20 years of expertise and hundreds of verified reviews. **Solution:** Implemented comprehensive Generative Engine Optimization (GEO): restructured content with answer-first formatting, added FAQPage and LocalBusiness schema markup, created quotable statistics and direct answer capsules, and optimized meta descriptions for AI extraction. **Results:** - Now appearing in Grok and Perplexity search results - Schema markup providing 28% citation boost in AI responses - Content structured for direct extraction by LLMs - Complete site redesign with modern, conversion-focused UX **Technologies:** Schema.org JSON-LD, FAQPage Markup, Content Architecture, Meta Optimization When your client sends you a message that reads "You did it! We're showing up on Grok and Perplexity!" That's the moment you know the work landed. ## The Invisible Problem [Destination Cabo](https://destinationcabo.com) had been in the luxury vacation rental business for over 20 years. They had the reviews. They had the repeat customers. They had genuine expertise in Cabo travel that most competitors couldn't match. But when travelers started asking AI assistants about Cabo villa rentals, Destination Cabo was nowhere to be found. The site ranked fine in traditional Google searches, but the new AI-powered search engines (Perplexity, Grok, ChatGPT's browsing mode) weren't citing them at all. This is the new reality of search: traditional SEO gets you indexed, but **Generative Engine Optimization** (GEO) gets you *cited*. ## What AI Search Engines Actually Need AI search engines don't just crawl pages. They extract answers. They're looking for: - **Direct answers** positioned at the top of content sections - **Quotable statistics** with specific numbers they can cite - **Structured data** that explicitly labels Q&A pairs - **Clear authority signals** that establish expertise The challenge isn't getting AI to find your site. It's making your content *extractable*. ## The Implementation We approached this as an anthropological problem: how do AI systems "read" content, and how can we make Destination Cabo's expertise legible to them? ### Content Architecture Every major content section was restructured with an "answer first" approach. Instead of building to a conclusion, we led with it. AI systems extract from the top of sections, so the most important information needed to live there. ### Schema Markup We implemented FAQPage schema across key service pages, explicitly marking up the questions travelers actually ask. This alone provides an estimated 28% boost in AI citation rates according to recent GEO research. ### Quotable Elements We surfaced specific, citeable facts throughout the content: - "40-60% savings versus resort rates" - "20 years of local expertise" - "4.9-star rating across 127+ verified reviews" These become the snippets that AI systems pull into their responses. ## The Result Within days of implementation, the client reported seeing Destination Cabo appear in both Grok and Perplexity search results for Cabo-related travel queries. The GEO work was part of a complete site overhaul: new design, new content architecture, new booking experience. But the AI visibility gains came specifically from the structured data and content optimization, not the visual refresh. > "You did it! We're showing up on Grok and Perplexity!" That's what success sounds like in the age of AI search. --- *Interested in making your site visible to AI search engines? [Let's talk about GEO](/contact).* --- ### Ticket Tomato: AI-Assisted Codebase Navigation **URL:** https://odysseyalive.com/projects/tickettomato-codebase-ai **Client:** Ticket Tomato **Category:** AI + Complex Systems **Status:** shipped **Summary:** Navigated a large, established codebase using AI-generated reports and documentation. An SAQ D compliance update that would typically take two weeks was completed in 5 hours. **Challenge:** Onboarding to a large, undocumented codebase is one of the most time-consuming challenges in software development. This ticketing platform had years of accumulated code, multiple payment integrations, and a last-minute PCI SAQ D compliance requirement with a hard deadline. **Solution:** Used AI tools to generate comprehensive codebase reports, map dependencies, and create living documentation. This accelerated the onboarding process dramatically and enabled a complete payment system conversion with confidence, even under extreme time pressure. **Results:** - SAQ D compliance update completed in 5 hours (typically 2 weeks) - Complete payment system migration with AI-assisted code review - Codebase documentation generated from AI analysis - Dramatically reduced onboarding time for mature production system **Technologies:** Claude Code, Codebase Analysis, Payment Integration, PCI Compliance There's a particular kind of dread that comes with inheriting a large codebase. The previous developers are gone. The documentation is sparse or outdated. And somewhere in those thousands of files is the thing you need to change, but you just don't know where yet. ## The Onboarding Problem [Ticket Tomato](https://tickettomato.com) is a Pacific Northwest event ticketing platform with years of development history. Like most platforms that have evolved organically, the codebase had grown complex. Multiple payment integrations. Patterns that evolved organically alongside newer approaches. The kind of system where making a change in one place can have unexpected effects elsewhere. Traditional onboarding to a codebase like this takes weeks. You read code. You trace execution paths. You build mental models. You break things and learn from the breakage. It's necessary work, but it's slow work. ## AI as a Codebase Translator Instead of the traditional approach, we used AI tools to accelerate the discovery process: 1. **Codebase mapping**: Generated comprehensive reports on file structure, dependencies, and architectural patterns 2. **Documentation synthesis**: Created living documentation from code analysis, capturing what the system actually does versus what old docs claimed 3. **Pattern recognition**: Identified coding conventions, common patterns, and potential problem areas across the codebase 4. **Impact analysis**: Before making changes, generated reports on what other parts of the system might be affected This isn't about replacing the need to understand the code. It's about getting to understanding faster. The AI doesn't make decisions. It provides context that would otherwise take days to gather manually. ## The 5-Hour Compliance Sprint The real test came with an unexpected deadline: a PCI SAQ D compliance update that needed to happen immediately. Under normal circumstances, this kind of security-critical update in an unfamiliar codebase would be a two-week project. You'd need to: - Understand the current payment flow completely - Identify every place cardholder data is handled - Verify encryption, storage, and transmission practices - Make changes without breaking existing functionality - Test exhaustively We had 5 hours. The AI-generated codebase reports made this possible. We already had maps of the payment integration touchpoints. We knew which files handled sensitive data. The impact analysis told us exactly what our changes would affect. The update was completed, tested, and deployed within the deadline. Not because we cut corners, but because the AI had already done weeks worth of codebase exploration in the background. ## The Larger Pattern This project demonstrated something important about AI in software development: it's not about having AI write your code. It's about having AI *read* your code and translate that reading into actionable intelligence. Every large codebase is essentially undocumented, no matter how many README files it has. The real documentation is the code itself. AI tools that can read, synthesize, and report on that code unlock a kind of acceleration that wasn't possible before. --- *Navigating a mature codebase that needs fresh perspective? [Let's talk about AI-assisted code navigation](/contact).* --- ### Real Estate Market Intelligence System **URL:** https://odysseyalive.com/projects/real-estate-market-intelligence **Client:** Regional Brokerage **Category:** Automation + AI **Status:** in-development **Summary:** Automated market report generation that used to take 4 hours per agent per week. Now it takes 15 minutes of human review. **Challenge:** Agents were spending more time researching comparables and writing reports than actually talking to clients. The data existed across multiple MLS systems, but pulling it together was entirely manual. **Solution:** Built an n8n workflow that aggregates MLS data, runs AI analysis for market trends, and generates polished PDF reports. Agents just review and personalize before sending. **Results:** - 4+ hours saved per agent per week - Report generation down from 4 hours to 15 minutes - Agents closing 2 additional deals per quarter on average **Technologies:** n8n, OpenAI API, MLS Integration, PDF Generation The challenge with real estate market reports isn't the data. It's the time. Every agent knows they should be sending regular market updates to their sphere, but when each report takes 4 hours to research and write, it becomes the thing that gets pushed to "next week." ## The Problem This regional brokerage had 47 agents, each spending roughly 4 hours per week on market reports. That's 188 hours of agent time every week, time that could be spent actually talking to clients and closing deals. The data existed. Multiple MLS systems had everything needed. But pulling it together, analyzing trends, and writing something that didn't sound like a robot? That was the bottleneck. ## The Solution We built an n8n workflow that does the heavy lifting: 1. **Automated data aggregation** from multiple MLS systems 2. **AI-powered trend analysis** that identifies meaningful patterns 3. **PDF generation** with the brokerage's branding 4. **Draft delivery** to agents for quick personalization The key insight: agents don't want to be removed from the process. They want to add their voice, their local knowledge, their relationships. So the system produces a polished draft, and they make it theirs in 15 minutes instead of 4 hours. ## The Results Within three months: - Report generation dropped from 4 hours to 15 minutes - Agent time freed up by 4+ hours per week each - Agents reported closing an average of 2 additional deals per quarter The ROI was obvious within weeks. But the real win was watching agents actually look forward to sending market updates instead of dreading them. --- ## Frequently Asked Questions ### What is AI automation consulting? AI automation consulting helps businesses integrate artificial intelligence into their existing workflows. Unlike generic solutions, a good consultant studies how your team actually works, including the workarounds and informal processes, then builds automations that amplify what's working rather than forcing new systems. ### How is Odyssey Alive different from other AI consultants? Odyssey Alive combines 25 years of web development experience with a cultural anthropology background. This means understanding not just the technical side, but why teams communicate and work the way they do. The approach involves shadowing your team before writing any code, building automations around your existing tools, and providing training people actually remember. ### What types of businesses benefit from AI automation? Small to medium businesses with repetitive workflows, data entry tasks, or communication bottlenecks see the biggest gains. This includes real estate agencies needing market reports, service businesses managing client communications, and any team drowning in manual data transfer between systems. ### What tools does Odyssey Alive use for automation? The primary automation platform is n8n, an open-source workflow automation tool. This is combined with custom integrations, API connections to your existing software (CRMs, spreadsheets, email systems), and AI services like OpenAI and Claude for intelligent processing. The specific tools depend on your existing tech stack. ### How long does a typical project take? Most custom integrations take 4-8 weeks from kickoff to handoff. That includes the discovery phase where workflows are observed and understood, building and testing, and training your team. ### Do I need to know anything technical? No. You know your business. That's what matters. The consultant asks questions about how your team actually works, including the workarounds nobody talks about, and translates that into automations. ### What if my team hates new tools? Then automations are built around what they already use. The goal isn't to replace your team's Google Doc system with something "better." It's to make their Google Doc system do more with less manual work. --- ## Links - Website: https://odysseyalive.com - About: https://odysseyalive.com/about - Services: https://odysseyalive.com/services - Projects: https://odysseyalive.com/projects - Focus (Blog): https://odysseyalive.com/focus - Contact: https://odysseyalive.com/contact - LinkedIn: https://linkedin.com/in/francismeetze - GitHub: https://github.com/bridgesense