
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Posts</title>
      <link>https://tailwind-nextjs-starter-blog.vercel.app/blog</link>
      <description>A blog created with Next.js and Tailwind.css</description>
      <language>en-us</language>
      <managingEditor>address@yoursite.com (Tim)</managingEditor>
      <webMaster>address@yoursite.com (Tim)</webMaster>
      <lastBuildDate>Sun, 12 Jul 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://tailwind-nextjs-starter-blog.vercel.app/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://tailwind-nextjs-starter-blog.vercel.app/blog/token-spend-measurement</guid>
    <title>I Had No Idea What a Pipeline Run Cost. Now I Do.</title>
    <link>https://tailwind-nextjs-starter-blog.vercel.app/blog/token-spend-measurement</link>
    <description>Every cost-reduction experiment I wanted to run — prompt optimization, cheaper model routing, stripped-down prompt variants — was uncalibrated because nothing measured per-run token spend. The fix was a measurement layer, and the load-bearing decision turned out to be the schema, not the capture point.</description>
    <pubDate>Sun, 12 Jul 2026 00:00:00 GMT</pubDate>
    <author>address@yoursite.com (Tim)</author>
    <category>automation</category><category>ai</category><category>ductor</category>
  </item>

  <item>
    <guid>https://tailwind-nextjs-starter-blog.vercel.app/blog/multi-issue-build-orchestration</guid>
    <title>Why I Sequenced Multi-Issue Build Orchestration Instead of Parallelizing It Immediately</title>
    <link>https://tailwind-nextjs-starter-blog.vercel.app/blog/multi-issue-build-orchestration</link>
    <description>I wanted the Pipeline tab to chew through a chain of planned issues instead of making me click them one by one. The tempting answer was parallel sessions, but the March 23 state lessons made serial mode the right thing to ship first.</description>
    <pubDate>Sun, 17 May 2026 00:00:00 GMT</pubDate>
    <author>address@yoursite.com (Tim)</author>
    <category>automation</category><category>ai</category><category>ductor</category>
  </item>

  <item>
    <guid>https://tailwind-nextjs-starter-blog.vercel.app/blog/discord-pipeline-bot</guid>
    <title>The Discord Bot Was the Easy Part</title>
    <link>https://tailwind-nextjs-starter-blog.vercel.app/blog/discord-pipeline-bot</link>
    <description>I asked an AI deliberation whether to build a Discord bot to replace my 3-minute poll cycle. The deliberation crashed three different ways — and that failure was more useful than the answer would have been.</description>
    <pubDate>Sun, 10 May 2026 00:00:00 GMT</pubDate>
    <author>address@yoursite.com (Tim)</author>
    <category>automation</category><category>ai</category><category>ductor</category>
  </item>

  <item>
    <guid>https://tailwind-nextjs-starter-blog.vercel.app/blog/deliberation-architecture-overhaul</guid>
    <title>Overhauling Deliberation: From Broken Provider Dispatch to Auto-PR Transcripts</title>
    <link>https://tailwind-nextjs-starter-blog.vercel.app/blog/deliberation-architecture-overhaul</link>
    <description>A deliberation session silently failed because the health check was hitting the wrong endpoint. Fixing that one bug turned into a five-part architecture overhaul covering provider dispatch, transcript persistence, and orchestrator handoff.</description>
    <pubDate>Sun, 03 May 2026 00:00:00 GMT</pubDate>
    <author>address@yoursite.com (Tim)</author>
    <category>ai</category><category>automation</category><category>ductor</category><category>dev-log</category>
  </item>

  <item>
    <guid>https://tailwind-nextjs-starter-blog.vercel.app/blog/2026-03-24-building-a-traffic-cop-for-ai-agents</guid>
    <title>Building a Traffic Cop for AI Agents</title>
    <link>https://tailwind-nextjs-starter-blog.vercel.app/blog/2026-03-24-building-a-traffic-cop-for-ai-agents</link>
    <description>How I built a multi-provider dispatch router that sends different AI personas to different LLM providers and the $57 billing surprise that proved it was worth it.</description>
    <pubDate>Tue, 24 Mar 2026 00:00:00 GMT</pubDate>
    <author>address@yoursite.com (Tim)</author>
    <category>ai</category><category>dev-log</category><category>multi-provider</category><category>architecture</category>
  </item>

  <item>
    <guid>https://tailwind-nextjs-starter-blog.vercel.app/blog/2026-03-23-what-is-ultravision</guid>
    <title>What Is Ultravision? Multi-Provider AI Deliberation</title>
    <link>https://tailwind-nextjs-starter-blog.vercel.app/blog/2026-03-23-what-is-ultravision</link>
    <description>How I built a system where three AI providers debate feature decisions before any code is written, and why the disagreements produce better designs than any single model.</description>
    <pubDate>Mon, 23 Mar 2026 00:00:00 GMT</pubDate>
    <author>address@yoursite.com (Tim)</author>
    <category>ai</category><category>dev-log</category><category>ecoorchestra</category><category>ultravision</category>
  </item>

  <item>
    <guid>https://tailwind-nextjs-starter-blog.vercel.app/blog/2026-03-20-building-a-circuit-breaker-across-two-repos</guid>
    <title>Building a Circuit Breaker Across Two Repos</title>
    <link>https://tailwind-nextjs-starter-blog.vercel.app/blog/2026-03-20-building-a-circuit-breaker-across-two-repos</link>
    <description>How I directed a circuit breaker feature across llm-router and AutoAgent using an AI development pipeline, and what the automated review caught before it hit production.</description>
    <pubDate>Fri, 20 Mar 2026 00:00:00 GMT</pubDate>
    <author>address@yoursite.com (Tim)</author>
    <category>ai</category><category>dev-log</category><category>llm-router</category><category>circuit-breaker</category><category>failover</category>
  </item>

  <item>
    <guid>https://tailwind-nextjs-starter-blog.vercel.app/blog/guardrails-vs-velocity</guid>
    <title>Guardrails vs Velocity: Two Philosophies for AI-Assisted Development</title>
    <link>https://tailwind-nextjs-starter-blog.vercel.app/blog/guardrails-vs-velocity</link>
    <description>EcoOrchestra governs every step. Ralph ships every loop. Both work. The question is which failure mode you fear more.</description>
    <pubDate>Fri, 20 Mar 2026 00:00:00 GMT</pubDate>
    <author>address@yoursite.com (Tim)</author>
    <category>ai</category><category>patterns</category><category>architecture</category><category>dev-log</category>
  </item>

  <item>
    <guid>https://tailwind-nextjs-starter-blog.vercel.app/blog/2026-03-18-how-i-built-a-blog-that-writes-itself</guid>
    <title>How I Built a Blog That Writes Itself</title>
    <link>https://tailwind-nextjs-starter-blog.vercel.app/blog/2026-03-18-how-i-built-a-blog-that-writes-itself</link>
    <description>Ghostpen turns development artifacts into blog posts written in my voice -- because the best time to write about a problem is when you just solved it.</description>
    <pubDate>Wed, 18 Mar 2026 00:00:00 GMT</pubDate>
    <author>address@yoursite.com (Tim)</author>
    <category>ai</category><category>dev-log</category><category>ghostpen</category><category>tooling</category>
  </item>

  <item>
    <guid>https://tailwind-nextjs-starter-blog.vercel.app/blog/2026-03-17-what-is-autoagent</guid>
    <title>Teaching an AI to Play Games by Watching YouTube</title>
    <link>https://tailwind-nextjs-starter-blog.vercel.app/blog/2026-03-17-what-is-autoagent</link>
    <description>An AI agent that learns to play games by watching VODs -- extracting knowledge with vision APIs, compiling behavior scripts, and executing them with computer vision.</description>
    <pubDate>Tue, 17 Mar 2026 00:00:00 GMT</pubDate>
    <author>address@yoursite.com (Tim)</author>
    <category>ai</category><category>dev-log</category><category>autoagent</category><category>gaming</category>
  </item>

  <item>
    <guid>https://tailwind-nextjs-starter-blog.vercel.app/blog/2026-03-16-what-is-llm-router</guid>
    <title>One Library to Route Them All: Multi-Provider LLM Routing</title>
    <link>https://tailwind-nextjs-starter-blog.vercel.app/blog/2026-03-16-what-is-llm-router</link>
    <description>A multi-provider LLM routing library that handles rate limits, batching, and failover -- so consuming applications never touch provider-specific APIs.</description>
    <pubDate>Mon, 16 Mar 2026 00:00:00 GMT</pubDate>
    <author>address@yoursite.com (Tim)</author>
    <category>ai</category><category>dev-log</category><category>llm-router</category><category>tooling</category>
  </item>

  <item>
    <guid>https://tailwind-nextjs-starter-blog.vercel.app/blog/2026-03-15-what-is-ecoorchestra</guid>
    <title>How I Built an AI Team That Enforces Its Own Quality Gates</title>
    <link>https://tailwind-nextjs-starter-blog.vercel.app/blog/2026-03-15-what-is-ecoorchestra</link>
    <description>How I built an AI development pipeline that runs a team of personas -- planner, developer, reviewer, QA engineer -- and enforces quality gates across multiple repos.</description>
    <pubDate>Sun, 15 Mar 2026 00:00:00 GMT</pubDate>
    <author>address@yoursite.com (Tim)</author>
    <category>ai</category><category>dev-log</category><category>ecoorchestra</category><category>tooling</category>
  </item>

  <item>
    <guid>https://tailwind-nextjs-starter-blog.vercel.app/blog/no-supported-provider-for-is-configured-azure-paas</guid>
    <title>No supported provider for blob is configured in an Azure PaaS and Sitecore 10.2 to 10.4 upgrade</title>
    <link>https://tailwind-nextjs-starter-blog.vercel.app/blog/no-supported-provider-for-is-configured-azure-paas</link>
    <description>A walkthrough of importing blob storage containers as a part of upgrading Sitecore to a newer version.</description>
    <pubDate>Wed, 09 Oct 2024 00:00:00 GMT</pubDate>
    <author>address@yoursite.com (Tim)</author>
    <category>sitecore</category><category>azure</category><category>blob-storage</category><category>troubleshooting</category>
  </item>

  <item>
    <guid>https://tailwind-nextjs-starter-blog.vercel.app/blog/installing-sitecore-10-4</guid>
    <title>Installing Sitecore version 10.4</title>
    <link>https://tailwind-nextjs-starter-blog.vercel.app/blog/installing-sitecore-10-4</link>
    <description>A walkthrough of installing Sitecore version 10.4, and some issues you may run into along the way.</description>
    <pubDate>Sat, 31 Aug 2024 00:00:00 GMT</pubDate>
    <author>address@yoursite.com (Tim)</author>
    <category>sitecore</category><category>sitecore-xp</category><category>installation</category>
  </item>

  <item>
    <guid>https://tailwind-nextjs-starter-blog.vercel.app/blog/setting-up-a-local-sitecore-xm-cloud-environment</guid>
    <title>Setting Up a Local Sitecore XM Cloud Environment</title>
    <link>https://tailwind-nextjs-starter-blog.vercel.app/blog/setting-up-a-local-sitecore-xm-cloud-environment</link>
    <description>Setting up a Local Sitecore XM Cloud Environment on a Windows 11 Hyper-V VM.</description>
    <pubDate>Sat, 27 Jul 2024 00:00:00 GMT</pubDate>
    <author>address@yoursite.com (Tim)</author>
    <category>sitecore</category><category>xm-cloud</category><category>docker</category><category>installation</category>
  </item>

  <item>
    <guid>https://tailwind-nextjs-starter-blog.vercel.app/blog/searchstax-backups-failing-and-dr-data-is-not-up-to-date</guid>
    <title>SearchStax deployment backups are failing with a disaster recovery environment</title>
    <link>https://tailwind-nextjs-starter-blog.vercel.app/blog/searchstax-backups-failing-and-dr-data-is-not-up-to-date</link>
    <description>Troubleshooting issues with SearchStax deployment backups failing with a disaster recovery environment.</description>
    <pubDate>Wed, 05 Jun 2024 00:00:00 GMT</pubDate>
    <author>address@yoursite.com (Tim)</author>
    <category>sitecore</category><category>searchstax</category><category>troubleshooting</category>
  </item>

  <item>
    <guid>https://tailwind-nextjs-starter-blog.vercel.app/blog/no-supported-provider-for-is-configured</guid>
    <title>BlobProviderException: No supported provider for &#39;&#39; is configured, and the Blob template field</title>
    <link>https://tailwind-nextjs-starter-blog.vercel.app/blog/no-supported-provider-for-is-configured</link>
    <description>Troubleshooting the BlobProviderException: No supported provider for &#39;&#39; is configured error, and a brief investigation into the Blob template field.</description>
    <pubDate>Thu, 02 May 2024 00:00:00 GMT</pubDate>
    <author>address@yoursite.com (Tim)</author>
    <category>sitecore</category><category>sitecore-xp</category><category>troubleshooting</category><category>blob-storage</category>
  </item>

    </channel>
  </rss>
