<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel>
    <title>Intent Record AB news</title>
    <link>https://intentrecord.xyz/news</link>
    <description>Releases, publications and milestones from Intent Record AB.</description>
    <language>en</language>
    <item>
      <title>A plain-language guide to the EU AI Act, free to read</title>
      <link>https://intentrecord.xyz/news#eu-ai-act-guide</link>
      <guid isPermaLink="false">https://intentrecord.xyz/news#eu-ai-act-guide</guid>
      <description>Twenty-six chapters covering the EU AI Act in plain language: why the law exists, how to work out whether you are a provider or a deployer, what the risk tiers actually mean, and what each key article requires of you.
          It is written for the people who have to act on the regulation rather th</description>
      <pubDate>2026-07-20</pubDate>
    </item>
    <item>
      <title>irp-capture 0.8.0 adds provenance lenses to the decision graph</title>
      <link>https://intentrecord.xyz/news#irp-0-8-0</link>
      <guid isPermaLink="false">https://intentrecord.xyz/news#irp-0-8-0</guid>
      <description>A decision ledger tells you what was decided. It does not tell you which decisions everything else is resting on. Version 0.8.0 adds three lenses over the decision graph that answer that directly: foundations ranks what the recorded reasoning rests on, lineage shows why a particular decision exists,</description>
      <pubDate>2026-07-17</pubDate>
    </item>
    <item>
      <title>IRP Evidence API: proving a record existed, without us holding your data</title>
      <link>https://intentrecord.xyz/news#irp-evidence-api</link>
      <guid isPermaLink="false">https://intentrecord.xyz/news#irp-evidence-api</guid>
      <description>A record kept on your own machine has an honest limitation: you could change it and recompute its hashes, so it cannot prove on its own when it was written. That gap matters if the record is ever meant to serve as evidence.
          The IRP Evidence API closes it with an external RFC 3161 timestamp</description>
      <pubDate>2026-06-30</pubDate>
    </item>
</channel></rss>
