Duane Forrester Decodes

You’re Using AI at the Execution Layer. The Value Is in the Judgment Layer.

The tools are deployed. The licenses are paid. And if you’re a senior SEO or GEO practitioner right now, you’re probably using AI every day - for drafts, for summaries, for first passes at content that used to take twice as long. That’s real productivity, and it’s not nothing. It’s also not the return the investment is capable of producing. And the gap between what you’re getting and what’s available isn’t a tool problem. It’s a mode problem. A peer-reviewed study published at the 2025 ASIS&T Annual Meeting [https://asistdl.onlinelibrary.wiley.com/doi/10.1002/pra2.1253] by Tim Gorichanaz at Drexel University gives that problem a name (h/t to Shari Thurow [https://www.linkedin.com/in/shari-thurow/] for pointing me at this paper!). Analyzing 205 real-world ChatGPT use cases, Gorichanaz identified six distinct modes in which people actually use AI: Writing, Deciding, Identifying, Ideating, Talking, and Critiquing. The data came from Reddit and skews Anglophone, which limits its generalizability, but the taxonomy it produced maps uncomfortably well onto how most practitioners are actually working. Two modes dominate. Four are being left on the table. The four being left are the ones that determine whether AI makes you more strategically valuable or just faster at execution-layer work. That distinction matters more right now than it has at any prior point in this industry’s history. The Two Modes Everyone Defaults To Writing was the largest category in Gorichanaz’s data at 47% of observed use cases - drafting, editing, summarizing, translating, generating. McKinsey’s 2025 State of AI survey [https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai] confirms this at the enterprise level: the most commonly reported AI use cases are content drafting and information capture, and 63% of organizations using generative AI apply it primarily to create text. Identifying - explaining something, answering a factual question, summarizing a document - was another 10% of the study’s data, and represents the other pillar most practitioners have built their AI workflow around. Research a topic, get a synthesis, move to the next task. Together these two modes account for the overwhelming majority of how AI is being used, by practitioners and enterprises alike. Both have real value, yet neither is where the leverage is. And if your AI practice begins and ends there, you’re using an increasingly sophisticated tool to do work that was already being automated - just faster and at higher volume. The other four modes (Deciding at 21% of Gorichanaz’s sample, Ideating at 9%, Talking at 8%, and Critiquing at 6%) are where the work becomes irreplaceable. They’re also where almost no practitioner has built a deliberate workflow, because nobody handed them one, and the pressure to show immediate output has consistently crowded out the space to develop one. The Decisions You’re Still Making Alone In the practitioner’s week, Deciding-mode questions are everywhere: which queries actually have AI visibility exposure worth prioritizing right now, whether a brand’s retrieval problem is a content architecture problem or a sourcing and signal problem, how to allocate effort across a portfolio when both SEO and GEO need attention and the budget doesn’t stretch to cover both fully, when to escalate a visibility concern to leadership versus when to fix it in the work before anyone asks. Most senior practitioners are currently solving these questions with experience and intuition. That’s not a failure as experience and intuition are genuinely valuable, and no AI replaces them. But AI used deliberately in Deciding mode adds something experience can’t provide on its own: a structured pressure-test of the assumptions underneath the decision, applied before the decision hardens. That requires more than a good question. Deciding mode requires giving the AI the relevant context (competitive landscape, current visibility posture, historical performance, strategic constraints) and then treating what comes back as a genuine input to the decision rather than a draft to be skimmed and set aside. It requires a workflow that doesn’t yet exist in most practitioners’ practice, not because anyone blocked it, but because no one built the time or structure for it either. The same McKinsey data makes clear what that gap costs at scale: 88% of organizations use AI, but only 6% qualify as high performers generating meaningful enterprise-wide impact, and high performers are 3.6 times more likely to have fundamentally reworked their workflows rather than simply deployed tools into existing ones. The pattern holds at the practitioner level. Faster output from an unreconstructed workflow is not the same thing as better decisions from a restructured one. The Gaps Nobody Briefed For SEO and GEO practitioners, Ideating mode has a specific application that most are not using and most should be: mapping the entity and authority gaps the brand hasn’t recognized yet. What angles of topical authority has the brand failed to establish that AI retrieval systems are currently filling from other sources? What community signals (forum discussions, aggregated reviews, third-party commentary) are shaping how LLMs represent the brand in response to category queries, and what would it take to shift them? What framings of the brand exist in model training data that the brand’s own content has never addressed or countered? These are genuinely Ideating-mode questions. They’re also questions most practitioners have some version of in the back of their mind without a structured method for surfacing the answers. AI used in Ideating mode, not “give me five content ideas” but a genuine iterative exploration with deliberate constraints and real willingness to follow the output somewhere the team hasn’t already been, is one of the most direct methods available for finding those gaps before a competitor or a client audit finds them first. The barrier isn’t capability. It’s the difference between a Writing prompt with a list output and an actual Ideating session. The first takes two minutes. The second takes twenty, requires a different posture toward the tool, and produces something that can’t be replicated by anyone who didn’t do it. That asymmetry is where practitioner value gets built in the current environment, and most practitioners are not claiming it. The Honest Read Your Team Won’t Give You This is the mode with the most direct application to daily practice and the most organizational resistance, because it requires using AI to find problems in work the practitioner or their team has already invested in. Used properly, Critiquing is how a senior practitioner catches what internal review missed. The weak entity claim in a content strategy that sounds authoritative but isn’t backed by the sourcing AI retrieval systems actually trust. The gap between what the brand says about itself across owned properties and what a well-prompted LLM surfaces when asked a category question the brand should own. The assumed premise in a GEO recommendation that made sense six months ago and is now contradicted by how retrieval patterns have shifted. That last application is not abstract. Running your own brand (or a client’s brand) through a structured AI Critiquing session before the next strategy cycle is exactly the kind of proactive work that separates practitioners operating at the judgment layer from practitioners operating at the production layer. It’s also the kind of work that changes the conversation with a client or a leadership team, because you’re surfacing problems before they become visible in the data rather than explaining them after the fact. The reason Critiquing is underused isn’t a governance problem. It’s a disposition problem. Organizations and practitioners have broadly trained themselves to use AI to produce output, not to interrogate it. Reversing that habit is a choice, and it’s one of the more consequential choices available to a senior practitioner right now. Rehearsal The Talking mode in Gorichanaz’s taxonomy covers AI as a conversation partner, and for practitioners, the most valuable version of that is rehearsal for the internal and client conversations where the stakes are real. The client call where you have to explain why organic traffic is down 30% while AI search visibility is also poor, and you need to hold two separate causal explanations simultaneously without letting them collapse into a single narrative that oversimplifies both. The internal briefing where you have to make the case for GEO investment alongside existing SEO budget to a leadership team that still conflates the two disciplines and wants a single number that explains the ROI of both. The agency or vendor review where you need to push back on a recommended approach without losing the relationship. These conversations are recurring and high-stakes, and most practitioners walk into them with only their own mental rehearsal as preparation. Talking mode (role-playing the pushback, asking the AI to argue the other side, running through the version of the conversation that goes wrong) is not a replacement for experience. It is a preparation method that costs twenty minutes and materially changes the quality of the practitioner who walks into the room. It doesn’t produce an artifact. It doesn’t show up in a utilization report. EY’s 2025 Work Reimagined Survey [https://www.ey.com/en_us/insights/workforce/work-reimagined-survey], which covered 15,000 employees and 1,500 employers across 29 countries, found that 88% of employees use AI at work, but only 5% use it in ways that fundamentally transform what they produce. The reason that gap is so wide is almost certainly that the advanced modes - Critiquing, Deciding, Talking - don’t produce something measurable in the moment. They produce a better practitioner over time, which is a return that compounds and doesn’t appear in a dashboard. What Mode You’re In Is What Layer You’re On The six-mode taxonomy maps almost exactly onto the split between execution-layer work and judgment-layer work. Writing and Identifying are execution-layer modes. They’re valuable, they’re visible, and they’re increasingly the modes that AI handles with less and less human involvement. Deciding, Ideating, Critiquing, and Talking are judgment-layer modes. They’re where the practitioner’s irreplaceability lives. A senior SEO or GEO practitioner who uses AI only in Writing and Identifying mode is, functionally, positioning themselves as an execution-layer worker at exactly the moment when AI is most aggressively compressing that layer. That’s not a prediction about job displacement. It’s an observation about professional differentiation. The practitioners building durable value in this environment are the ones using AI to make their judgment better, not just their output faster. Gorichanaz’s study reframes what information need actually means in the AI era, not just question-answering or uncertainty reduction, but what the authors call skillfully coping in the world, meaning the ongoing application of practical intelligence to situations requiring both understanding and action. For a senior practitioner, that framing is a useful diagnostic. The question isn’t what AI can do. It’s which parts of your work require the kind of practical intelligence that compounds with experience, and whether your current AI practice is making that intelligence sharper or just making everything around it move faster. McKinsey’s workplace research [https://www.mckinsey.com/capabilities/tech-and-ai/our-insights/superagency-in-the-workplace-empowering-people-to-unlock-ais-full-potential-at-work] finds that only 1% of leaders call their companies mature on AI deployment, meaning AI is fully integrated into workflows and driving substantial business outcomes. The practitioner-level version of that gap is just as wide, and just as fixable. If you mapped your actual AI usage against the six modes this week (not what you intend to do, what you actually did) how would the distribution look? How much was Writing and Identifying? How much was Deciding, Ideating, Critiquing, Talking? The practitioners who close that gap deliberately, who build even a minimal workflow around the judgment-layer modes, are not doing something exotic. They’re doing something most of their peers are not. In a discipline where the execution layer is getting compressed by the same tools everyone has access to, that gap is the one worth closing first. If this framing connects to work you’re navigating, I’d like to hear about what you’re seeing. And if you want to go deeper on the structural layer beneath all of this, The Machine Layer [https://www.amazon.com/Machine-Layer-Visible-Trusted-Search/dp/B0G2WZKM59/ref=sr_1_1] is where that conversation continues. And before you go, just a heads up that I have a special announcement coming on Tuesday this week, just 2 days from now! You’ll get an extra email and podcast this week. Thanks for your time, everyone, and I’ll be back soon. Thanks for reading! This post is public so feel free to share it. Get full access to Duane Forrester Decodes at duaneforresterdecodes.substack.com/subscribe [https://duaneforresterdecodes.substack.com/subscribe?utm_medium=podcast&utm_campaign=CTA_4]

LLM Guidance Doesn’t Port the Way SEO Guidance Did

For roughly two decades, the SEO discipline operated on a quiet assumption that turned out to be one of its most valuable features. Guidance from one search engine traveled. If Google said sitemaps mattered, Bing said sitemaps mattered. If Bing said structured data deserved real effort, Google said the same. Practitioners optimized for Google with reasonable confidence that the work would carry across the other engines, and most of the time it did. That portability was not luck. It was the product of a structurally large overlap layer that the major search engines had jointly built, brick by brick, over twenty years. That world doesn’t exist in LLM-land. The major providers train on different corpora, run different crawlers under different policies, route different queries through different retrieval systems, and apply different alignment processes that shape the final response in ways the upstream signals can’t predict. Guidance from any one provider, including Google’s guidance about its own Gemini products, is one data point. Practitioners carrying the SEO habit forward, the habit of treating one engine’s guidance as roughly the whole map, will optimize confidently for one platform and miss the others. Sidebar: As I was finalizing this piece, Google published fresh guidance on optimizing for their generative AI features [https://developers.google.com/search/docs/fundamentals/ai-optimization-guide]. Their framing is explicit: from Google Search's perspective, optimizing for AI search is still SEO. That framing is accurate for Google Search. It does not extend to ChatGPT, Claude, Perplexity, or any other LLM, and that is precisely the trap this article is about. The shared standards that made SEO guidance portable The era of portable guidance was built on actual collaboration, not coincidence. The Sitemaps protocol [https://www.sitemaps.org/] became the joint property of Google, Yahoo, and Microsoft in November 2006, when the three engines formally agreed to support a common protocol at version 0.90, building on Google’s earlier Sitemaps 0.84 from June 2005. Five years later, on June 2, 2011, the same three engines launched Schema.org [https://blogs.bing.com/search/June-2011/Introducing-Schema-org-Bing,-Google-and-Yahoo-Uni], with Yandex joining shortly after, to create a common vocabulary for structured data markup. That was the announcement that got made on stage at SMX Advanced. I was on the Bing team at the time, and what struck me then is what still matters now. The engines were competitors, but they had decided that a shared vocabulary served them all. Webmasters got one set of rules. The web got cleaner data. The engines got better signals. Everybody won. The pattern repeated with robots.txt [https://www.rfc-editor.org/rfc/rfc9309.html], the 1994 convention that became RFC 9309 at the IETF in 2022, formalizing what every serious crawler already honored. And it repeated again, more recently, with IndexNow [https://www.indexnow.org/], the protocol Microsoft Bing and Yandex launched in October 2021. IndexNow is now supported by Bing, Yandex, Naver, Seznam, and Yep. Google has tested the protocol since 2021 but has not adopted it. That overlap layer is exactly why Google’s guidance felt safe to follow even if you cared about Bing traffic. The signals the engines used were not identical, but the inputs they accepted, the protocols they honored, and the standards they advertised were. Optimization had a shared substrate. Where the LLM stacks actually diverge The LLM environment doesn’t have a shared substrate of comparable size. The differences are not cosmetic and they are not temporary. They are baked into how the systems are built. Start with training data. OpenAI has signed disclosed licensing deals with News Corp worth up to $250 million over five years [https://everything-pr.com/ai-licensing-tracker/], Axel Springer [https://openai.com/index/axel-springer-partnership/] at roughly $13 million per year, Reddit [https://www.cjr.org/analysis/reddit-winning-ai-licensing-deals-openai-google-gemini-answers-rsl.php] at an estimated $70 million per year, plus the Financial Times, Condé Nast, Hearst, Vox Media, The Atlantic, the Associated Press, Le Monde, and others. Google has its own Reddit deal estimated at $60 million per year granting real-time data API access. Anthropic has not publicly disclosed equivalent publisher licensing deals, and that undisclosed status is itself the practitioner-facing point. The corpora that fed these models, and that continue to refresh them, are not the same documents. Practitioners cannot know what any given provider has paid for and what it hasn’t. The crawler infrastructure diverges next. OpenAI runs three separate bots [https://platform.openai.com/docs/bots]: GPTBot for training, OAI-SearchBot for search indexing, and ChatGPT-User for user-initiated retrieval. Anthropic runs three of its own [https://support.anthropic.com/en/articles/8896518-does-anthropic-crawl-data-from-the-web-and-how-can-site-owners-block-the-crawler]: ClaudeBot for training, Claude-SearchBot for search, and Claude-User for user-initiated retrieval. Perplexity runs PerplexityBot and Perplexity-User. Google introduced Google-Extended in September 2023 as the user-agent that controls whether Google can use a site’s content to train Gemini, separate entirely from the Googlebot that handles traditional search indexing. There is no single AI user-agent. Every provider requires a separate rule, and the rules don’t translate cleanly across providers because the bots don’t do equivalent jobs in equivalent ways. The retrieval architectures diverge structurally. ChatGPT has historically used Bing’s index [https://yoast.com/chatgpt-search/] as its primary web search source, and that connection appears to still be primary, though OpenAI continues to build out additional infrastructure alongside it. Perplexity built its retrieval system on a Vespa-based pipeline that treats documents and sub-document chunks as first-class retrievable units. Google’s Gemini uses Google’s own index plus Knowledge Graph grounding. Claude uses Brave Search as a retrieval partner. Same query, four different retrieval systems, four different views of which sources exist and which sources are worth surfacing. Then comes the alignment layer, which is where SEO had no equivalent at all. After a model is trained on its corpus, providers run post-training to shape how the model actually behaves: tone, refusal patterns, format, safety posture, what counts as a good answer. OpenAI’s primary approach has been RLHF, or Reinforcement Learning from Human Feedback [https://arxiv.org/abs/2203.02155], where human raters score model outputs and the model learns to produce highly rated responses. Anthropic developed Constitutional AI, which trains models to critique and revise their own outputs against a written set of principles. These methodologies produce demonstrably different behavior in the final products. The same retrieved content, fed into two models aligned by two methodologies, can yield two materially different responses about the same brand. When one provider’s guidance demonstrably fails to port The clearest single example of guidance that doesn’t port is llms.txt [https://llmstxt.org/]. Jeremy Howard of Answer.AI proposed the file in September 2024 as a markdown manifest, placed at a site’s root, that would guide LLMs to the most important content. The proposal got picked up across the SEO community. Yoast built a generator. Agencies added llms.txt creation to their service catalogs. Conference speakers declared it essential. As of mid-2026, no major LLM provider has confirmed they consume the file [https://ahrefs.com/blog/what-is-llms-txt/]. Not OpenAI. Not Anthropic. Not Google. Server-log analyses across hundreds of thousands of domains show major AI crawlers don’t routinely request /llms.txt at all. Google’s John Mueller publicly compared it to the deprecated meta keywords tag [https://www.cshel.com/ai-seo/no-llms-txt-is-not-the-new-meta-keywords/]. Gary Illyes confirmed at Search Central Live in July 2025 that Google does not support llms.txt and is not planning to. I’ve written about this elsewhere [https://duaneforresterdecodes.substack.com/p/llmstxt-the-webs-next-great-idea], so I won’t repeat the technicalities here. What matters for this argument is the structural lesson. Schema.org succeeded because three engines built it together and then enforced it together. llms.txt was proposed by one researcher, picked up by tooling vendors, and ignored by the platforms it was supposed to serve. The shared-standards model that gave SEO its portable guidance is not available to LLM practitioners at the same scale, because the platforms are not building the standards together. They are building their own pipelines. The Gemini inversion The cleanest illustration of how far guidance portability has degraded sits inside one company. Google publishes its own SEO documentation [https://developers.google.com/search/docs] at Search Central, the canonical guidance the industry has followed for two decades. Those documents emphasize traditional ranking signals, E-E-A-T, content quality, technical accessibility, and structured data. That guidance is still useful for Google Search itself. Google also makes Gemini, the model that powers AI Overviews and Google’s separate AI Mode surface. And the citation behavior of those surfaces does not appear to track the guidance the same company publishes for its own search results. In late 2024, roughly three-quarters of pages cited in AI Overviews [https://ahrefs.com/blog/ai-overview-citations-top-10/] also ranked in Google’s top 12 for the same query. By early 2026, after Google upgraded AI Overviews to Gemini 3 in January, Ahrefs analyzed 4 million AI Overview URLs and found that only 38% of cited pages also appeared in the top 10 for the same query. A separate BrightEdge analysis [https://www.searchenginejournal.com/google-ai-overview-citations-from-top-ranking-pages-drop-sharply/568637/] put the overlap closer to 17%. SE Ranking’s post-upgrade work found that Gemini 3 replaced approximately 42% of the domains previously cited under earlier model versions and generates 32% more sources per response. The gap widens further when you look at Google’s AI Mode, which is a separate conversational surface that runs on the same Gemini family. SEMRush data [https://whitehat-seo.co.uk/blog/ai-engines-comparison-citations] shows AI Mode and AI Overviews reach semantically similar conclusions 86% of the time, but cite the same URLs only 13.7% of the time. Only 14% of AI Mode citations rank in Google’s traditional top 10. It appears, so far, that the canonical relationship has shifted. Google’s published SEO guidance is still the cleanest path to ranking in Google Search. But that ranking is no longer a reliable proxy for being cited by Google’s own AI surfaces. The same guidance, the same content, the same domain, can produce three meaningfully different outcomes across Google Search, AI Overviews, and AI Mode, even though all three live inside the same company. The old playbook of following the search engine’s guidance and trusting that the engine’s other surfaces would behave consistently does not appear to be delivering the same returns it used to. What still ports, and why it’s smaller than it looks A universal layer does survive. Crawler accessibility still matters across every provider. Primary-source factual content still wins more citations than aggregator restatement. Clean retrievable structure still helps every system understand what a page is about. Presence on the high-authority sources that all major LLMs disproportionately cite, Wikipedia, YouTube, Reddit, major news outlets, still functions as a force multiplier across platforms. Earning visibility on those sources gives content a chance to surface in any LLM that draws on them. But the universal layer is much smaller than it was in the SEO era. Qwairy’s analysis of 118,000 AI responses [https://whitehat-seo.co.uk/blog/ai-engines-comparison-citations] across ChatGPT, Perplexity, Google AI Mode, and Claude found that only 11% of cited domains appeared across multiple platforms. The other 89% were platform-specific. A brand that wins citations on Perplexity may be largely invisible on Claude. A brand that’s a regular reference on ChatGPT may not show up in AI Overviews at all. The same content can be the right answer for one system and the wrong answer for the system next to it. What this means for the work The practical implication is not abandoning all hope. It is that practitioners need to stop treating any single LLM provider’s guidance as the universal map and start treating it as one input among several. Read what every major provider publishes about their own systems. Test your visibility across platforms, not just on the platform you happen to use most. Treat divergence as the default and overlap as the exception, not the other way around. This is not how SEO worked, and the difference matters. The old reflex was to optimize for Google and trust the portability. The new reality is that following one LLM’s guidance, even Google’s guidance about Gemini, will leave you optimized for a slice of the landscape and potentially blind to the rest. The discipline is being rebuilt on platform-specific work that didn’t exist in the SEO era, and the practitioners who recognize that first are going to spend the next two years setting the standards everyone else follows. The overlap shrunk. You now have more work than ever to accomplish. If you have thoughts on where the divergence between providers is sharpest in your own work, drop a comment below or reach out directly. I’d genuinely like to hear what’s showing up in the data. For more on how the AI search environment is reshaping the practitioner discipline, The Machine Layer [https://www.amazon.com/Machine-Layer-Visible-Trusted-Search/dp/B0G2WZKM59/ref=sr_1_1] is on Amazon. Thanks for reading! This post is public so feel free to share it. Get full access to Duane Forrester Decodes at duaneforresterdecodes.substack.com/subscribe [https://duaneforresterdecodes.substack.com/subscribe?utm_medium=podcast&utm_campaign=CTA_4]

Stop Treating AI Visibility as One Problem. It’s Actually Three, on Three Different Layers.

When a brand stops appearing in ChatGPT, or when its share of voice in Perplexity drops by half over a quarter, the typical response from the marketing org is to write more content. Sometimes a lot more. The thinking goes that if AI systems aren’t surfacing the brand, the fix is to feed them more material to work with. That instinct is a misdiagnosis. It’s a retrieval-layer fix being applied to what is increasingly a different kind of problem entirely, and the cost shows up as wasted budget, missed quarters, and a creeping sense that the work isn’t connecting to the outcomes anymore. The mistake is treating AI visibility as a single problem when it isn’t. There are three structurally different layers between your brand and the answer a user receives, each with its own failure modes, its own fixes, and increasingly its own organizational owner. Diagnose the wrong layer and the fix doesn’t land. Where most of the conversation has been living The first layer is retrieval. This is where the AI search optimization conversation has spent most of the last two years. The mechanics are familiar in shape if not in detail. When a model needs to answer a question grounded in real-world content, it pulls relevant material from external sources and uses that material to construct the response. The technical name is retrieval-augmented generation, or RAG, and the layer it operates on is the gateway between your content and the model’s output. This is where crawlability, parseability, and chunk-friendliness do their work. If your content can’t be retrieved cleanly, nothing downstream matters. The visibility tracking platforms most marketing teams have evaluated this year measure outcomes that depend on this layer functioning, which is why they tend to reward the same disciplines that produced good results in classical search: structured content, schema markup, self-contained answers, clean technical implementation. But retrieval has a structural limit, and Microsoft Research has been unusually direct about it [https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/]. Plain RAG, in their words, struggles to connect the dots. It retrieves chunks of text that look relevant to the question, but it cannot reason about how those chunks relate to each other. When the answer requires synthesizing information across multiple sources, or when the question is broad enough that the right answer depends on understanding patterns across an entire dataset, retrieval alone breaks down. The model gets the chunks and has to guess at the relationships, and guessing is where hallucinations enter. The discipline question this layer asks is straightforward. Can the model retrieve our content at all, and is it retrieving the right content for the right query? Most marketing teams have some version of this work in flight already, even if the specific tactics have shifted from classical SEO. But retrieval is only the gateway. Even when a model retrieves your content correctly, what it does with it depends on whether you exist as a recognized thing in the layer above. Where entity recognition does the real work The second layer is the relationship layer, and the dominant structure on it is the knowledge graph. The major search infrastructures all maintain one. Google’s Knowledge Graph, Microsoft’s Satori, and the open knowledge graph built on Wikidata and schema.org collectively define how your brand is represented as an entity, what category you sit in, and which other entities you’re connected to. This is the layer that decides whether AI Overviews and large language model responses treat you as a recognized member of your category, or as one fuzzy candidate string among many. Brands that exist as clean, well-defined entities get cited consistently. Brands that exist as undifferentiated tokens scattered across the open web get pattern-matched against fifty other candidates and lose more often than they win. Knowledge graphs have been around long enough that the discipline is reasonably mature. Schema markup on owned properties, consistent naming and identifiers across the open web, structured presence on the high-trust nodes like Wikidata entries and review platforms, and the slow accumulation of brand mentions in contexts that the graph treats as authoritative. This is where the unlinked brand mentions conversation lives, because consistent contextual mentions strengthen the entity even without a hyperlink attached. The fix at this layer is structural rather than volume-based. Writing more content does almost nothing if the entity definition underneath it is fuzzy. The discipline question here is harder than the retrieval-layer question. Are we a clean, defensible entity in our category, or are we still being pattern-matched against fifty other candidate strings? A brand that can’t answer that question affirmatively is going to lose ground in AI search regardless of how much content it produces, because the second layer is where the model decides what your content is actually about. The knowledge graph tells the model what your brand is. But increasingly, your brand has to function inside a third layer that most marketing teams haven’t met yet, where the model isn’t just understanding you, it’s being asked to reason about you on behalf of someone making a decision. The layer enterprise companies are quietly building right now The third layer is the context graph, and this one needs a careful introduction because most of the marketing conversation hasn’t reached it yet. A context graph has the same structural shape as a knowledge graph, with entities, relationships, and typed connections, but it’s grounded differently. A knowledge graph models the world. It tells you what things are and how they relate in general. A context graph models a specific organization’s data, decisions, policies, and operational reality. The cleanest framing I’ve seen [https://www.tekst.com/blogs/context-graph-vs-knowledge-graph-the-enterprise-ai-distinction-that-actually-matters] calls a knowledge graph the library and a context graph the operating manual written by the people who actually run the place. The library tells you what exists. The operating manual tells you what’s relevant, what’s authorized, and what to do about it right now. The library is read-only semantic infrastructure. The operating manual is a living operational layer that grows every time a business process executes. What separates a context graph from anything that came before it is that governance lives inside the graph rather than alongside it. Policies, permissions, validity windows, and authorization rules are nodes the graph itself queries, not external documentation applied at the edges. When an agent retrieves something from a context graph, the result has already been filtered through what’s currently authorized, currently valid, and currently applicable. The graph is also continuously evolving, so what it knows about you this week is not necessarily what it knew last quarter. That’s where the word “governed” comes from when people in this space talk about governed retrieval. It isn’t a frame, but rather the architecture. That architecture used to be invisible to anyone outside the organization that built it, which is why marketers haven’t had to think about it. That changed at Google Cloud Next ‘26, when Google introduced the Knowledge Catalog [https://cloud.google.com/blog/topics/google-cloud-next/next26-day-1-recap] inside its new Agentic Data Cloud. Google’s own description of the product, written in their own first-party blog content, says the Knowledge Catalog constructs a unified, dynamic context graph of your entire business, enabling you to ground agents in all of your business data and semantics. That sentence is the moment the term left the data-engineering blogs and entered enterprise procurement vocabulary. The reason this matters for marketing is that context graphs are what’s going to power the next generation of agents inside your enterprise customers. Gartner projects [https://www.gartner.com/en/newsroom/press-releases/2025-08-26-gartner-predicts-40-percent-of-enterprise-apps-will-feature-task-specific-ai-agents-by-2026-up-from-less-than-5-percent-in-2025] that 40 percent of enterprise applications will be integrated with task-specific AI agents by the end of 2026, up from less than 5 percent in 2025. Procurement agents, competitive intelligence agents, content strategy agents, vendor evaluation agents. These agents won’t be reasoning about your brand from the open web. They’ll be reasoning about your brand from inside their company’s context graph, and what that graph says about you depends on what got ingested into it. That ingestion is where the work for marketing lives. The brand that arrives at the context graph fragmented arrives weak. If your category positioning is inconsistent across owned and earned media, the graph picks up the contradictions and represents you ambiguously. If your entity data is fuzzy on the second layer, it stays fuzzy when it gets pulled into the third. If your third-party signal is thin or contradictory, the graph has nothing solid to anchor to. The work is upstream of the graph, but the consequences land downstream of it, inside an agent’s reasoning process that you’ll never see directly. I think of this discipline as governed visibility. The practice of making sure your brand arrives at the context graph in a state that holds up under governed retrieval. Clean entity definition, consistent third-party representation, reliable structured data, and a category position that doesn’t fall apart when an agent traverses the relationships around it. Governed visibility isn’t a new tactic stack. It’s the result of doing the second-layer work well enough that the third layer has something solid to ingest. The discipline question at this layer is the one most marketing teams haven’t started asking yet. When an agent inside our customer’s company is reasoning about us, what does it find, and is the version of us it finds the version we’d want it to act on? Three layers, three different problems, three different fixes. But also three different responsibility zones, and that’s where most teams are quietly losing ground. The reason most teams will lose this even though they’re working hard Each layer maps to a different organizational responsibility, and most marketing teams only own one of the three cleanly. • The retrieval layer is shared with web, dev, and sometimes IT. Marketing influences what gets published, but the infrastructure that makes content retrievable sits in someone else’s domain. • The knowledge graph layer is genuinely marketing’s territory. Schema discipline, entity definition, third-party signal, brand consistency, the slow structural work that compounds over years. • The context graph layer is where IT owns the infrastructure inside the customer’s organization, but marketing has to influence what gets ingested. The work is upstream and the consequences land downstream, often invisibly. The teams that win in 2026 are the ones that figured out how to operate across all three responsibility zones rather than perfecting their work on just one. Most teams I see are still optimizing their owned content, which is the retrieval layer, while losing ground on entity definition, which is the knowledge graph layer, and remaining completely absent from the context graph conversation, which is the layer where some enterprise businesses are quietly standing up right now. The work isn’t writing more content. The work is figuring out which layer the problem actually lives on, and building the disciplines to operate on all three. Governed visibility is the third-layer discipline that marketing is going to have to develop whether or not the term sticks. The brands that build it now will look prepared in eighteen months. The brands that don’t will be wondering why their content investments stopped producing the visibility they used to. If any of this lands or contradicts what you’re seeing inside your own teams, I want to hear about it. Drop a comment about which layer your work has been concentrated on, where you’re seeing the gaps, or where the responsibility zones break down inside your organization. The patterns are still forming, and the conversations in the comments tend to be fresher than anything else. A lot of the measurement frameworks for this kind of work sit in The Machine Layer [https://www.amazon.com/Machine-Layer-Visible-Trusted-Search/dp/B0G2WZKM59/ref=sr_1_1], which expands the original twelve KPIs for the GenAI era into something teams can actually run against. Thanks for reading! This post is public so feel free to share it. Get full access to Duane Forrester Decodes at duaneforresterdecodes.substack.com/subscribe [https://duaneforresterdecodes.substack.com/subscribe?utm_medium=podcast&utm_campaign=CTA_4]

Search Engines Were Built to Send Traffic Out. LLMs Were Built to Answer You, keep you in.

Search engines were designed to do several things at once: rank a field of options, route the user to one of them, and keep the human inside the decision so the engine never owned the choice. That last part was not an accident. It was the liability architecture. LLMs were built without any of it. They were built to answer the question directly, which is a different job entirely, and the design choices that follow from it change what visibility looks like, what risk looks like, and what the word ROI can honestly mean when the thing sending you traffic was never built to send traffic in the first place. Two Systems, Two Jobs A search engine’s job description is long. It crawls the web, indexes it, ranks a pool of candidate results against a query, presents them as a ranked list, and then waits for the human to make a click decision. The SERP itself has been drifting toward retention for years now, with galleries, rich snippets, answer boxes, local maps, video carousels, and AI Overviews all layering in features that keep the user on the page longer and route fewer of them to third-party sites. But the underlying contract was always the same. The engine offers options. The user selects one. The user owns the choice. An LLM does not offer options. It produces an answer. The citation, when it appears, is not functioning as a routing instrument. It is closer to a grounding artifact produced by a retrieval pipeline, or in some framings a confidence hedge, or both at the same time. Whichever read you prefer, none of them describe a system designed to send traffic somewhere else. The system was designed to resolve the question in place. That distinction sits beneath every metric conversation in this space. When practitioners ask what the LLM referral rate is, what the attributed traffic number looks like, what the click-through from an AI answer is, they are asking questions that assume a routing mechanism that is not actually part of the architecture. Whatever traffic does come through is a byproduct, not a design goal, and confusing the two is the first mistake in almost every conversation about AI visibility ROI. The Liability Surface Moved The human in the click decision was the SERP’s shield. If the link the user selected led somewhere harmful, misleading, or defamatory, the engine could point to the list of options and the user’s own agency in choosing one. The engine had not published the claim. It had surfaced ten candidate sources, the user had chosen one, and whatever happened next was not the engine’s editorial output. That is not a small feature. That is the reason Section 230 protections were structured the way they were, and why algorithmic ranking has traditionally been treated as something other than direct speech. LLMs have no equivalent shield to stand behind. The system is producing the answer directly, in its own voice, without a field of options or a user-selected source. The liability surface that the SERP was designed to offload sits with the model producing the output, and the cases that have already moved through courts are starting to sketch the edges of that surface. Walters v. OpenAI [https://www.globallegalinsights.com/news/openai-wins-ai-hallucination-defamation-lawsuit/] was dismissed on summary judgment in May 2025, and the decision leaned heavily on OpenAI’s disclaimers and a sophisticated reader who reasonably knew the chatbot could hallucinate. That reading protects general-purpose consumer chatbots in a very specific kind of case. It does not protect every product that uses a language model. In a separate matter, Air Canada was held liable for its customer service chatbot’s false statements about its own bereavement fare policy [https://www.datatechandtools.com/p/when-your-chatbot-lies-the-liability], because a customer could reasonably rely on an airline’s branded support agent for accurate information about that airline’s policies. Reasonable reliance is the key legal term, and the more specialized and authoritative the chatbot appears, the harder the disclaimer defense becomes to run. The active litigation is still mapping the frontier. OpenAI is currently facing multiple lawsuits tied to allegations that ChatGPT drove users toward suicide or harmful delusions [https://chatgptdisaster.com/lawsuits.html], several involving minors. The New York Times copyright case against OpenAI was allowed to proceed [https://chatgptdisaster.com/lawsuits.html] by a federal judge in March 2025, and Anthropic settled with book authors in August 2025 for a reported sum well into the billions. European GDPR complaints continue to move through Noyb. Battle v. Microsoft [https://molawyersmedia.com/2025/11/12/ai-defamation-law-court-cases-openai-microsoft-google/] is still live. None of these outcomes are settled, and some will be dismissed on the same disclaimer grounds that resolved Walters. The point is not that LLM operators will lose every case. The point is that the liability surface now sits with the system producing the output, whether the individual plaintiff wins or loses, and every brand building against an LLM inherits some version of that surface when it uses the system’s output in its own customer-facing work. The Denominator Problem The most common argument against investing in AI visibility work sounds decisive until you look closely at what it is measuring. The argument runs roughly: ChatGPT and the others send a tiny sliver of referral traffic, somewhere in the low single digits of total inbound, so why reallocate budget toward a channel that barely moves the needle? Conductor’s research pegs the combined AI referral share at about 1% of publisher traffic [https://www.adexchanger.com/publishers/the-ai-search-reckoning-is-dismantling-open-web-traffic-and-publishers-may-never-recover/]. That number is real. At first read, it seems to close the ROI question cleanly. It closes nothing. The problem is the denominator. While the AI share of traffic holds roughly steady, the absolute volume of search-driven traffic has collapsed across most publisher categories. Similarweb data shows organic traffic to news publishers fell from about 2.3 billion monthly visits in mid-2024 to under 1.7 billion by May 2025 [https://www.stanventures.com/news/similarweb-zero-click-search-surge-google-ai-overviews-3562/], a loss of more than 600 million visits in under a year. Business Insider’s search traffic dropped 55% between April 2022 and April 2025, HuffPost lost roughly half of its search referrals, and The New York Times saw search’s share of its desktop and mobile traffic slide from 44% to 37% [https://www.adexchanger.com/publishers/the-ai-search-reckoning-is-dismantling-open-web-traffic-and-publishers-may-never-recover/]. Zero-click searches climbed from 56% to 69% between May 2024 and May 2025 [https://www.stanventures.com/news/similarweb-zero-click-search-surge-google-ai-overviews-3562/] as AI Overviews expanded across the SERP. A Reuters Institute survey of 280 media leaders in late 2025 found they expect another 43% decline on average over the next three years [https://pressgazette.co.uk/media-audience-and-business-data/google-traffic-down-2025-trends-report-2026/]. Read against that backdrop, a stable percentage share of a shrinking pie is not stable. It is a loss. The skeptics who point at the 1% number are measuring relative share of a traffic base that is contracting underneath them, and they are treating a falling absolute as if it were a steady state. The real question is not whether LLMs are sending meaningful traffic yet. The real question is whether the channel that used to send meaningful traffic is still doing what it used to do, and the answer is visibly no. The denominator is moving, and any ROI calculation anchored to the old denominator is a calculation of the previous environment, not the current one. What The Billions Say If the design-intent and liability and denominator arguments still leave room for doubt, the last place to look is revealed preference. What are the companies with the most complete internal data on user behavior actually doing with their capital? The answer is unambiguous. The five largest US cloud and AI infrastructure providers have committed between 660 and 690 billion dollars in 2026 capital expenditure, nearly doubling 2025 levels [https://futurumgroup.com/insights/ai-capex-2026-the-690b-infrastructure-sprint/]. Alphabet alone is guiding to between 175 and 185 billion for 2026, more than doubling its 2025 spend of 91 billion [https://techcrunch.com/2026/02/05/amazon-and-google-are-winning-the-ai-capex-race-but-whats-the-prize/]. Microsoft, Amazon, Meta, and Oracle are all running similarly aggressive curves. The number that matters most, and that defuses the usual counter-argument, comes from Bank of America credit strategists who estimate AI capex will reach 94% of operating cash flows in 2025 and 2026, up from 76% in 2024 [https://techblog.comsoc.org/2025/11/01/ai-spending-boom-accelerates-big-tech-to-invest-invest-an-aggregate-of-400-billion-in-2025-more-in-2026/]. That is not the shape of a defensive hedge. A hedge is a fraction of the cash flow, deployed to avoid being caught flat-footed if a competitor’s bet pays off. Companies do not put 94% of operating cash flow into a category for two consecutive years unless the leadership genuinely believes the category is the business. And those leadership teams have access to data that the rest of us do not. They can see inside their own products, their own user behavior shifts, their own cohort analyses, their own enterprise pipeline conversations. They are legally bound to deploy shareholder capital in a way that reflects what they actually see, and what they are deploying it toward is the architecture that produces direct answers rather than ranked lists of options. To believe search-as-we-knew-it remains the gold standard, you have to believe that dozens of CEOs, boards, and senior leadership teams with decades of internal-only data are reading their own numbers wrong, while an external industry with none of that data is reading the market correctly. That does not pencil. The human-behavior side of the equation makes the same point in a different register. Every labor-saving technology that has ever been introduced has reshaped the status quo faster than its skeptics predicted, because cognitive efficiency is not a preference. It is a survival behavior, wired in through long periods when calories were scarce and shortcuts mattered. When a new tool appears that makes some task meaningfully easier, adoption is not a matter of whether. It is a matter of how fast and along what curve. ChatGPT is now at roughly 900 million weekly active users, up from 200 million eighteen months earlier [https://9to5mac.com/2026/02/27/chatgpt-approaching-1-billion-weekly-active-users/], and the full category is past a billion active users across platforms [https://datareportal.com/reports/digital-2026-one-billion-people-using-ai]. The behavior has already shifted. The money has already shifted. The only thing that has not fully shifted is the measurement frame most practitioners are still using to evaluate the channel. Which brings the question back to the one that is actually worth asking. What do you do if there is no ROI by the old definition, and you still cannot ignore the channel? The honest answer is that brands will need to invest in visibility work whose return is not expressed in clicks or referral traffic, because clicks and referral traffic are artifacts of the previous design. Being the cited source, the grounded source, the trusted source inside the answer is a different kind of visibility, and it will need a different kind of measurement. The teams that figure that out first will not be doing it because they found an ROI case that convinced their CFO. They will be doing it because they looked at the capex curves, the behavioral curves, and the liability curves, and concluded that the channel is the future regardless of whether the spreadsheet knows how to score it yet. • • • If this lands somewhere real in your work, or if it reads wrong from where you are sitting, I would like to hear about it. Leave a comment with what you are seeing in your own numbers, or reach out directly. The shift happening right now is too large for any one practitioner’s vantage point, and the best signal I get comes from the conversations that start after the article ends. If you find yourself drawn to the kind of thinking these articles explore, my book The Machine Layer [https://www.amazon.com/Machine-Layer-Visible-Trusted-Search/dp/B0G2WZKM59/ref=sr_1_1] covers the broader landscape of how AI systems are reshaping visibility, trust, and discovery for brands and practitioners navigating this shift. You can find it on Amazon. Thanks for reading! This post is public so feel free to share it. Get full access to Duane Forrester Decodes at duaneforresterdecodes.substack.com/subscribe [https://duaneforresterdecodes.substack.com/subscribe?utm_medium=podcast&utm_campaign=CTA_4]

AI Gives You the Vocabulary. It Doesn’t Give You the Expertise.

Hiring managers are watching something uncomfortable happen in interview rooms right now. Candidates arrive with the right credentials, the right vocabulary, the right tool stack on their résumés, and then someone asks them to reason through a problem out loud, and the room goes quiet in the wrong way. Not in the thoughtful kind of way but the empty kind that tells you the person across the table has never actually had to think through a hard problem on their own. And research is converging on the same conclusion. Microsoft [https://www.microsoft.com/en-us/research/wp-content/uploads/2025/01/lee_2025_ai_critical_thinking_survey.pdf], the Swiss Business School [https://papers.ssrn.com/sol3/papers.cfm?abstract_id=5082524], and TestGorilla [https://www.testgorilla.com/skills-based-hiring/state-of-skills-based-hiring-2025/] have all documented the same pattern independently: heavy AI reliance correlates directly with declining critical thinking, and the effect is strongest in younger, less experienced practitioners. This isn’t a technology story so much as a cognition story, and the SEO industry is living a version of it in slow motion. What none of those studies name is the specific mechanism: the three-layer architecture of expertise where AI commands the retrieval layer completely, and the judgment layers underneath it are more exposed than they've ever been. That architecture is what this piece is about. The debate is framed on the wrong axis Every conversation about AI and critical thinking eventually lands in the same place: humans versus machines, organic thinking versus generated output, authentic expertise versus artificial fluency. It’s a compelling frame and also the wrong one. The real fracture line isn’t human versus AI. It’s retrieval versus judgment, and those are not the same cognitive act, even though AI has made them feel interchangeable in ways that should concern anyone serious about their craft. Retrieval is access. It’s the ability to surface relevant information, synthesize patterns across a body of knowledge, and produce fluent output that maps to the shape of expertise. Large language models are extraordinary at this, genuinely and structurally superior to any individual human at the retrieval layer, and getting better at speed. Fighting that reality is not a strategy. Judgment, however, is different. Judgment is knowing which question is actually the right question given this specific context, the ability to recognize when something that looks correct is wrong for this situation in ways that aren’t in any training data, the accumulated weight of having been wrong in consequential situations, learning why, and recalibrating. You cannot retrieve your way to judgment. You build it through deliberate practice under real conditions, over time, with skin in the game that a model structurally cannot have. The problem isn’t that AI handles retrieval well. The problem is that retrieval output now sounds so much like judgment output that the gap between them has become nearly invisible, especially to people who haven’t yet built enough judgment to know the difference. The Judgment Stack Think about expertise as a stack, not a spectrum. Layer 1 is retrieval - synthesis, pattern vocabulary, volume processing, surface recognition. This is AI territory, and handing work in this area over to an AI is not weakness but correct resource allocation. The practitioner who uses an LLM to compress a competitive analysis that would have taken three hours into forty minutes isn’t cutting corners, they’re buying back time to do the work that actually compounds. Layer 2 is the interface layer - hypothesis formation, question quality, contextual filtering, knowing which output to trust and which to interrogate. This is where the leverage actually lives, and it’s fundamentally human-plus-AI territory. Your prompt quality is a direct proxy for your judgment quality. Two practitioners can feed the same LLM the same general problem and get outputs that are miles apart in usefulness, because one of them knows what a good answer looks like before they ask the question, and that foreknowledge doesn’t come from the model but from Layer 3 working backward. Layer 3 is consequence and context - the ability to recognize when a pattern that has always worked is about to break, to assess novel situations that don’t map cleanly to anything in the training data, to hold strategic framing steady under pressure when the data is ambiguous. This is human territory, not because AI couldn’t theoretically develop something like it, but because it requires something a deployed model structurally cannot have: skin in the game, real consequence, the accumulated scar tissue of being wrong when it mattered and having to carry that forward. The critical thinking crisis everyone is diagnosing right now is not, at its root, an AI problem but a Layer 2 collapse. People skip directly from Layer 1 retrieval to Layer 3 claims, bypassing the judgment infrastructure entirely. Layer 1 output is fluent, confident, and often correct enough to pass casual scrutiny, which keeps the gap invisible right up until someone asks a follow-up the model didn’t anticipate, and the person has no independent footing to stand on. What SEO is actually revealing SEO is a useful diagnostic here because the industry has always been an early signal for how the broader marketing world processes technological disruption. We were the first to chase algorithmic shortcuts at scale. We were the first to industrialize content in ways that traded quality for volume. And right now we are watching two distinct practitioner populations diverge in real time, with the gap between them widening faster than most people have noticed. The first population is using LLMs as answer machines: feed the problem in, take the output out, ship it. Ask the model what’s wrong with a site’s rankings. Ask it to write the content strategy. Ask it to explain why traffic dropped. This isn’t entirely without value, since Layer 1 retrieval has genuine utility even here, but the practitioners operating purely at this layer are making a trade they may not fully understand yet. They are outsourcing the only part of the job that compounds in value over time. Every hard problem they hand off to a model without first attempting to reason through it themselves is a training repetition they didn’t take, a weight they didn’t lift, and those repetitions are how Layer 3 gets built. You want the muscle? You have to do the work. The second population is using LLMs as reasoning partners. They come to the model with a hypothesis already formed, a question already sharpened by their own thinking, and they use the output to pressure-test their reasoning, surface considerations they may have missed, and accelerate the parts of the work that don’t require their hard-won judgment, which frees them to apply that judgment more deliberately where it matters. These practitioners are getting faster and better simultaneously, because the model is amplifying something that already exists. The difference between these two groups has nothing to do with tool access, since they are using the same tools, and everything to do with what each practitioner brings to the model before they open it. The leveling lie The argument for AI as a leveling tool is not wrong, it’s just incomplete, and that incompleteness is where the damage happens. A junior practitioner today has access to a compression of the field’s knowledge that would have been unimaginable five years ago. Ask an LLM about crawl budget allocation, entity relationships, structured data implementation, or the mechanics of how retrieval-augmented systems weight freshness signals, and you will get a coherent, usually accurate answer in seconds. That is a genuine democratization of Layer 1, and dismissing it as illusory is its own form of gatekeeping. But Layer 1 access is not expertise. It is the vocabulary of expertise, and there is a specific kind of danger in having the vocabulary before you have the understanding, because fluency masks the gap. You can discuss the concepts. You can deploy the terminology correctly. You can produce output that looks like the work of someone with deep experience, and you can do all of that while having no independent capacity to evaluate whether what you just produced is actually right for the situation in front of you. This is not a character flaw but a metacognitive failure, the condition of not knowing what you don’t yet know. The junior practitioner using an LLM to accelerate their access to field knowledge isn’t being lazy. In many cases they are working hard and genuinely trying to develop. The problem is that Layer 1 fluency generates a confidence signal that isn’t calibrated to actual capability. The model doesn’t tell you when you’ve hit the edge of what it knows. It doesn’t flag the situations where the standard answer breaks down. It doesn’t know what it doesn’t know either, and neither do you yet, and that combination is where well-intentioned work quietly goes wrong. The leveling effect is real, but the ceiling on it is lower than most people assume. What gets leveled is access to the knowledge layer. What doesn’t get leveled (what cannot be compressed or transferred through any tool) is the judgment architecture that determines what you do with that knowledge when the situation doesn’t follow the pattern. The practitioners who understand this distinction will use AI to accelerate their development. The ones who don’t will use it to feel further along than they are, right up until the moment a genuinely novel problem requires something they haven’t built yet. Where the abdication actually happens Let’s be precise about this, because the accusation of abdication usually gets thrown around in ways that are more emotional than useful. Using AI at Layer 1 is not abdication. Letting a model handle competitive analysis synthesis, first-draft content frameworks, technical audit pattern recognition, or structured data generation is correct delegation, since these are retrievable tasks and doing them manually when a better tool exists isn’t intellectual virtue but inefficiency pretending to be rigor. Abdication happens at a specific and different point. It happens when you stop taking the problems that would have built your Layer 3 judgment and start routing them directly to a model instead: not because the model’s output isn’t useful, but because the attempt itself was the point. The struggle to formulate an answer to a hard problem, even an incomplete or wrong answer, is the mechanism by which judgment gets built. Hand that struggle off consistently and you are not saving time but spending something you may not realize you’re spending until it’s gone. This is the part of the conversation that doesn’t get said clearly enough: the low-consequence training repetitions are how you prepare for the high-consequence moments. A practitioner who has reasoned through hundreds of traffic anomalies, content decay patterns, and crawl architecture decisions (even inefficiently, even wrongly at first) has built something that cannot be replicated by having asked an LLM to reason through those same problems on their behalf, because the model’s reasoning is not your reasoning, just as watching someone else lift the weight does not build your muscle. The senior practitioners who feel their position eroding right now are often misdiagnosing the threat. The threat isn’t that AI makes their knowledge less valuable, since genuine Layer 3 judgment is actually more valuable in an AI-saturated environment, not less, precisely because it becomes rarer as more people mistake Layer 1 fluency for the whole stack. The real threat is that the market hasn’t developed clean signals yet for distinguishing Layer 3 capability from Layer 1 fluency dressed up convincingly. It’s a signal problem that is temporary and will resolve itself in the most public and consequential ways possible - in front of clients, in front of leadership, in front of the situations where someone needs to make a call the model can’t make. The answer for experienced practitioners is not to resist AI but to use it in ways that continue building Layer 3 rather than substituting for it. Use the model to go faster on Layer 1, and use the time that buys you to take on harder problems at Layer 2 and 3 than you could have reached before. The ceiling on your development just got higher, and whether you use that is a choice. The answer for junior practitioners is harder but more important: understand that the shortcut doesn’t shorten the path but changes the surface underfoot. You can move across the terrain faster with better tools, but the terrain still has to be crossed, and there is no prompt that builds the judgment architecture for you. Only doing the work, being wrong in situations that matter, and carrying that forward builds that. The prerequisite Critical thinking is not the alternative to AI use. Instead, it is the prerequisite for AI use that compounds. Without it, you are operating entirely at Layer 1, fluent and fast and increasingly indistinguishable from everyone else who has access to the same tools you do, and everyone has access to the same tools you do. The tools are not the differentiator and never were, serving instead as a floor, and that floor is rising under everyone’s feet simultaneously. What compounds is judgment. The accumulated capacity to ask better questions than the person next to you, to recognize the moment when the standard pattern breaks, to hold a strategic position steady when the data is ambiguous and the pressure is real. That capacity doesn’t live in the model but in the practitioner, built over time through deliberate practice under real conditions, and it is the only thing in The Judgment Stack that gets more valuable as the tools get better. The interview rooms where qualified candidates go quiet when asked to reason out loud are not showing us a technology problem. They are showing us what happens when a generation of practitioners optimizes for Layer 1 output without building the infrastructure underneath it, accumulating the vocabulary without the architecture and the fluency without the foundation. The practitioners who will matter in three years are building that foundation right now, using every tool available to go faster at Layer 1 and using the time that buys them to go deeper at Layer 3 than was previously possible. They are not choosing between AI and thinking but using AI to think harder than they could before, and that is not a leveling effect but a compounding one…and compounding, as anyone who has spent serious time in this industry understands, is an advantage worth building. If this maps to something you’re seeing in your team or organization (practitioners who look capable until the pressure is real, capability gaps you can’t quite locate) drop a comment below or reach out. I’d like to hear what you’re observing. For the broader framework of how AI is reshaping brand visibility, trust, and discovery, The Machine Layer [https://www.amazon.com/Machine-Layer-Visible-Trusted-Search/dp/B0G2WZKM59/ref=sr_1_1] expands this thinking across the full landscape. Available on Amazon. Thanks for reading! This post is public so feel free to share it. Get full access to Duane Forrester Decodes at duaneforresterdecodes.substack.com/subscribe [https://duaneforresterdecodes.substack.com/subscribe?utm_medium=podcast&utm_campaign=CTA_4]