<?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>Okf on orndorff.dev</title>
    <link>https://orndorff.dev/tags/okf/</link>
    <description>Recent content in Okf on orndorff.dev</description>
    <generator>Hugo -- 0.138.0</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 21 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://orndorff.dev/tags/okf/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Expert Is the Graph: A Local GraphRAG Toolkit for Micro-Scale Domain Experts</title>
      <link>https://orndorff.dev/posts/the-expert-is-the-graph/</link>
      <pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://orndorff.dev/posts/the-expert-is-the-graph/</guid>
      <description>&lt;p&gt;This is the post I&amp;rsquo;ve been building toward across three earlier ones. It pulls the
whole system together — the toolkit, the agent, the benchmarks — and ends on the
experiment that reframed the entire project for me: I handed the &lt;em&gt;same&lt;/em&gt; knowledge
graph to a tiny local model and to a frontier model (Claude Sonnet), graded both
with the same judge, and &lt;strong&gt;the frontier model didn&amp;rsquo;t win&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;That result is the thesis. When you put a domain behind a good retrieval layer,
the expertise lives in the &lt;em&gt;graph&lt;/em&gt;, not the model reading it. Which means you can
build something I&amp;rsquo;ve started calling a &lt;strong&gt;micro-scale domain expert&lt;/strong&gt;: a small,
portable, inspectable knowledge artifact that any agent — a 4-bit model on your
laptop or a frontier model in the cloud — can pick up and answer from. This post
is about the toolkit that makes those, and the evidence that the cheap part (the
model) is interchangeable while the valuable part (the graph) is where the work
goes.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
