<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>schristoph.online</title><link>https://schristoph.online/tags/modellifecycle/</link><description>Personal homepage and blog of Stefan Christoph</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>Stefan Christoph. All rights reserved.</copyright><lastBuildDate>Mon, 16 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://schristoph.online/tags/modellifecycle/index.xml" rel="self" type="application/rss+xml"/><item><title>Your AI Models Have an Expiry Date — A Practical Guide to Model Lifecycle Management</title><link>https://schristoph.online/blog/model-lifecycle-management/?utm=rss-feed</link><pubDate>Mon, 16 Mar 2026 00:00:00 +0000</pubDate><guid>https://schristoph.online/blog/model-lifecycle-management/</guid><description>&lt;h2 id="introduction--the-promise-i-made">Introduction — The Promise I Made&lt;/h2>
&lt;p>In my previous article [1], I explored the maintenance trap in IT — how software systems are more like plants than stones, requiring constant care. I ended with a cliffhanger: &lt;em>&amp;ldquo;What is open from the article is how to specifically test and evaluate models — something to be picked up in the next article.&amp;rdquo;&lt;/em>&lt;/p>
&lt;p>This is that article.&lt;/p>
&lt;p>Since publishing the first piece, something happened that made this topic very real for many of my customers. Anthropic announced the deprecation of Claude 3.5 Sonnet, a model that had become the backbone of countless production applications. Teams that had built their systems around a specific model version suddenly faced a hard deadline to migrate. Some were prepared. Most were not.&lt;/p></description></item></channel></rss>