<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Phase Space</title><link>https://phasespace.co/</link><description>Recent content on Phase Space</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 22 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://phasespace.co/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Your LLM NPCs Sound the Same (And How to Fix It)</title><link>https://phasespace.co/blog/why-your-llm-npcs-sound-the-same/</link><pubDate>Sun, 22 Feb 2026 00:00:00 +0000</pubDate><guid>https://phasespace.co/blog/why-your-llm-npcs-sound-the-same/</guid><description>&lt;p>&lt;em>&amp;ldquo;Let me tell you, my good friend&amp;hellip;&amp;rdquo;&lt;/em>&lt;/p>
&lt;p>If you&amp;rsquo;ve built LLM-powered NPCs, you&amp;rsquo;ve heard this. Your character starts strong, maybe even impressive. But by turn 20, something&amp;rsquo;s wrong. They&amp;rsquo;re repeating themselves. The same phrases. The same gestures. The same rhythm.&lt;/p>
&lt;p>I ran 150 turns of dialogue with an LLM-powered character last week:&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Pattern&lt;/th>
 &lt;th>Frequency&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>&amp;ldquo;takes a long swig from his glass&amp;rdquo;&lt;/td>
 &lt;td>&lt;strong>59%&lt;/strong> of responses&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&amp;ldquo;my good friend/man/fellow&amp;rdquo;&lt;/td>
 &lt;td>&lt;strong>30%&lt;/strong> of responses&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&amp;ldquo;eyes unfocused&amp;rdquo;&lt;/td>
 &lt;td>&lt;strong>15%&lt;/strong> of responses&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&amp;ldquo;let me tell you&amp;rdquo;&lt;/td>
 &lt;td>&lt;strong>13%&lt;/strong> of responses&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>My character—a boozy ex-politician I&amp;rsquo;ll call Frank—couldn&amp;rsquo;t stop drinking. Not because it was dramatically appropriate. Because the LLM fell into a rut.&lt;/p></description></item><item><title>Part 2: Re-Clocking: What I Actually Did</title><link>https://phasespace.co/blog/timebase-corrector-part-2/</link><pubDate>Sat, 14 Feb 2026 00:00:00 +0000</pubDate><guid>https://phasespace.co/blog/timebase-corrector-part-2/</guid><description>&lt;p>&lt;em>In &lt;a href="https://phasespace.co/blog/timebase-corrector-part-1/">Part 1&lt;/a>, I recognized the parallel: my nervous system (after developmental trauma and Complex PTSD) was experiencing timebase error. Perfectly functional responses clocked against old threats instead of present safety. Recognition changes your relationship to symptoms. But recognition alone doesn&amp;rsquo;t regulate a nervous system.&lt;/em>&lt;/p>
&lt;p>&lt;em>You still need a stable reference to re-clock against.&lt;/em>&lt;/p>
&lt;hr>
&lt;h2 id="building-your-internal-sync-generator">Building Your Internal Sync Generator&lt;/h2>
&lt;p>In video, the TBC forces unstable signals to align with a master clock. In nervous system work, you build that clock yourself.&lt;/p></description></item><item><title>Part 1: The Timebase Corrector and the Traumatized Brain</title><link>https://phasespace.co/blog/timebase-corrector-part-1/</link><pubDate>Wed, 11 Feb 2026 00:00:00 +0000</pubDate><guid>https://phasespace.co/blog/timebase-corrector-part-1/</guid><description>&lt;p>&lt;em>I learned about timebase correctors doing post-production work. Years later, during deep therapy and meditation retreat work, I saw the connection.&lt;/em>&lt;/p>
&lt;hr>
&lt;p>The problem is always the same: &lt;strong>the signal has lost its relationship to a stable reference.&lt;/strong>&lt;/p>
&lt;p>In video, it&amp;rsquo;s called timebase error. In trauma, it&amp;rsquo;s autonomic dysregulation. Both systems generate perfectly functional responses to the wrong moment in time.&lt;/p>
&lt;hr>
&lt;h2 id="the-problem-unstable-signals">The Problem: Unstable Signals&lt;/h2>
&lt;h3 id="in-video">In Video&lt;/h3>
&lt;p>Videotape is a beautiful, terrible medium. Magnetic particles on polyester film, scraped across spinning heads at precise speeds. When it works, it&amp;rsquo;s engineering and chemical wizardry. When it doesn&amp;rsquo;t, the picture rolls, tears, or bleeds color like watercolor in rain.&lt;/p></description></item><item><title>About</title><link>https://phasespace.co/about/</link><pubDate>Sat, 07 Feb 2026 00:00:00 +0000</pubDate><guid>https://phasespace.co/about/</guid><description>&lt;h1 id="paul-kyle">Paul Kyle&lt;/h1>
&lt;p>Faculty and Lead Technical Specialist, Post Production at &lt;a href="https://filmvideo.calarts.edu">CalArts School of Film/Video&lt;/a> since 2010. Digital video since 1995. MFA San Francisco Art Institute.&lt;/p>
&lt;p>I teach editing, color grading, and post-production. I developed winter session courses on AI and the Moving Image. Before CalArts, I spent a decade in NYC post-production and co-founded a digital media startup. Along the way I trained in clinical psychology, specializing in mindfulness-based and expressive arts therapy. Twenty years of meditation practice taught me that attention itself is a signal processing problem.&lt;/p></description></item><item><title/><link>https://phasespace.co/blog/drafts/homelab-techstack-draft/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://phasespace.co/blog/drafts/homelab-techstack-draft/</guid><description>&lt;h1 id="the-phase-space-a-complete-homelab-tech-stack-inventory">The Phase Space: A Complete Homelab Tech Stack Inventory&lt;/h1>
&lt;p>&lt;em>As of February 2026. This is a raw inventory draft for phasespace.co — edit for public consumption.&lt;/em>&lt;/p>
&lt;hr>
&lt;h2 id="tldr">TL;DR&lt;/h2>
&lt;p>Three-node Proxmox cluster, two NVIDIA Blackwell GPUs (RTX 5090 + RTX 5060), 156GB total RAM, 28TB NAS, 40+ LXC containers and VMs, four specialized AI agents running on-premises 24/7. This is what it actually takes to run AI infrastructure at home.&lt;/p>
&lt;hr>
&lt;h2 id="proxmox-cluster-overview">Proxmox Cluster Overview&lt;/h2>
&lt;p>&lt;strong>Cluster name:&lt;/strong> grue-cluster&lt;br>
&lt;strong>PVE version:&lt;/strong> 9.1.2, kernel 6.17.4-1-pve&lt;br>
&lt;strong>Nodes:&lt;/strong> 3 (all online, uptime ~4.8 days at time of writing)&lt;/p></description></item></channel></rss>