<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>MNSTRY.org · Approval</title>
    <link>https://mnstry.org/topics/approval/</link>
    <description>Five rooms on the difference between an approval and a record of one. A
marker that has to travel in the diff it approves, an exception list allowed
to move in only one direction, a permission strong enough to fail the build,
a disclosure the format refuses to call reversible, and an erasure that
actually works. The through-line is not diligence. It is whether the shape
of the record leaves room for the thing a person actually decided.</description>
    <item>
      <title>Justification travels in the diff</title>
      <link>https://mnstry.org/writing/justification-travels-in-the-diff/</link>
      <guid isPermaLink="true">https://mnstry.org/writing/justification-travels-in-the-diff/</guid>
      <description>How to tell a real approval from a filed one, and why three unrelated parts of our own tooling reached the same placement rule without consulting each other. The canonical treatment of co-located justification.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The ratchet</title>
      <link>https://mnstry.org/writing/the-ratchet/</link>
      <guid isPermaLink="true">https://mnstry.org/writing/the-ratchet/</guid>
      <description>How a codebase enforces a standard it does not yet meet, without lying about its state and without cleaning up inside someone else's unfinished work. The canonical treatment of the shrink-only exception list.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Consent that fails CI</title>
      <link>https://mnstry.org/writing/consent-that-fails-ci/</link>
      <guid isPermaLink="true">https://mnstry.org/writing/consent-that-fails-ci/</guid>
      <description>How consent moves from a stored preference to a compile-time property, and why the build is the only guard with a perfect attendance record. The canonical treatment of typed consent.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Disclosure is irrevocable</title>
      <link>https://mnstry.org/writing/disclosure-is-irrevocable/</link>
      <guid isPermaLink="true">https://mnstry.org/writing/disclosure-is-irrevocable/</guid>
      <description>Why moving material across a read boundary is typed as durable and non-revocable, and what a system gives up when it stops promising a takeback. The canonical treatment of irrevocable disclosure.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Destroy the key</title>
      <link>https://mnstry.org/writing/destroy-the-key/</link>
      <guid isPermaLink="true">https://mnstry.org/writing/destroy-the-key/</guid>
      <description>How an append-only history and an enforceable right to erasure stop being in conflict, and what the technique costs in honesty. The canonical treatment of cryptographic erasure.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
