<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Compliance on SREKubeCraft | Nikos Nikolakakis</title><link>https://srekubecraft.io/tags/compliance/</link><description>Recent content in Compliance on SREKubeCraft | Nikos Nikolakakis</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 14 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://srekubecraft.io/tags/compliance/index.xml" rel="self" type="application/rss+xml"/><item><title>Sphragis - The EU AI Act Compliance Gateway You Actually Control</title><link>https://srekubecraft.io/posts/introducing-sphragis-eu-ai-act-compliance-gateway/</link><pubDate>Sun, 14 Jun 2026 00:00:00 +0000</pubDate><guid>https://srekubecraft.io/posts/introducing-sphragis-eu-ai-act-compliance-gateway/</guid><description>&lt;p&gt;It is 02:00 and you are on call. Checkout is throwing 500s. You do not tail logs by hand anymore, you ask Claude Code, and it calls your Datadog MCP server, pulls the failing traces and the surrounding log lines, and reasons over them to find the bad deploy. One of those log lines is a request payload with a real customer&amp;rsquo;s email and IBAN in it, because production telemetry carries that. The MCP handed it to the model as context. You never saw it. Nobody &lt;em&gt;decided&lt;/em&gt; to send that customer&amp;rsquo;s bank details to a US provider. The agent fetched it and shipped it upstream, the way it does on every investigation.&lt;/p&gt;</description></item></channel></rss>