<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mlops on t0ul</title><link>https://t0ul.com/tags/mlops/</link><description>Recent content in Mlops on t0ul</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 18 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://t0ul.com/tags/mlops/index.xml" rel="self" type="application/rss+xml"/><item><title>Data and privacy governance</title><link>https://t0ul.com/blog/data-and-privacy-governance/</link><pubDate>Tue, 18 Aug 2026 00:00:00 +0000</pubDate><guid>https://t0ul.com/blog/data-and-privacy-governance/</guid><description>&lt;p&gt;&lt;em&gt;Part of my &lt;a href="https://t0ul.com/blog/the-plan/"&gt;AI Security Engineering&lt;/a&gt; series, a local email-to-calendar agent I build, then attack, then harden. If you have not set up the lab yet, start with &lt;a href="https://t0ul.com/blog/setting-up-the-lab/"&gt;Set up your lab&lt;/a&gt;. The lessons are &lt;a href="https://github.com/t0ul/ai-security-engineering"&gt;on GitHub&lt;/a&gt;, and the agent itself lives at &lt;a href="https://github.com/t0ul/emaildrop"&gt;t0ul/emaildrop&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="two-gates-on-trust"&gt;Two gates on trust&lt;/h2&gt;
&lt;p&gt;Governance so far has been about the agent&amp;rsquo;s operation: who may change it, how to stop it. This post is about its supply chain, the two moments where something from outside becomes something the agent relies on. Data comes in, and a change goes out. Each is a gate, and a gate that is not enforced is a door.&lt;/p&gt;</description></item></channel></rss>