<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: PSKK-Git</title>
    <description>The latest articles on DEV Community by PSKK-Git (@chaddler).</description>
    <link>https://dev.to/chaddler</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F918611%2F9d36ee06-6096-4172-9a02-4c49a9182f00.png</url>
      <title>DEV Community: PSKK-Git</title>
      <link>https://dev.to/chaddler</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/chaddler"/>
    <language>en</language>
    <item>
      <title>The washing machine ate a customer's bedsheets, and the owner was at a wedding</title>
      <dc:creator>PSKK-Git</dc:creator>
      <pubDate>Sat, 07 Nov 2026 19:36:57 +0000</pubDate>
      <link>https://dev.to/chaddler/the-washing-machine-ate-a-customers-bedsheets-and-the-owner-was-at-a-wedding-h91</link>
      <guid>https://dev.to/chaddler/the-washing-machine-ate-a-customers-bedsheets-and-the-owner-was-at-a-wedding-h91</guid>
      <description>&lt;p&gt;&lt;em&gt;Flip the Switch hackathon · Sunrise Room&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;A washer in a small laundromat dies with a customer's bedsheets inside. Meena, at the counter, needs two answers: is this machine known to be faulty, and may I refund this? The owner is at a wedding. So she types into WhatsApp and hopes.&lt;/p&gt;

&lt;p&gt;I put the whole scene in one Switch room. Staff post like it's a group chat. Three agents do the legwork: one diagnoses the fault, one prepares the refund, one checks the plan. One rule sits above everything: &lt;strong&gt;nothing that costs money happens until the owner says yes.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The part I built is the &lt;strong&gt;scribe&lt;/strong&gt;, a memory agent that never erases. When a rule changes, the old one is superseded and kept, so you can still explain last Tuesday's refund. &lt;code&gt;blast #3&lt;/code&gt; shows what else rested on a rule before you change it. (The idea comes from Zep's Graphiti. Mine is one SQLite file, and I haven't benchmarked it.)&lt;/p&gt;

&lt;p&gt;In a real room, the triager read the machine's fault (E21), the scribe recalled the earlier incident and named who reported it, and the fixer staged a Rs 180 refund that waited for my approval. It also broke in ways 55 passing tests never caught: agents in an empty folder, no &lt;code&gt;python&lt;/code&gt; on the machine, and a chat server that stalled when the laptop ran low on memory.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Honest limits:&lt;/strong&gt; the shop is a mock and no money moves. Approval is a policy enforced by Switch's addressing rules, not a lock. And I couldn't show a second staff member being refused, because the room had one account.&lt;/p&gt;

&lt;p&gt;Without Switch's rooms, jobs, addressing and protocol, this is a script on my laptop. With them, the scribe is a teammate.&lt;/p&gt;

&lt;p&gt;Code and demo: &lt;a href="https://github.com/PSKK-Git/sunrise-room" rel="noopener noreferrer"&gt;https://github.com/PSKK-Git/sunrise-room&lt;/a&gt;&lt;br&gt;
&lt;a href="https://github.com/PSKK-Git/sunrise-room" rel="noopener noreferrer"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>agents</category>
      <category>ai</category>
      <category>hackathon</category>
    </item>
  </channel>
</rss>
