<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Legacy-Modernisation on M.F.Borman</title><link>https://www.mfborman.nl/tags/legacy-modernisation/</link><description>Recent content in Legacy-Modernisation on M.F.Borman</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 17 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.mfborman.nl/tags/legacy-modernisation/feed.xml" rel="self" type="application/rss+xml"/><item><title>The compounding pipeline: from novel to deterministic</title><link>https://www.mfborman.nl/posts/2026-02-17-the-compounding-pipeline/</link><pubDate>Tue, 17 Feb 2026 00:00:00 +0000</pubDate><guid>https://www.mfborman.nl/posts/2026-02-17-the-compounding-pipeline/</guid><description>The first time AI solves a migration pattern, it is novel. The second time, a recipe. The tenth time, deterministic. Context maturity is what makes this compound.</description></item><item><title>Context maturity is a capability, not a project</title><link>https://www.mfborman.nl/posts/2026-02-14-context-maturity-is-a-capability/</link><pubDate>Sat, 14 Feb 2026 00:00:00 +0000</pubDate><guid>https://www.mfborman.nl/posts/2026-02-14-context-maturity-is-a-capability/</guid><description>AI makes backward context creation feasible at estate scale. What matters is whether attested context exists — the technology is incidental.</description></item><item><title>AI-extracted understanding is a hypothesis, not documentation</title><link>https://www.mfborman.nl/posts/2026-02-12-ai-extracted-understanding-is-a-hypothesis/</link><pubDate>Thu, 12 Feb 2026 00:00:00 +0000</pubDate><guid>https://www.mfborman.nl/posts/2026-02-12-ai-extracted-understanding-is-a-hypothesis/</guid><description>When AI analyses existing code, the output looks like documentation. It is not. Validation means checking whether an interpretation matches observed reality.</description></item><item><title>Legacy is context maturity, not code age</title><link>https://www.mfborman.nl/posts/2026-02-10-legacy-is-context-maturity-not-code-age/</link><pubDate>Tue, 10 Feb 2026 00:00:00 +0000</pubDate><guid>https://www.mfborman.nl/posts/2026-02-10-legacy-is-context-maturity-not-code-age/</guid><description>A twenty-year COBOL estate has the same problem as a three-year microservices platform whose team rotated out. The variable is context maturity.</description></item></channel></rss>