<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Manifesto</title>
    <link>https://manifesto.wtf/</link>
    <atom:link href="https://manifesto.wtf/rss.xml" rel="self" type="application/rss+xml" />
    <description>Reader-first AI news, guides, explainers, and workflow intelligence.</description>
    <language>en-us</language>
    <lastBuildDate>Wed, 24 Jun 2026 12:00:00 GMT</lastBuildDate>
    <item>
      <title>Gemini’s Long-Context Push Is Changing How Operator Teams Write Internal Playbooks</title>
      <link>https://manifesto.wtf/articles/gemini-context-operators</link>
      <guid>https://manifesto.wtf/articles/gemini-context-operators</guid>
      <pubDate>Wed, 24 Jun 2026 12:00:00 GMT</pubDate>
      <description>Long context only matters when it changes team behavior. Operator teams are starting to treat Gemini as a working memory layer for briefs, policies, and internal research.</description>
    </item>
    <item>
      <title>Claude Is Becoming the Default Writing Layer for Enterprise Teams That Care About Review</title>
      <link>https://manifesto.wtf/articles/claude-enterprise-playbook</link>
      <guid>https://manifesto.wtf/articles/claude-enterprise-playbook</guid>
      <pubDate>Tue, 23 Jun 2026 12:00:00 GMT</pubDate>
      <description>The strongest Claude adoption story is not better prose in isolation. It is how well the model fits review-heavy teams that need stable tone, reliable revisions, and long documents.</description>
    </item>
    <item>
      <title>ChatGPT’s Real Advantage Right Now Is the Speed of the Workbench, Not the Marketing</title>
      <link>https://manifesto.wtf/articles/chatgpt-workbench-shift</link>
      <guid>https://manifesto.wtf/articles/chatgpt-workbench-shift</guid>
      <pubDate>Mon, 22 Jun 2026 12:00:00 GMT</pubDate>
      <description>The teams staying in ChatGPT are optimizing around fast iteration, reusable workflows, and the convenience of a product people already use every day.</description>
    </item>
    <item>
      <title>Grok’s Realtime Story Is Most Useful in Monitoring and Fast-Twitch Ops, Not General Editorial Work</title>
      <link>https://manifesto.wtf/articles/grok-real-time-ops</link>
      <guid>https://manifesto.wtf/articles/grok-real-time-ops</guid>
      <pubDate>Sun, 21 Jun 2026 12:00:00 GMT</pubDate>
      <description>Realtime access is compelling, but the strongest use cases are narrow: alert monitoring, live event tracking, and rapid response desks.</description>
    </item>
    <item>
      <title>The Best Marketing Teams Are Pairing AI Content Velocity With Much Tougher Measurement</title>
      <link>https://manifesto.wtf/articles/marketers-measurement-stack</link>
      <guid>https://manifesto.wtf/articles/marketers-measurement-stack</guid>
      <pubDate>Sat, 20 Jun 2026 12:00:00 GMT</pubDate>
      <description>Content velocity without better measurement just creates more noise. The strongest teams are rebuilding scorecards, feedback loops, and review rituals around AI-assisted output.</description>
    </item>
    <item>
      <title>Broker Teams Are Building AI Deal Desks Before They Build AI Chatbots</title>
      <link>https://manifesto.wtf/articles/realtor-deal-desk</link>
      <guid>https://manifesto.wtf/articles/realtor-deal-desk</guid>
      <pubDate>Fri, 19 Jun 2026 12:00:00 GMT</pubDate>
      <description>The most practical real-estate AI use case is internal: qualification, listing prep, and follow-up orchestration before a consumer ever talks to a bot.</description>
    </item>
    <item>
      <title>Hospitality Teams Are Using AI to Tighten Service Systems, Not Replace Front-of-House Judgment</title>
      <link>https://manifesto.wtf/articles/food-bev-service-ops</link>
      <guid>https://manifesto.wtf/articles/food-bev-service-ops</guid>
      <pubDate>Thu, 18 Jun 2026 12:00:00 GMT</pubDate>
      <description>The real gains in food and beverage are coming from forecasting, prep timing, and service coordination rather than novelty experiences.</description>
    </item>
    <item>
      <title>Creative Teams Are Moving From Prompt Collections to Repeatable Direction Systems</title>
      <link>https://manifesto.wtf/articles/creative-director-ai-system</link>
      <guid>https://manifesto.wtf/articles/creative-director-ai-system</guid>
      <pubDate>Wed, 17 Jun 2026 12:00:00 GMT</pubDate>
      <description>Studios that treat AI prompting like a production system are outperforming teams still treating it like an improvisation exercise.</description>
    </item>
    <item>
      <title>The Newsletter Is Becoming the Most Useful Product Surface for Independent AI Publications</title>
      <link>https://manifesto.wtf/articles/newsletter-is-a-product</link>
      <guid>https://manifesto.wtf/articles/newsletter-is-a-product</guid>
      <pubDate>Mon, 15 Jun 2026 12:00:00 GMT</pubDate>
      <description>For reader-first publications, the newsletter is no longer just distribution. It is the most controlled, repeatable editorial product in the stack.</description>
    </item>
  </channel>
</rss>
