<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Plausibly Wrong</title><link>https://zwischen.ai/blog/</link><description>Recent content on Plausibly Wrong</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 19 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://zwischen.ai/blog/feed.xml" rel="self" type="application/rss+xml"/><item><title>AI writing its own tests is theatre</title><link>https://zwischen.ai/blog/ai-writing-its-own-tests-is-theatre/</link><pubDate>Sun, 19 Apr 2026 00:00:00 +0000</pubDate><guid>https://zwischen.ai/blog/ai-writing-its-own-tests-is-theatre/</guid><description>&lt;p&gt;An org. chart slide is up on the screen in your AI strategy deck. Three boxes, clean arrows, comforting symmetry: &amp;ldquo;Code Agent&amp;rdquo; → &amp;ldquo;Testing Subagent&amp;rdquo; → &amp;ldquo;Review Agent.&amp;rdquo; Somebody says &amp;ldquo;defense in depth,&amp;rdquo; and the room nods because it looks like the software org. charts you grew up trusting.&lt;/p&gt;
&lt;p&gt;But you&amp;rsquo;ve seen what happens next. The code ships with a bug that the tests &amp;ldquo;proved&amp;rdquo; couldn&amp;rsquo;t exist. The review agent writes a confident paragraph about why the tests are sufficient. And when your team digs in, you find the same blind spot echoed three times, dressed up as process.&lt;/p&gt;</description></item><item><title>Editorial standards</title><link>https://zwischen.ai/blog/editorial-standards/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://zwischen.ai/blog/editorial-standards/</guid><description>&lt;p&gt;Plausibly Wrong is published by Zwischen. We write about how AI systems actually work, where they break, and what that means for the decisions you&amp;rsquo;re making.&lt;/p&gt;
&lt;h2 id="how-we-publish"&gt;How we publish&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Every post is edited by a human before release.&lt;/li&gt;
&lt;li&gt;We verify factual claims we consider material — numbers, quotes, product capabilities, legal and regulatory assertions.&lt;/li&gt;
&lt;li&gt;We aim to distinguish clearly between observed behavior, interpretation, and recommendation.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="tools"&gt;Tools&lt;/h2&gt;
&lt;p&gt;We use modern tools — including AI — during research and drafting. Tools don&amp;rsquo;t get a byline. The editorial team is accountable for what we publish.&lt;/p&gt;</description></item></channel></rss>