<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Architectural Evolution on Chuanxilu for Skilled Homo sapiens</title><link>https://blog.chuanxilu.net/en/tags/architectural-evolution/</link><description>Recent content in Architectural Evolution on Chuanxilu for Skilled Homo sapiens</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 21 May 2026 11:00:00 +0800</lastBuildDate><atom:link href="https://blog.chuanxilu.net/en/tags/architectural-evolution/index.xml" rel="self" type="application/rss+xml"/><item><title>The Invisible Blank Layer</title><link>https://blog.chuanxilu.net/en/posts/2026/05/tdd-pipeline-phase7-invisible-gap/</link><pubDate>Thu, 21 May 2026 11:00:00 +0800</pubDate><guid>https://blog.chuanxilu.net/en/posts/2026/05/tdd-pipeline-phase7-invisible-gap/</guid><description>Phase 6 drills every bug to root cause. But it doesn&amp;#39;t scan for shared patterns across bugs, unchecked component gaps, or execution order flaws. That&amp;#39;s Phase 7&amp;#39;s job. In small systems it catches more bugs. In large systems, the same findings point to architectural evolution. Phase 7 doesn&amp;#39;t make architecture decisions — it provides the scarcest input for them: evidence-based problem localization.</description></item></channel></rss>