<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Decision-Record on Start AI Tools - Presented by Intent Solutions</title><link>https://startaitools.com/tags/decision-record/</link><description>Recent content in Decision-Record on Start AI Tools - Presented by Intent Solutions</description><generator>Hugo</generator><language>en-US</language><copyright>Intent Solutions. All rights reserved.</copyright><lastBuildDate>Thu, 08 Oct 2026 10:00:00 -0600</lastBuildDate><atom:link href="https://startaitools.com/tags/decision-record/index.xml" rel="self" type="application/rss+xml"/><item><title>Park a Migration Without Losing the Work</title><link>https://startaitools.com/posts/park-the-cutover-keep-the-work/</link><pubDate>Thu, 08 Oct 2026 10:00:00 -0600</pubDate><guid>https://startaitools.com/posts/park-the-cutover-keep-the-work/</guid><description>&lt;p&gt;A migration that ships by reaching the default branch with a green badge still has a second decision hidden inside it: do we point production at it today, in a week, or ever. When the build and the deploy are welded together, that second decision leaks into rollback theater even when the right answer is to wait months. The pattern this post calls publish-and-park splits them on purpose, so parking an owner can be the cutover&amp;rsquo;s moment instead of its point of no return.&lt;/p&gt;</description></item></channel></rss>