<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Cairn blog</title><description>Shipping notes from Cairn: what shipped, how to use it, and why it works the way it does.</description><link>https://cairndev.sh/</link><language>en</language><item><title>Where a human approval belongs in an ML pipeline, and where it doesn&apos;t</title><link>https://cairndev.sh/blog/where-a-human-approval-belongs.html</link><guid isPermaLink="true">https://cairndev.sh/blog/where-a-human-approval-belongs.html</guid><description>Put a person in front of the leg that spends money or changes production, and show them the evidence. Let data decide everything a number can decide. How Cairn&apos;s gates are built around that rule, and what we deliberately keep away from approvers.</description><pubDate>Fri, 09 Oct 2026 00:00:00 GMT</pubDate><dc:creator>Vibhu Sharma</dc:creator><category>Engineering</category><category>governance</category><category>approvals</category><category>pipelines</category></item><item><title>Fine-tune with a cost gate</title><link>https://cairndev.sh/blog/fine-tune-with-a-cost-gate.html</link><guid isPermaLink="true">https://cairndev.sh/blog/fine-tune-with-a-cost-gate.html</guid><description>How Cairn&apos;s fine-tune pipeline prices a run before a GPU starts, checks the trained model against held-out data, and waits for a person before anything is promoted. The commands to run it are at the end.</description><pubDate>Thu, 08 Oct 2026 00:00:00 GMT</pubDate><dc:creator>Vibhu Sharma</dc:creator><category>Guide</category><category>training</category><category>governance</category><category>cli</category></item><item><title>From a DAG of scripts to a governed pipeline</title><link>https://cairndev.sh/blog/from-a-dag-to-a-governed-pipeline.html</link><guid isPermaLink="true">https://cairndev.sh/blog/from-a-dag-to-a-governed-pipeline.html</guid><description>If your ML work already runs as a DAG of scripts, Cairn doesn&apos;t replace the tools that run it. It adds what a DAG doesn&apos;t record or enforce: cost caps, data and human gates, one record per leg, and a trace you can replay.</description><pubDate>Wed, 07 Oct 2026 00:00:00 GMT</pubDate><dc:creator>Vibhu Sharma</dc:creator><category>Guide</category><category>pipelines</category><category>governance</category><category>migration</category></item></channel></rss>