<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sovereignty on Thinx-Tank</title><link>https://blog.thinxai.net/tags/sovereignty/</link><description>Recent content in Sovereignty on Thinx-Tank</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 04 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.thinxai.net/tags/sovereignty/index.xml" rel="self" type="application/rss+xml"/><item><title>Sovereignty Is a Routing Problem</title><link>https://blog.thinxai.net/posts/sovereignty-is-a-routing-problem/</link><pubDate>Sun, 04 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/sovereignty-is-a-routing-problem/</guid><description>&lt;p&gt;Every enterprise AI conversation hits the same wall: the data cannot leave, but the best models live outside. The two usual answers are both wrong. Banning frontier models leaves capability on the table. Allowing them by default builds an IP pipeline into someone else&amp;rsquo;s training run.&lt;/p&gt;&#10;&lt;p&gt;Data sovereignty is not a place. It is a routing decision. Every request gets classified, and the classification picks the model. The router is the policy enforcement point.&lt;/p&gt;</description></item></channel></rss>