Track

UM Understanding & modernisation

Legacy estates (Java, .NET, C/C++, COBOL alike), migration, code comprehension.

From the issues

#01 · Research Desk29 Sep 2026

When the Model Retires: your AI stack is already legacy

Most teams move off a retired AI model after it breaks, not before. A study of 22,555 commits across 17,703 GitHub repos estimates 82% of migrations landed after the shutdown date, and 94% of the apps had the model ID hard-coded. Put model IDs in config, with an owner and a retirement date.

Numbers on this track

Number	What it measures	Source	Checked	Track · issue
82%	Estimated share of LLM migrations made after the model's shutdown date (22,555 commits, 17,703 GitHub repos)	Kim, arXiv:2609.31288 25 Sep 2026	✓verified at source	UMUnderstanding & modernisation Issue #01
94%	LLM apps with the model ID hard-coded	Kim, arXiv:2609.31288 25 Sep 2026	✓verified at source	UMUnderstanding & modernisation Issue #01
89% vs 13%	Post-shutdown migrations under Anthropic's 60 to 114-day notices vs OpenAI's one-year notice	Kim, arXiv:2609.31288 25 Sep 2026	✓verified at source	UMUnderstanding & modernisation Issue #01
8%	LLM migrations that switched model provider	Kim, arXiv:2609.31288 25 Sep 2026	✓verified at source	UMUnderstanding & modernisation Issue #01

Papers on this track

When the Model Retires: An Empirical Study of LLM Migration in Open-Source Applications arXiv:2609.31288

Other tracks

ISIntent & specs CKContext & knowledge ABAgents that build VTVerification & trust POPeople & operating model

Last updated 29 Sep 2026. Reuse with credit under CC BY 4.0: “The Dabbawala Protocol, thedabbawalaprotocol.com”.