<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
  xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
  xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Rashed Wahdan · Incident journal</title>
    <link>https://relsayed.online</link>
    <description>Rashed Wahdan’s portfolio and incident journal, with postmortems and practical notes on reliability.</description>
    <item>
      <title>A rollout that pushed latency past budget</title>
      <link>https://relsayed.online/journal/rollout-latency/</link>
      <description>A fictional postmortem following a latency spike from detection through rollback and recovery.</description>
      <pubDate>Fri, 20 Nov 2026 00:00:00 -0000</pubDate>
      <guid isPermaLink="true">https://relsayed.online/journal/rollout-latency/</guid>
      <dc:date>2026-11-20T00:00:00Z</dc:date>
    </item>
    <item>
      <title>What to capture while an incident is live</title>
      <link>https://relsayed.online/journal/notes-during-incident/</link>
      <description>A short log format for preserving observations, decisions, and recovery checks.</description>
      <pubDate>Thu, 19 Nov 2026 00:00:00 -0000</pubDate>
      <guid isPermaLink="true">https://relsayed.online/journal/notes-during-incident/</guid>
      <dc:date>2026-11-19T00:00:00Z</dc:date>
    </item>
    <item>
      <title>Turn postmortem findings into follow-up work</title>
      <link>https://relsayed.online/journal/postmortem-followups/</link>
      <description>A way to write action items with a clear owner and a checkable outcome.</description>
      <pubDate>Wed, 18 Nov 2026 00:00:00 -0000</pubDate>
      <guid isPermaLink="true">https://relsayed.online/journal/postmortem-followups/</guid>
      <dc:date>2026-11-18T00:00:00Z</dc:date>
    </item>
  </channel>
</rss>