<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AIOC on Thinx-Tank</title><link>https://blog.thinxai.net/tags/aioc/</link><description>Recent content in AIOC on Thinx-Tank</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 14 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.thinxai.net/tags/aioc/index.xml" rel="self" type="application/rss+xml"/><item><title>Delegation Is Not Inheritance</title><link>https://blog.thinxai.net/posts/delegation-is-not-inheritance/</link><pubDate>Wed, 14 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/delegation-is-not-inheritance/</guid><description>&lt;p&gt;On October 8, at Gemini at Work 2026, Google introduced a single Gemini agent for work. Most of the coverage went to the front door: one agent across Workspace, Microsoft 365, and Slack, with persistent coworker agents that hold their own email address, storage, and Workspace account. The line I keep coming back to is smaller. Per &lt;a href="https://futurumgroup.com/insights/google-collapses-enterprise-ai-into-a-single-gemini-agent-at-gemini-at-work-2026/"&gt;Futurum&amp;rsquo;s report on the announcement&lt;/a&gt;, the agent &amp;ldquo;spins up temporary sub-agents for individual jobs.&amp;rdquo;&lt;/p&gt;</description></item><item><title>AI Operations Center, a Human Analogy</title><link>https://blog.thinxai.net/posts/ai-operations-center-human-analogy/</link><pubDate>Sun, 04 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/ai-operations-center-human-analogy/</guid><description>&lt;p&gt;There is a noticeable lack of enterprise strategy and architecture for AI Operations. Everyone is deploying agents; almost nobody has built the operating model to run them. The AI Operations Center is my answer: a governed environment for people and AI to access, operate, and manage the AI ecosystem. Centralized tooling, with people retaining defined authority, accountability, and control.&lt;/p&gt;&#10;&lt;p&gt;This is the human-readable companion to the &lt;a href="https://blog.thinxai.net/posts/agentic-execution-control-plane/"&gt;Agentic Execution Control Plane&lt;/a&gt; architecture. Five functions, one human analogy each:&lt;/p&gt;</description></item><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><item><title>Git Is the Control Plane</title><link>https://blog.thinxai.net/posts/git-is-the-control-plane/</link><pubDate>Wed, 30 Sep 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/git-is-the-control-plane/</guid><description>&lt;p&gt;Earlier this month &lt;a href="https://medium.com/google-cloud/gitops-for-ai-agents-on-google-cloud-argocd-config-sync-and-gke-03fdad8b0716"&gt;Neel Shah wrote up his pattern&lt;/a&gt; for running AI agents on GKE with GitOps. The core of the piece is a repo layout where an agent&amp;rsquo;s system prompt, tool allowlist, model binding, and guardrail config all live as versioned files, and a reconciler (ArgoCD or Config Sync) continuously forces the live cluster to match. A prompt tweak is a one-line diff. Rollback is a git revert. A policy engine blocks a dangerous tool grant before it lands.&lt;/p&gt;</description></item></channel></rss>