<?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>Forem: terryncew</title>
    <description>The latest articles on Forem by terryncew (@terryncew).</description>
    <link>https://forem.com/terryncew</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3505173%2F59e4eba4-09f3-44aa-8d73-7445cb1d7ad8.png</url>
      <title>Forem: terryncew</title>
      <link>https://forem.com/terryncew</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/terryncew"/>
    <language>en</language>
    <item>
      <title>Small receipts. Big accountability. A tiny JSON that makes AI runs legible.</title>
      <dc:creator>terryncew</dc:creator>
      <pubDate>Thu, 02 Oct 2025 16:59:40 +0000</pubDate>
      <link>https://forem.com/terryncew/small-receipts-big-accountability-a-tiny-json-that-makes-ai-runs-legible-2dgj</link>
      <guid>https://forem.com/terryncew/small-receipts-big-accountability-a-tiny-json-that-makes-ai-runs-legible-2dgj</guid>
      <description>&lt;p&gt;Most AI failures aren’t mysterious—they’re unobserved. We log answers, not paths. I’m shipping a tiny “receipt” per run (just JSON) that carries two cheap signals and a few guards so you can diff, audit, and keep the path, not just the output.&lt;/p&gt;

&lt;p&gt;What’s in the receipt&lt;br&gt;
• κ (kappa): stress when density outruns structure&lt;br&gt;
• Δhol: stateful drift across runs&lt;br&gt;
• Guard context: unsupported-claim ratio (UCR), cycles, unresolved contradictions&lt;br&gt;
• A calibrated green/amber/red with “why” and “try next”&lt;/p&gt;

&lt;p&gt;Why it’s practical&lt;br&gt;
• Stdlib-only; no vendor lock-in&lt;br&gt;
• CI-friendly; easy to version, sign, and diff&lt;br&gt;
• Signals, not proofs; it’s triage that tells you where to look&lt;/p&gt;

&lt;p&gt;Does it work?&lt;br&gt;
On a small, 24-case labeled slice: recall ≈ 0.77, precision ≈ 0.56 using percentile thresholds. It’s not a benchmark—it’s enough signal to route human attention.&lt;/p&gt;

&lt;p&gt;Try it&lt;br&gt;
• COLE (receipt + guard + page): &lt;a href="https://github.com/terryncew/COLE-Coherence-Layer-Engine-" rel="noopener noreferrer"&gt;https://github.com/terryncew/COLE-Coherence-Layer-Engine-&lt;/a&gt;&lt;br&gt;
• OpenLine Core (wire + example frame): &lt;a href="https://github.com/terryncew/openline-core" rel="noopener noreferrer"&gt;https://github.com/terryncew/openline-core&lt;/a&gt;&lt;br&gt;
• Start with TESTERS.md (5 minutes). If anything breaks, open an issue with the step and error.&lt;/p&gt;

&lt;p&gt;Ask&lt;br&gt;
Kick the tires on 20 of your evals. Tell me where κ/Δhol/UCR help, where they’re noisy, and what you’d add to the guard policy. &lt;/p&gt;

&lt;p&gt;License: MIT (code/spec). Your data remains yours.&lt;/p&gt;

</description>
      <category>devops</category>
      <category>opensource</category>
      <category>machinelearning</category>
      <category>ai</category>
    </item>
    <item>
      <title>Open Line Protocol — a geometry-first wire for AI agents (MIT)</title>
      <dc:creator>terryncew</dc:creator>
      <pubDate>Tue, 16 Sep 2025 02:13:53 +0000</pubDate>
      <link>https://forem.com/terryncew/open-line-protocol-a-geometry-first-wire-for-ai-agents-mit-268m</link>
      <guid>https://forem.com/terryncew/open-line-protocol-a-geometry-first-wire-for-ai-agents-mit-268m</guid>
      <description>&lt;p&gt;I open-sourced &lt;strong&gt;Open Line Protocol (OLP)&lt;/strong&gt; so agents send &lt;strong&gt;small graphs + telemetry&lt;/strong&gt;, not paragraphs.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What it is&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Frozen wire &lt;strong&gt;v0.1&lt;/strong&gt; (typed schema)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Digest&lt;/strong&gt;: &lt;code&gt;b0, cycle_plus, x_frontier, s_over_c, depth&lt;/code&gt; + &lt;code&gt;Δ_hol&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Guards&lt;/strong&gt;: block self-licking loops, silent deletions, order-debt spikes&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Receipts&lt;/strong&gt;: JSON evidence validated in CI (portable, auditable)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Try it&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Repo: &lt;a href="https://github.com/terryncew/openline-core" rel="noopener noreferrer"&gt;https://github.com/terryncew/openline-core&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Live hub (receipts): &lt;a href="https://terryncew.github.io/openline-hub/" rel="noopener noreferrer"&gt;https://terryncew.github.io/openline-hub/&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Why it matters&lt;/strong&gt;&lt;br&gt;
Agents coordinate better when plans are &lt;strong&gt;auditable&lt;/strong&gt; and &lt;strong&gt;order-safe&lt;/strong&gt;. OLP is the frozen wire; receipts are the proof.&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>ai</category>
      <category>agents</category>
      <category>protocol</category>
    </item>
  </channel>
</rss>
