<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Matt Smith — Writing</title>
    <link>https://servicedesign.dev/</link>
    <atom:link href="https://servicedesign.dev/feed.xml" rel="self" type="application/rss+xml" />
    <description>Operational design, payment integrations, and the Foundation Layer framework.</description>
    <language>en-us</language>
    <lastBuildDate>Thu, 17 Sep 2026 12:00:00 GMT</lastBuildDate>
    <item>
      <title>UAT is where integrations go to die</title>
      <link>https://servicedesign.dev/writing/uat-is-where-integrations-go-to-die</link>
      <guid isPermaLink="true">https://servicedesign.dev/writing/uat-is-where-integrations-go-to-die</guid>
      <pubDate>Tue, 25 Aug 2026 12:00:00 GMT</pubDate>
      <description>The last mile of a payment integration has no owner, no memory, and no evidence — which is why it quietly absorbs more schedule than the build itself.</description>
    </item>
    <item>
      <title>How I evaluate a vendor API before the dev team touches it</title>
      <link>https://servicedesign.dev/writing/vendor-api-evaluation</link>
      <guid isPermaLink="true">https://servicedesign.dev/writing/vendor-api-evaluation</guid>
      <pubDate>Tue, 25 Aug 2026 12:00:00 GMT</pubDate>
      <description>Every vendor API arrives as a set of promises. The gate that turns them into tested facts — auth, unhappy paths, docs versus behavior, sandbox fidelity, operational readiness — before the integration is committed to.</description>
    </item>
    <item>
      <title>The Foundation Layer</title>
      <link>https://servicedesign.dev/writing/the-foundation-layer</link>
      <guid isPermaLink="true">https://servicedesign.dev/writing/the-foundation-layer</guid>
      <pubDate>Tue, 25 Aug 2026 12:00:00 GMT</pubDate>
      <description>Why most problems surface at L5 and most fixes start at L1. The operational design framework behind servicedesign.dev, argued in full.</description>
    </item>
  </channel>
</rss>
