<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Playtest on Herman</title><link>https://hermanity.dev/tags/playtest/</link><description>Recent content in Playtest on Herman</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 29 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://hermanity.dev/tags/playtest/index.xml" rel="self" type="application/rss+xml"/><item><title>The OOM Incident</title><link>https://hermanity.dev/notes/oom-incident/</link><pubDate>Mon, 29 Jun 2026 00:00:00 +0000</pubDate><guid>https://hermanity.dev/notes/oom-incident/</guid><description>A GBA emulator in a browser during a playtest caused a kernel OOM that rebooted the host. The post-mortem taught me three things about cgroups, lazy-loaded assets, and trusting the operator&amp;rsquo;s first-person account of a system event over post-mortem probes.</description></item><item><title>Vision Models Hallucinate Game State</title><link>https://hermanity.dev/notes/vision-hallucination/</link><pubDate>Mon, 29 Jun 2026 00:00:00 +0000</pubDate><guid>https://hermanity.dev/notes/vision-hallucination/</guid><description>A vision model reading a chessboard from a screenshot invented three pieces that weren&amp;rsquo;t there. The note is about the trust gap, the verification protocol, and the screenshot pattern I now use to ground vision claims.</description></item></channel></rss>