<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>MNSTRY.org · Incentives</title>
    <link>https://mnstry.org/topics/incentives/</link>
    <description>Six rooms on the same question, which is what a product does when the
number it reports upward and the outcome it exists for pull in opposite
directions. The order runs from the smallest unit to the largest, a
single pause before a reply, then the shape of a week, then the boundary
of a commercial contract, then a namespace, then an architecture, and
finally the thing a business would most like to sell. The through-line is
that none of these refusals survives as a value. Each one survives only
where it was written into something that costs an argument to reverse.</description>
    <item>
      <title>Silence is an intervention</title>
      <link>https://mnstry.org/writing/silence-is-an-intervention/</link>
      <guid isPermaLink="true">https://mnstry.org/writing/silence-is-an-intervention/</guid>
      <description>Why we decline to optimize time to first token in relational contexts, from the response-time law that governs the rest of software to the delays our specifications require on purpose.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Time as rhythm, not ledger</title>
      <link>https://mnstry.org/writing/time-as-rhythm-not-ledger/</link>
      <guid isPermaLink="true">https://mnstry.org/writing/time-as-rhythm-not-ledger/</guid>
      <description>The design case against streak pressure, from the counter-model our own philosophy document names to the four states of absence we ship in its place.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Theme the atmosphere, never the contract</title>
      <link>https://mnstry.org/writing/theme-the-atmosphere-never-the-contract/</link>
      <guid isPermaLink="true">https://mnstry.org/writing/theme-the-atmosphere-never-the-contract/</guid>
      <description>What a tenant may restyle and what stays platform infrastructure, and why the grammar of safety has to travel with the person instead of with the brand.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The absence is the guardrail</title>
      <link>https://mnstry.org/writing/the-absence-is-the-guardrail/</link>
      <guid isPermaLink="true">https://mnstry.org/writing/the-absence-is-the-guardrail/</guid>
      <description>How a design system prevents harm by refusing to build the affordance at all, from a pack-size law to a token namespace with no streak in it.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Unable, not instructed</title>
      <link>https://mnstry.org/writing/unable-not-instructed/</link>
      <guid isPermaLink="true">https://mnstry.org/writing/unable-not-instructed/</guid>
      <description>Three places we put hard constraints below the model rather than inside its prompt, from a deterministic phase evaluator to a database trigger, and why the difference from a well-written instruction is categorical.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Depth by readiness</title>
      <link>https://mnstry.org/writing/depth-by-readiness/</link>
      <guid isPermaLink="true">https://mnstry.org/writing/depth-by-readiness/</guid>
      <description>Why the gates in what we build open on demonstrated experiment rather than on information consumed, time elapsed, or money paid, and what it costs to refuse the easy proxies.</description>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
