<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Json Schema on SoloSoft</title><link>https://www.solosoft.dev/tags/json-schema/</link><description>Recent content in Json Schema on SoloSoft</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 17 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.solosoft.dev/tags/json-schema/index.xml" rel="self" type="application/rss+xml"/><item><title>AG-UI 1.0 Audited: 31 Event Types, 68 Conformance Streams — and Two First-Party SDKs the Corpus Never Reaches</title><link>https://www.solosoft.dev/post/ag-ui-conformance-audit/</link><pubDate>Tue, 17 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.solosoft.dev/post/ag-ui-conformance-audit/</guid><description>&lt;p&gt;Most &amp;ldquo;open protocols&amp;rdquo; for AI agents are a README, a logo, and a TypeScript package that happens to talk to its own server. AG-UI is not that. It ships a 94,359-byte JSON Schema as the normative contract, 219 fixture documents, 68 recorded event streams with machine-readable expectations, and a harness that asserts the corpus cannot quietly shrink.&lt;/p&gt;
&lt;p&gt;That makes it auditable in a way almost nothing else in this space is. So I audited it: cloned the repo at &lt;code&gt;main&lt;/code&gt;, installed the &lt;em&gt;published&lt;/em&gt; packages from npm and PyPI rather than the monorepo source, and ran the protocol&amp;rsquo;s own conformance corpus through a replay harness I wrote against the shipped client. Then I checked the parts the corpus says it does not cover.&lt;/p&gt;</description></item></channel></rss>