<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>MNSTRY.org · Boundaries</title>
    <link>https://mnstry.org/topics/boundary/</link>
    <description>Five rooms on where a boundary actually is, as opposed to where the interface
suggests it is. A view that hides and ships, a pipeline that finishes and
sends, an architecture with no path to build a leak out of, an acceptance
contract satisfied by an unusable screen, and a fact settled twice. The last
two come from a single review and mark the honest limit of the argument the
first three make.</description>
    <item>
      <title>Projection is not protection</title>
      <link>https://mnstry.org/writing/projection-is-not-protection/</link>
      <guid isPermaLink="true">https://mnstry.org/writing/projection-is-not-protection/</guid>
      <description>Why audience metadata, filtered views, and hidden panels protect nothing, and what five near-identical warnings in our own tooling reveal about how badly people want them to. The canonical treatment of the projection boundary.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Readiness is not authorization</title>
      <link>https://mnstry.org/writing/readiness-is-not-authorization/</link>
      <guid isPermaLink="true">https://mnstry.org/writing/readiness-is-not-authorization/</guid>
      <description>What collapses when a system treats completed work as its own release approval, and the posture that keeps the last step a human one. The canonical treatment of the readiness-authorization split.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The unleakable context</title>
      <link>https://mnstry.org/writing/unleakable-context/</link>
      <guid isPermaLink="true">https://mnstry.org/writing/unleakable-context/</guid>
      <description>Why the only private context that stays private is the context with no path out of its domain, with Signal's subpoena record as the existence proof. The canonical treatment of the domain lock.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Mount continuity is not usability</title>
      <link>https://mnstry.org/writing/mount-continuity-is-not-usability/</link>
      <guid isPermaLink="true">https://mnstry.org/writing/mount-continuity-is-not-usability/</guid>
      <description>Where structural testing stops being sufficient, read off a case in which every continuity assertion held while the text field sat below the visible edge of the screen. The canonical treatment of the on-screen geometry contract.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Two classifiers, two truths</title>
      <link>https://mnstry.org/writing/two-classifiers-two-truths/</link>
      <guid isPermaLink="true">https://mnstry.org/writing/two-classifiers-two-truths/</guid>
      <description>A keyboard that was open and closed at once inside one running application, and why the repair is a single owner per fact rather than two components instructed to agree more carefully. The canonical treatment of one authority per fact.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
