<?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: Bhushan Sribhashyam</title>
    <description>The latest articles on DEV Community by Bhushan Sribhashyam (@bushans).</description>
    <link>https://dev.to/bushans</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%2F2415308%2F1870ff1d-bd2b-469c-bae2-07c81754a0dd.jpg</url>
      <title>DEV Community: Bhushan Sribhashyam</title>
      <link>https://dev.to/bushans</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/bushans"/>
    <language>en</language>
    <item>
      <title>Make your systems agent-readable in one command</title>
      <dc:creator>Bhushan Sribhashyam</dc:creator>
      <pubDate>Wed, 01 Jul 2026 16:44:37 +0000</pubDate>
      <link>https://dev.to/bushans/make-your-systems-agent-readable-in-one-command-348a</link>
      <guid>https://dev.to/bushans/make-your-systems-agent-readable-in-one-command-348a</guid>
      <description>&lt;h2&gt;
  
  
  The context problem
&lt;/h2&gt;

&lt;p&gt;Everyone is wiring AI agents into their stack. But an agent is only as smart as&lt;br&gt;
the context it's given, and that context — table schemas, join logic, API docs,&lt;br&gt;
the "why" behind a system — is fragmented across databases, wikis, and&lt;br&gt;
codebases. Most attempts to fix this either lock your knowledge in a proprietary&lt;br&gt;
catalog or ask an LLM to hallucinate documentation you can't trust.&lt;/p&gt;
&lt;h2&gt;
  
  
  A simpler idea: knowledge as files
&lt;/h2&gt;

&lt;p&gt;Google recently proposed the &lt;a href="https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md" rel="noopener noreferrer"&gt;Open Knowledge Format&lt;/a&gt;&lt;br&gt;
(OKF): represent knowledge as &lt;em&gt;just markdown files with YAML frontmatter&lt;/em&gt;. No&lt;br&gt;
schema registry, no SDK, no central authority. A bundle is a directory of&lt;br&gt;
"concepts"; each file is readable by humans, parseable by agents, and diffable&lt;br&gt;
in git.&lt;/p&gt;

&lt;p&gt;I liked it enough to build &lt;strong&gt;okfgen&lt;/strong&gt; — a reference implementation of both sides&lt;br&gt;
of that ecosystem.&lt;/p&gt;
&lt;h2&gt;
  
  
  Deterministic by default
&lt;/h2&gt;

&lt;p&gt;okfgen's one opinion: it extracts &lt;em&gt;facts&lt;/em&gt;, not guesses. Point it at a database&lt;br&gt;
and it reads the actual column schemas. Point it at a repo and it maps the real&lt;br&gt;
module structure and dependencies. No LLM, no API key — so the output is&lt;br&gt;
reproducible, auditable, and runs in an air-gapped environment. (An optional&lt;br&gt;
&lt;code&gt;--llm&lt;/code&gt; flag adds Claude-written polish where you want it, but nothing needs it.)&lt;/p&gt;
&lt;h2&gt;
  
  
  Producers → bundle → consumers
&lt;/h2&gt;

&lt;p&gt;The &lt;em&gt;producers&lt;/em&gt; turn a source into a bundle:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;uvx okfgen generate ./my-repo
uvx okfgen generate schema:./warehouse.json
uvx okfgen generate ckan:https://data.gov/dataset/...
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then an &lt;em&gt;enrichment&lt;/em&gt; pass infers join paths between tables from foreign-key&lt;br&gt;
naming (&lt;code&gt;customer_id → customers&lt;/code&gt;) and wires backlinks, so the knowledge becomes&lt;br&gt;
a navigable graph.&lt;/p&gt;

&lt;p&gt;The &lt;em&gt;consumers&lt;/em&gt; read any bundle back — regardless of who produced it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;visualize&lt;/strong&gt; → a self-contained interactive graph (one HTML file, no backend, data never leaves the page)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;search&lt;/strong&gt; → a full-text index&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;ask&lt;/strong&gt; → a reasoning agent that answers with citations &lt;em&gt;and shows which concepts it traversed&lt;/em&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;validate&lt;/strong&gt; → an OKF conformance check&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  In your agent, via MCP
&lt;/h2&gt;

&lt;p&gt;okfgen ships an MCP server, so Claude, Cursor, and any MCP client can generate&lt;br&gt;
and reason over bundles directly. An agent can now say "catalog this database&lt;br&gt;
and tell me how orders relate to customers" and get a grounded, cited answer.&lt;/p&gt;

&lt;h2&gt;
  
  
  It works on real data today
&lt;/h2&gt;

&lt;p&gt;The same adapters that read a local schema also read live open-data portals —&lt;br&gt;
CKAN (data.gov, Toronto, thousands of city/gov portals) and Socrata (NYC,&lt;br&gt;
Seattle, Chicago). The live demo gallery is built from exactly these:&lt;br&gt;
&lt;a href="https://bushans.github.io/okfgen/" rel="noopener noreferrer"&gt;browse the interactive graphs →&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;uvx okfgen generate &lt;span class="nb"&gt;.&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It's open source (Apache-2.0), on PyPI, and early — the spec itself is a v0.1&lt;br&gt;
draft. If you try it, I'd genuinely love to hear what source you pointed it at&lt;br&gt;
and where it fell short.&lt;/p&gt;

&lt;p&gt;⭐ &lt;a href="https://github.com/bushans/okfgen" rel="noopener noreferrer"&gt;github.com/bushans/okfgen&lt;/a&gt;&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>python</category>
      <category>ai</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
