<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>FDE Field Notes — Scott Felten</title>
    <link>https://scottfelten.com/blog/</link>
    <description>Practical analysis of Forward Deployed Engineering and enterprise AI delivery.</description>
    <language>en-us</language>
    <lastBuildDate>Mon, 31 Aug 2026 12:00:00 GMT</lastBuildDate>
    <atom:link href="https://scottfelten.com/blog/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>If the Agent Can Change the Test, It Didn&#39;t Pass</title>
      <link>https://scottfelten.com/blog/if-the-agent-can-change-the-test-it-did-not-pass/</link>
      <guid isPermaLink="true">https://scottfelten.com/blog/if-the-agent-can-change-the-test-it-did-not-pass/</guid>
      <pubDate>Mon, 31 Aug 2026 12:00:00 GMT</pubDate>
      <description>An agent evaluation is decision-ready only when the system under test cannot rewrite the baseline, success oracle, or retained evidence used to approve it.</description>
    </item>
    <item>
      <title>The Agent&#39;s Tool List Is Not Its Authority Model</title>
      <link>https://scottfelten.com/blog/the-agents-tool-list-is-not-its-authority-model/</link>
      <guid isPermaLink="true">https://scottfelten.com/blog/the-agents-tool-list-is-not-its-authority-model/</guid>
      <pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>
      <description>A connected-tool inventory shows where an agent can reach. Production requires an authority ledger that makes each consequential action attributable, conditional, time-bound, testable, and revocable.</description>
    </item>
    <item>
      <title>The Contract Is Not the Deployment</title>
      <link>https://scottfelten.com/blog/the-contract-is-not-the-deployment/</link>
      <guid isPermaLink="true">https://scottfelten.com/blog/the-contract-is-not-the-deployment/</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <description>Buying AI creates access. Deployment begins when a named workflow has an owner, evidence standard, operating boundary, and path to adoption.</description>
    </item>
    <item>
      <title>The FDE Is a Delivery System—Not a Job Title</title>
      <link>https://scottfelten.com/blog/fde-is-a-delivery-system-not-a-job-title/</link>
      <guid isPermaLink="true">https://scottfelten.com/blog/fde-is-a-delivery-system-not-a-job-title/</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <description>OpenAI, Anthropic, and Google disclose different ways to allocate field delivery. Compare the responsibilities and handoffs, not the labels.</description>
    </item>
    <item>
      <title>Build It, Buy It, or Partner for the First Deployment?</title>
      <link>https://scottfelten.com/blog/build-buy-or-partner-first-ai-deployment/</link>
      <guid isPermaLink="true">https://scottfelten.com/blog/build-buy-or-partner-first-ai-deployment/</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <description>Build, buy, and partner are not mutually exclusive bets. They are choices about who should own each layer of the first production workflow.</description>
    </item>
    <item>
      <title>OpenAI&#39;s FDE Loop Runs Back to the Product and the Model</title>
      <link>https://scottfelten.com/blog/openai-fde-loop-product-model/</link>
      <guid isPermaLink="true">https://scottfelten.com/blog/openai-fde-loop-product-model/</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <description>OpenAI’s public FDE role connects discovery and production adoption to eval-driven product and model feedback. The return path is where field work can compound.</description>
    </item>
    <item>
      <title>Anthropic Is Building a Portfolio System Around Scarce FDE Capacity</title>
      <link>https://scottfelten.com/blog/anthropic-fde-portfolio-scarce-capacity/</link>
      <guid isPermaLink="true">https://scottfelten.com/blog/anthropic-fde-portfolio-scarce-capacity/</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <description>Anthropic’s public FDE roles expose qualification, prioritization, partner routing, commercial coordination, and handoff as one delivery system.</description>
    </item>
    <item>
      <title>Google&#39;s FDE Model Scales Through Partners</title>
      <link>https://scottfelten.com/blog/google-fde-model-scales-through-partners/</link>
      <guid isPermaLink="true">https://scottfelten.com/blog/google-fde-model-scales-through-partners/</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <description>Google&#39;s public partner design shows how frontier delivery can distribute capacity without losing accountability—if context, evidence, and escalation have named owners.</description>
    </item>
    <item>
      <title>The Real Unit of FDE Capacity Is a Qualified Deployment</title>
      <link>https://scottfelten.com/blog/qualified-deployment-is-the-unit-of-fde-capacity/</link>
      <guid isPermaLink="true">https://scottfelten.com/blog/qualified-deployment-is-the-unit-of-fde-capacity/</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <description>A full FDE queue can hide weak allocation. Govern capacity as a portfolio of qualified deployments with a workflow, evidence plan, owner, route, and stop condition.</description>
    </item>
    <item>
      <title>When Services Accelerate Software—and When They Start Eating It</title>
      <link>https://scottfelten.com/blog/when-services-accelerate-software/</link>
      <guid isPermaLink="true">https://scottfelten.com/blog/when-services-accelerate-software/</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <description>Field delivery can increase adoption and improve the product—or build a shadow product. A four-ledger review shows whether services are compounding or consuming software economics.</description>
    </item>
    <item>
      <title>Measure Workflow Change—Not Token Burn</title>
      <link>https://scottfelten.com/blog/measure-workflow-change-not-token-burn/</link>
      <guid isPermaLink="true">https://scottfelten.com/blog/measure-workflow-change-not-token-burn/</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <description>Usage shows that an AI system was touched. A decision-ready evidence plan shows whether a bounded workflow changed enough to expand, hold, reshape, or stop.</description>
    </item>
    <item>
      <title>The Incumbent AI Delivery Function Is Hiding in Five Teams</title>
      <link>https://scottfelten.com/blog/incumbent-ai-delivery-function-five-teams/</link>
      <guid isPermaLink="true">https://scottfelten.com/blog/incumbent-ai-delivery-function-five-teams/</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <description>Traditional vendors distribute forward-deployed work across guidance, services, success, specialists, and partners. Buyers should map ownership and handoffs, not search for one title.</description>
    </item>
    <item>
      <title>Microsoft FastTrack Shows Where Product Guidance Stops</title>
      <link>https://scottfelten.com/blog/microsoft-fasttrack-product-guidance-boundary/</link>
      <guid isPermaLink="true">https://scottfelten.com/blog/microsoft-fasttrack-product-guidance-boundary/</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <description>Microsoft&#39;s explicit FastTrack scope can become a practical ownership map for the custom deployment work that remains.</description>
    </item>
    <item>
      <title>Salesforce Put ‘FDE Partner’ on the Ecosystem Map</title>
      <link>https://scottfelten.com/blog/salesforce-fde-partner-ecosystem-map/</link>
      <guid isPermaLink="true">https://scottfelten.com/blog/salesforce-fde-partner-ecosystem-map/</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <description>Salesforce&#39;s FDE Partner category is a real market signal, but buyers still need to inspect accountability, evidence, operation, and transfer.</description>
    </item>
    <item>
      <title>The Installed Base Is the Incumbent&#39;s Advantage—and Its Deployment Tax</title>
      <link>https://scottfelten.com/blog/installed-base-advantage-deployment-tax/</link>
      <guid isPermaLink="true">https://scottfelten.com/blog/installed-base-advantage-deployment-tax/</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <description>An installed base brings enterprise context and distribution, but also every unresolved data, authority, integration, and operating decision.</description>
    </item>
    <item>
      <title>Stop Hiring for a Unicorn: Design the FDE Team Topology</title>
      <link>https://scottfelten.com/blog/design-fde-team-topology/</link>
      <guid isPermaLink="true">https://scottfelten.com/blog/design-fde-team-topology/</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <description>A scalable FDE organization starts with explicit responsibilities and artifact handoffs, not an ever-rarer all-in-one hire.</description>
    </item>
    <item>
      <title>Custom Work That Must Become Product</title>
      <link>https://scottfelten.com/blog/custom-work-that-must-become-product/</link>
      <guid isPermaLink="true">https://scottfelten.com/blog/custom-work-that-must-become-product/</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <description>Field work compounds only when each custom asset becomes supported product, reusable delivery capability, a visible exception, or a documented stop.</description>
    </item>
    <item>
      <title>Agent Handoff Rules Are Product Requirements</title>
      <link>https://scottfelten.com/blog/agent-handoff-rules-product-requirements/</link>
      <guid isPermaLink="true">https://scottfelten.com/blog/agent-handoff-rules-product-requirements/</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <description>An enterprise agent is defined as much by what it must escalate as by what it can automate. Put authority, handoffs, and recovery into the specification before integration.</description>
    </item>
    <item>
      <title>Who Owns What the Product Learns in the Field?</title>
      <link>https://scottfelten.com/blog/who-owns-product-field-learning/</link>
      <guid isPermaLink="true">https://scottfelten.com/blog/who-owns-product-field-learning/</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <description>Customer feedback can mean data, patterns, evals, requirements, or code. A durable field-to-product loop gives each one an owner and a disposition.</description>
    </item>
    <item>
      <title>Bounded Deployment Is the Alternative to Unbounded AI Consulting</title>
      <link>https://scottfelten.com/blog/bounded-deployment-alternative-to-unbounded-ai-consulting/</link>
      <guid isPermaLink="true">https://scottfelten.com/blog/bounded-deployment-alternative-to-unbounded-ai-consulting/</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <description>The way out of pilot limbo is not a larger transformation promise. It is a consequential workflow with visible evidence, owners, dependencies, and a stop rule.</description>
    </item>
    <item>
      <title>Transfer by Design: How an Independent FDE Leaves Without Taking the Capability Along</title>
      <link>https://scottfelten.com/blog/transfer-by-design-independent-fde/</link>
      <guid isPermaLink="true">https://scottfelten.com/blog/transfer-by-design-independent-fde/</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <description>A runbook written at the end cannot repair ownership decisions deferred at the beginning. Transfer must shape architecture, access, evidence, and delivery from intake.</description>
    </item>
    <item>
      <title>The Independent FDE Practice Needs an Operating System</title>
      <link>https://scottfelten.com/blog/independent-fde-practice-operating-system/</link>
      <guid isPermaLink="true">https://scottfelten.com/blog/independent-fde-practice-operating-system/</guid>
      <pubDate>Thu, 27 Aug 2026 12:00:00 GMT</pubDate>
      <description>Senior judgment is necessary, but it does not make a repeatable practice. The practice needs explicit systems for qualification, service design, delivery control, evidence, and ecosystem transfer.</description>
    </item>
  </channel>
</rss>
