<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Socium Analysis</title>
    <link>https://socium.build/analysis/</link>
    <atom:link href="https://socium.build/analysis/rss.xml" rel="self" type="application/rss+xml" />
    <description>Derivations and failure analyses from building Socium.</description>
    <language>en-us</language>
    <item>
      <title>Chain of custody for requirements</title>
      <link>https://socium.build/analysis/chain-of-custody-for-requirements/</link>
      <guid isPermaLink="true">https://socium.build/analysis/chain-of-custody-for-requirements/</guid>
      <description>A design declared three authorities, the requirements restatement described one, and every artifact after that was faithful to the restatement. Every check passed. The requirement was not tampered with, it was dropped at a transfer nobody was watching.</description>
      <pubDate>Wed, 29 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Presence is not a relation</title>
      <link>https://socium.build/analysis/presence-is-not-a-relation/</link>
      <guid isPermaLink="true">https://socium.build/analysis/presence-is-not-a-relation/</guid>
      <description>A check's name states a claim, its body is a predicate, and nothing in the toolchain compares the two. Six of nine checks in one control asserted relations with a substring search, and one of them was reading a module comment.</description>
      <pubDate>Wed, 29 Jul 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
