<?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>5-Why on 能工智人的传习录</title><link>https://blog.chuanxilu.net/tags/5-why/</link><description>Recent content in 5-Why on 能工智人的传习录</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Wed, 06 May 2026 09:00:00 +0800</lastBuildDate><atom:link href="https://blog.chuanxilu.net/tags/5-why/index.xml" rel="self" type="application/rss+xml"/><item><title>追问的最后一道防线：独立确认与协议的自反性</title><link>https://blog.chuanxilu.net/posts/2026/05/inquiry-protocol-design-3/</link><pubDate>Wed, 06 May 2026 09:00:00 +0800</pubDate><guid>https://blog.chuanxilu.net/posts/2026/05/inquiry-protocol-design-3/</guid><description>追问协议的最后一道防线：独立确认者用可证伪性检验找反例，对抗 AI 的浅层锚定。以及追问协议的来路——从 18 个 bug 的实践到 v0.4.1 的升级，和未来自反性的计划。</description></item><item><title>给 AI 套上质量缰绳：追问协议的七个条件</title><link>https://blog.chuanxilu.net/posts/2026/05/inquiry-protocol-design-2/</link><pubDate>Tue, 05 May 2026 17:00:00 +0800</pubDate><guid>https://blog.chuanxilu.net/posts/2026/05/inquiry-protocol-design-2/</guid><description>追问协议的终止条件设计：T1-T3 是地板（保证 AI 走得够深），HC1-HC4 是护栏（防止追问失控）。T2 的预防性反事实检验是最关键的洞察。</description></item><item><title>AI 用不好 5-Why：浅尝辄止、单线追踪与确认偏差</title><link>https://blog.chuanxilu.net/posts/2026/05/inquiry-protocol-design-1/</link><pubDate>Tue, 05 May 2026 10:00:00 +0800</pubDate><guid>https://blog.chuanxilu.net/posts/2026/05/inquiry-protocol-design-1/</guid><description>5-Why 交给 AI 为什么用不好？不是方法论过时了，是 AI 的思考质量天然不足——停得太早、只追一条线、只找支持证据。一个四轮归因全部失败的真实案例。</description></item></channel></rss>