<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ai-Act on Step Into Dev</title><link>https://stepinto.dev/tags/ai-act/</link><description>Recent content in Ai-Act on Step Into Dev</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Fri, 06 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://stepinto.dev/tags/ai-act/index.xml" rel="self" type="application/rss+xml"/><item><title>Reading the AI Act One Article at a Time</title><link>https://stepinto.dev/posts/ai-law-on-fridays/</link><pubDate>Fri, 06 Nov 2026 00:00:00 +0000</pubDate><guid>https://stepinto.dev/posts/ai-law-on-fridays/</guid><description>&lt;p&gt;The two posts I wrote in February about building AI platforms under European law, &lt;a href="https://stepinto.dev/posts/compliance-as-code-two-europes/"&gt;compliance-as-code&lt;/a&gt; and &lt;a href="https://stepinto.dev/posts/fine-tuning-under-european-law/"&gt;fine-tuning&lt;/a&gt;, stop at the architecture. They say where the compliance layer sits and not much about what goes in it. The AI Act is written in clauses, and each clause ends up as something specific in the code: a field in a log, a state in the UI, a test in CI. Most of what I read about the Act is written for lawyers or for the board, and very little of it gets as far as a pull request.&lt;/p&gt;</description></item></channel></rss>