<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Rag on Juntak Noh — AI Notes</title>
    <link>https://ai.klavierhye.cc/tags/rag/</link>
    <description>Recent content in Rag on Juntak Noh — AI Notes</description>
    <generator>Hugo -- 0.147.7</generator>
    <language>en</language>
    <lastBuildDate>Tue, 22 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ai.klavierhye.cc/tags/rag/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Too Many Guardrails Made the Bigger Model Worse: Deleting 13,528 Lines of Orchestration</title>
      <link>https://ai.klavierhye.cc/posts/too-many-guardrails/</link>
      <pubDate>Tue, 22 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://ai.klavierhye.cc/posts/too-many-guardrails/</guid>
      <description>&lt;p&gt;&lt;em&gt;This is &lt;strong&gt;Part 7&lt;/strong&gt;, the last of Field Notes from a Korean Phone Voice Agent, a seven-part series about a project I led: a real-time Korean phone voice agent (STT → LLM → TTS) for a public-service call line. STT evaluation → Rules vs. models → Latency → Silent failures → Guardrails → Metrics → &lt;strong&gt;Simplification&lt;/strong&gt;. &lt;a href=&#34;https://ai.klavierhye.cc/posts/how-guardrails-pile-up/&#34;&gt;Part 5&lt;/a&gt; showed how the dialog layer&amp;rsquo;s rules piled up, and &lt;a href=&#34;https://ai.klavierhye.cc/posts/llm-eval-metric-chose-architecture/&#34;&gt;Part 6&lt;/a&gt; why the evaluation kept rewarding them. This part is about taking them out.&lt;/em&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
