<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>FaultKey · CausalLayer</title>
    <link>https://faultkey.com/</link>
    <atom:link href="https://faultkey.com/feed.xml" rel="self" type="application/rss+xml"/>
    <description>Deterministic AI liability attribution — every AI incident becomes a signed, Bitcoin-anchored CausalCertificateV1 receipt.</description>
    <language>en-au</language>
    <copyright>Apache-2.0</copyright>
    <pubDate>Sat, 17 May 2026 00:00:00 +1000</pubDate>
    <lastBuildDate>Sat, 17 May 2026 00:00:00 +1000</lastBuildDate>
    <generator>FaultKey static-site pipeline</generator>
    <docs>https://www.rssboard.org/rss-specification</docs>
    <ttl>60</ttl>
    <image>
      <url>https://faultkey.com/icon-400.png</url>
      <title>FaultKey · CausalLayer</title>
      <link>https://faultkey.com/</link>
    </image>

    <item>
      <title>v0.2.1 release: deterministic AI-liability MCP server, public test vectors, Bitcoin anchor</title>
      <link>https://github.com/smq9sn5jck-coder/causallayer-mcp/releases/tag/v0.2.1</link>
      <guid isPermaLink="true">https://github.com/smq9sn5jck-coder/causallayer-mcp/releases/tag/v0.2.1</guid>
      <pubDate>Sat, 17 May 2026 02:00:00 +1000</pubDate>
      <description>FaultKey · CausalLayer v0.2.1 ships byte-identical test vectors, a SHA256SUMS file, and a public source tarball. The MCP endpoint at https://mcp.faultkey.com/mcp now exposes four production tools.</description>
    </item>

    <item>
      <title>How CausalCertificateV1 maps to APRA CPS 230 paragraph 36(b)</title>
      <link>https://faultkey.com/blog/apra-cps-230</link>
      <guid isPermaLink="true">https://faultkey.com/blog/apra-cps-230</guid>
      <pubDate>Sat, 17 May 2026 03:00:00 +1000</pubDate>
      <description>APRA's prudential standard CPS 230 requires APRA-regulated entities to maintain documented evidence of operational events. CausalCertificateV1 receipts produce that evidence in cryptographically tamper-evident form.</description>
    </item>

    <item>
      <title>EU AI Act Article 12 record-keeping with deterministic receipts</title>
      <link>https://faultkey.com/blog/eu-ai-act-art-12</link>
      <guid isPermaLink="true">https://faultkey.com/blog/eu-ai-act-art-12</guid>
      <pubDate>Sat, 17 May 2026 04:00:00 +1000</pubDate>
      <description>Article 12 of the EU AI Act requires high-risk AI systems to keep automatic logs throughout their lifecycle. We show how CausalCertificateV1 receipts can serve as that log surface, with the additional property of being externally verifiable.</description>
    </item>

    <item>
      <title>NIST AI RMF MEASURE 2.7: documenting AI incidents with byte-identical receipts</title>
      <link>https://faultkey.com/blog/nist-ai-rmf</link>
      <guid isPermaLink="true">https://faultkey.com/blog/nist-ai-rmf</guid>
      <pubDate>Sat, 17 May 2026 05:00:00 +1000</pubDate>
      <description>The MEASURE function of the NIST AI RMF requires that AI incidents be documented in a way that supports later assessment. Deterministic receipts solve the "is the documentation itself reproducible" problem in a single primitive.</description>
    </item>

    <item>
      <title>ISO/IEC 42001 Clause 7.5 documented information via tamper-evident receipts</title>
      <link>https://faultkey.com/blog/iso-iec-42001</link>
      <guid isPermaLink="true">https://faultkey.com/blog/iso-iec-42001</guid>
      <pubDate>Sat, 17 May 2026 06:00:00 +1000</pubDate>
      <description>ISO/IEC 42001 Clause 7.5 requires the AI management system to maintain documented information. We show how CausalCertificateV1 satisfies the "controlled documented information" requirements for both retention and protection.</description>
    </item>
  </channel>
</rss>
