<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Signing on CodeInstances.com</title>
    <link>https://codeinstances.com/tags/signing/</link>
    <description>Recent content in Signing on CodeInstances.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://codeinstances.com/tags/signing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CodeInstances Signs Runs, So You Can Check Who Kept One and That Nothing Changed</title>
      <link>https://codeinstances.com/codeinstances-signs-runs-so-you-can-check-who-kept-one-and-that-nothing-changed/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://codeinstances.com/codeinstances-signs-runs-so-you-can-check-who-kept-one-and-that-nothing-changed/</guid>
      <description>&lt;p&gt;CodeInstances v0.7.0 adds signing. Every instance already carried an id, the SHA-256 of its contents, so &lt;code&gt;verify&lt;/code&gt; could tell you a file had been edited. What it couldn&amp;rsquo;t tell you is who made the file in the first place. Anyone can change a run and write a fresh id. Now a run can carry a signature, and &lt;code&gt;verify -trust&lt;/code&gt; checks it against keys you&amp;rsquo;ve decided to trust.&lt;/p&gt;&#xA;&lt;p&gt;That matters when a run is evidence. A CI job says the tests passed, an AI agent says what it did and what came back, a bug report says this is what happened. With a signed instance the person reading it doesn&amp;rsquo;t have to take the file&amp;rsquo;s word for it. They check the key.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
