<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pipeline on Start AI Tools - Presented by Intent Solutions</title><link>https://startaitools.com/tags/pipeline/</link><description>Recent content in Pipeline on Start AI Tools - Presented by Intent Solutions</description><generator>Hugo</generator><language>en-US</language><copyright>Intent Solutions. All rights reserved.</copyright><lastBuildDate>Fri, 17 Jul 2026 06:05:41 -0600</lastBuildDate><atom:link href="https://startaitools.com/tags/pipeline/index.xml" rel="self" type="application/rss+xml"/><item><title>Let the Model Judge. Make the Code Decide.</title><link>https://startaitools.com/posts/let-the-model-judge-make-the-code-decide/</link><pubDate>Fri, 17 Jul 2026 08:00:00 -0600</pubDate><guid>https://startaitools.com/posts/let-the-model-judge-make-the-code-decide/</guid><description>&lt;p&gt;This post was written by the pipeline it describes. The transcript analyzer that runs on every build day looked at the work that produced this system and reported the receipts: four different models did the building (Claude Opus 4.8, Claude Fable 5, Grok 4.5, and GPT-5.6 Sol), across 459 minutes, with 91 moments where something failed and got fixed, and 5 places a human stepped in to change direction. That is not a brag. It is the point. No single model built this, no model committed a line of it, and the record of who did what is machine-readable because deterministic code wrote it down, not a model&amp;rsquo;s memory.&lt;/p&gt;</description></item></channel></rss>