<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Governance on Thinx-Tank</title><link>https://blog.thinxai.net/tags/governance/</link><description>Recent content in Governance on Thinx-Tank</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 17 Nov 2026 07:22:26 -0600</lastBuildDate><atom:link href="https://blog.thinxai.net/tags/governance/index.xml" rel="self" type="application/rss+xml"/><item><title>The State of the Standards for AI</title><link>https://blog.thinxai.net/posts/state-of-the-standards-q4-2026/</link><pubDate>Tue, 17 Nov 2026 07:22:26 -0600</pubDate><guid>https://blog.thinxai.net/posts/state-of-the-standards-q4-2026/</guid><description>&lt;p&gt;This is the baseline. I plan to revisit the state of the AI standards once a quarter and report only what changed: what got published, what got cited, what slipped, and what got replaced. A baseline has to be plain about what exists today, or the diff next quarter means nothing.&lt;/p&gt;&#10;&lt;p&gt;Three layers matter for my work. The framework layer tells an organization how to govern AI. The conformity layer tells a provider how to prove it meets a law. The agent layer would tell an operator how an agent should identify itself, take authorization, and leave evidence at run time. The first layer is settled. The second is one standard deep. The third is still draft work.&lt;/p&gt;</description></item><item><title>A Taxonomy Is Not a Governance</title><link>https://blog.thinxai.net/posts/taxonomy-is-not-governance/</link><pubDate>Mon, 16 Nov 2026 19:20:00 -0600</pubDate><guid>https://blog.thinxai.net/posts/taxonomy-is-not-governance/</guid><description>&lt;p&gt;McKinsey published a guide for banking CIOs in October, &lt;a href="https://www.mckinsey.com/capabilities/tech-and-ai/our-insights/the-rise-of-the-agentic-coworker-a-banking-cios-guide-to-the-next-wave-of-ai"&gt;The Rise of the Agentic Coworker&lt;/a&gt;, and one of its five foundations is memory. Their sentence is worth quoting in full: three kinds of memory keep coworkers from treating every case as if it were the first. Episodic memory preserves what happened before: prior actions, exceptions, and outcomes for a client. Procedural memory encodes how the work should be done, including where authority limits apply. Semantic memory grounds the coworker in the bank&amp;rsquo;s own vocabulary: product codes, policy definitions, risk appetite, and regulatory citations. A write-back loop records human corrections, so the next coworker inherits the case, the method, and the language.&lt;/p&gt;</description></item><item><title>A Model Is Not a Model</title><link>https://blog.thinxai.net/posts/a-model-is-not-a-model/</link><pubDate>Mon, 16 Nov 2026 07:21:52 -0600</pubDate><guid>https://blog.thinxai.net/posts/a-model-is-not-a-model/</guid><description>&lt;p&gt;I hear the same sentence in planning meetings, said as if it settles the question. A model is a model. If the hosted price bothers us, we will run an open weight model ourselves and the problem goes away.&lt;/p&gt;&#10;&lt;p&gt;It does not. Not yet. That last word matters, and I will come back to it. First I need to name the two errors packed into the premise, because each one costs money on its own.&lt;/p&gt;</description></item><item><title>Production Is Not a Result</title><link>https://blog.thinxai.net/posts/production-is-not-a-result/</link><pubDate>Thu, 12 Nov 2026 07:20:00 -0600</pubDate><guid>https://blog.thinxai.net/posts/production-is-not-a-result/</guid><description>&lt;p&gt;Genpact published its &lt;em&gt;Autonomy in Practice&lt;/em&gt; report today, built on a survey of more than 2,000 senior executives at companies with revenues from $1 billion to over $50 billion, across 17 industries and 14 business functions. The headline numbers in &lt;a href="https://www.prnewswire.com/news-releases/79-of-enterprises-report-ai-agents-in-production-but-only-15-have-fully-tied-ai-investment-to-pl-outcomes-302937385.html"&gt;Genpact&amp;rsquo;s release&lt;/a&gt; deserve to be read as a set, not separately. 79 percent of enterprises have AI agents in production. Just 20 percent use them broadly and consistently across functions. Only 15 percent have fully tied AI investment to P&amp;amp;L outcomes. And on average, just 49 percent of AI initiatives funded in the past 24 months delivered the value expected.&lt;/p&gt;</description></item><item><title>Route by Outcome, Not by Token</title><link>https://blog.thinxai.net/posts/route-by-outcome-not-by-token/</link><pubDate>Tue, 10 Nov 2026 07:20:00 -0600</pubDate><guid>https://blog.thinxai.net/posts/route-by-outcome-not-by-token/</guid><description>&lt;p&gt;Most organizations route model traffic by habit. One default model handles everything, or the biggest model handles everything because nobody wants to be blamed for a weak answer. Then the bill arrives, or the failure rate does, and both look like surprises. They are not surprises. They are the predictable result of a routing decision nobody wrote down.&lt;/p&gt;&#10;&lt;p&gt;Routing is not a technical setting tucked inside a prompt. It is an economic decision and a governance decision. The model a task runs on decides what the work costs, what quality comes back, and how much rework I buy afterward. If that decision matters, it belongs on the record.&lt;/p&gt;</description></item><item><title>How Companies Integrate Their Values into the Broader AI Ecosystem</title><link>https://blog.thinxai.net/posts/values-into-the-ai-ecosystem/</link><pubDate>Mon, 09 Nov 2026 07:49:00 -0600</pubDate><guid>https://blog.thinxai.net/posts/values-into-the-ai-ecosystem/</guid><description>&lt;p&gt;Most of the AI ecosystem is general-purpose on purpose. Foundation models, agent frameworks, MCP servers, tool catalogs, and most vendor control planes are built to be reused by anyone. They optimize for capability, interoperability, and scale. What they do not carry, by default, is any particular company&amp;rsquo;s values: its risk posture, its approval culture, its attribution rules, its authority model.&lt;/p&gt;&#10;&lt;p&gt;Deploy agents into that ecosystem without binding those things in, and the agents inherit defaults: the model&amp;rsquo;s, the framework&amp;rsquo;s, the platform&amp;rsquo;s, or whatever the prompt of the moment happens to say. Those defaults are rarely the organization&amp;rsquo;s own. The fix is a governance layer under the agents: a meta-harness with constitutional surfaces an agent cannot rewrite, and a kernel that decides what actually takes effect.&lt;/p&gt;</description></item><item><title>Autonomy Is Earned Per Action, Not Granted Per Agent</title><link>https://blog.thinxai.net/posts/autonomy-is-earned-per-action/</link><pubDate>Thu, 05 Nov 2026 07:20:00 -0600</pubDate><guid>https://blog.thinxai.net/posts/autonomy-is-earned-per-action/</guid><description>&lt;p&gt;The fleets are already here. &lt;a href="https://www.globenewswire.com/news-release/2026/11/04/3395406/0/en/komodor-survey-finds-more-than-50-of-engineering-organizations-face-control-and-governance-issues-as-they-scale-agentic-operations.html"&gt;Komodor&amp;rsquo;s 2026 Agentic Operations Survey&lt;/a&gt;, released November 4 from responses by 1,000 engineering and technology leaders, found that nearly 84% run fleets of 10 or more operational agents. The leading uses are production work: self-remediation and AI SRE at 44.2%, incident investigation at 43.2%.&lt;/p&gt;&#10;&lt;p&gt;The control picture has not kept up. Building safe guardrails was the most cited challenge at 53.6%, followed by governance and security at 50.4%, and 42.7% named insufficient visibility into agent permissions. And 75.7% hold autonomy back with restrictions: agents limited to read-only tasks, human approval required for changes, or automated actions confined to noncritical workloads.&lt;/p&gt;</description></item><item><title>The MxM Fabric Defined</title><link>https://blog.thinxai.net/posts/the-mxm-fabric-defined/</link><pubDate>Wed, 04 Nov 2026 11:35:00 -0600</pubDate><guid>https://blog.thinxai.net/posts/the-mxm-fabric-defined/</guid><description>&lt;p&gt;In &lt;a href="https://blog.thinxai.net/posts/personal-agents-workers-and-the-fabric/"&gt;Personal Agents, Workers, and the Fabric That Governs Them&lt;/a&gt;, published earlier today, I made the argument: a personal agent faces the human, workers do the delegated work, and what governs both cannot live in a model&amp;rsquo;s disposition. It has to live in a fabric, where behavior is written down, versioned, and checkable. This post defines that fabric.&lt;/p&gt;&#10;&lt;p&gt;MxM is a multi-mode meta-harness. It defines, enforces, and proves how agents behave, what they can do, and how they are held accountable, across models, vendors, runtimes, and organizations. The short version fits in four phrases: define once, bootstrap everywhere, govern at scale, endure through change. Everything below is those four phrases made concrete.&lt;/p&gt;</description></item><item><title>Personal Agents, Workers, and the Fabric That Governs Them</title><link>https://blog.thinxai.net/posts/personal-agents-workers-and-the-fabric/</link><pubDate>Wed, 04 Nov 2026 04:52:00 -0600</pubDate><guid>https://blog.thinxai.net/posts/personal-agents-workers-and-the-fabric/</guid><description>&lt;p&gt;There is a distinction worth keeping as synthetic intelligence moves into daily work. A personal agent is the agent that interacts with the human. Workers are the agents that personal agent may engage: an executor in its own lane, a peer reached through a bridge, a subagent spawned for a single task. The human directs one agent. Engaging the rest is that agent&amp;rsquo;s job.&lt;/p&gt;&#10;&lt;p&gt;The distinction raises a question immediately. When the personal agent dispatches a worker, what governs the worker? The answer is precise. The worker does not adopt the personal agent&amp;rsquo;s behavior characteristics as its own constitution. It takes on no standing posture, no memory of the relationship, no identity. But in the work it is governed by those characteristics completely. The agent&amp;rsquo;s discipline binds the delegation itself, because an agent may not send a worker to do what its own morals would bar it from doing directly. The brief carries the rules for the task, the output counts as the agent&amp;rsquo;s own output, and review on the return path is where breaches are caught. Accountability never leaves the agent that dispatched the work. Authority flows down. Accountability flows up.&lt;/p&gt;</description></item><item><title>Govern the Door, Not the Agent You Do Not Own</title><link>https://blog.thinxai.net/posts/govern-the-door/</link><pubDate>Tue, 03 Nov 2026 07:22:00 -0600</pubDate><guid>https://blog.thinxai.net/posts/govern-the-door/</guid><description>&lt;p&gt;Most of my recent posts have been about agents inside the enterprise: the ones you buy, build, or approve. This one is about the agents you did none of those things for. They belong to your customers. You did not select them, you cannot patch them, and you will never see their release notes. They arrive at your portal with your customer&amp;rsquo;s password, and from your authentication logs they look exactly like your customer.&lt;/p&gt;</description></item><item><title>The Agent Wore a Contractor's Login</title><link>https://blog.thinxai.net/posts/agent-wore-a-contractors-login/</link><pubDate>Mon, 02 Nov 2026 07:20:00 -0600</pubDate><guid>https://blog.thinxai.net/posts/agent-wore-a-contractors-login/</guid><description>&lt;p&gt;On October 29, &lt;a href="https://www.cdomagazine.tech/us-federal-news-bureau/defense-contractor-gave-personal-ai-agent-access-to-pentagon-system"&gt;CDO Magazine summarized a WIRED investigation&lt;/a&gt; that every enterprise IT shop should read slowly. According to WIRED&amp;rsquo;s sources, an Accenture contractor connected a personal Claude Code account to a production system on NIPRNet, the Defense Department network for unclassified work. The system held controlled unclassified information and served multiple intelligence agencies. To get help writing code and standing up cloud servers, the contractor reportedly handed the agent his own login credentials.&lt;/p&gt;</description></item><item><title>Give the Agent a Role, Not Your Login</title><link>https://blog.thinxai.net/posts/give-the-agent-a-role/</link><pubDate>Sat, 31 Oct 2026 07:20:00 -0500</pubDate><guid>https://blog.thinxai.net/posts/give-the-agent-a-role/</guid><description>&lt;p&gt;In &lt;a href="https://blog.thinxai.net/posts/browser-is-an-agent-surface/"&gt;yesterday&amp;rsquo;s post&lt;/a&gt; I worked through a design problem that Island&amp;rsquo;s governed browser exposed without naming. The agent does its work inside a person&amp;rsquo;s session, under that person&amp;rsquo;s identity, with that person&amp;rsquo;s full reach. The vendor can split the record afterward and show which actions the person took and which the agent took. That helps the investigation. It does not fix the grant. The agent still started the day holding everything the person holds.&lt;/p&gt;</description></item><item><title>The Browser Is an Agent Surface Now</title><link>https://blog.thinxai.net/posts/browser-is-an-agent-surface/</link><pubDate>Fri, 30 Oct 2026 07:21:00 -0500</pubDate><guid>https://blog.thinxai.net/posts/browser-is-an-agent-surface/</guid><description>&lt;p&gt;Most enterprise work still happens in a browser. The CRM, the ERP, the HR system, the invoice queue: all of them are web applications behind a login form. An agent that cannot use a browser cannot do that work. An agent that can use a browser, on a consumer setup with saved passwords and a person&amp;rsquo;s full session, can do far more than that work.&lt;/p&gt;&#10;&lt;p&gt;Island made that problem a product category on October 29. In &lt;a href="https://www.globenewswire.com/news-release/2026/10/29/3391421/0/en/island-brings-the-enterprise-browser-to-ai-agents.html"&gt;Island&amp;rsquo;s announcement of its Enterprise Browser for Agents&lt;/a&gt;, the company describes a browser built for agents to access, read, and act on SaaS applications, internal applications, and public websites under the same enterprise controls and policies the company already applies to people. Sales agents update CRM records after calls. HR agents help onboard new hires. Finance agents process invoices. Island&amp;rsquo;s stated examples are ordinary back-office work, which is the point. The browser is not a side channel for agents. For a large share of enterprise tasks, it is the workplace.&lt;/p&gt;</description></item><item><title>An Alliance Is Not a Control Plane</title><link>https://blog.thinxai.net/posts/alliance-is-not-a-control-plane/</link><pubDate>Thu, 29 Oct 2026 07:23:00 -0500</pubDate><guid>https://blog.thinxai.net/posts/alliance-is-not-a-control-plane/</guid><description>&lt;p&gt;On October 28, ServiceNow announced the Control Tower Alliance, a partner program built around its Super Intelligence Control Tower. &lt;a href="https://www.unite.ai/kong-becomes-founding-member-of-servicenow-control-tower-alliance/"&gt;Unite.AI&amp;rsquo;s summary of the announcement&lt;/a&gt; lists eleven founding members: Anthropic, Amazon Web Services, Cisco, HiddenLayer, Kong, NVIDIA, Okta, OpenAI, Stripe, WitnessAI, and Zenity. ServiceNow describes the tower as a centralized control plane to discover, secure, govern, observe, and measure enterprise AI. Partners build solutions that run on the tower, submit them to ServiceNow qualification and certification against shared standards for agent identity and safety guardrails, and sell jointly.&lt;/p&gt;</description></item><item><title>Govern the Agents You Did Not Build</title><link>https://blog.thinxai.net/posts/govern-the-agents-you-did-not-build/</link><pubDate>Tue, 27 Oct 2026 07:21:00 -0500</pubDate><guid>https://blog.thinxai.net/posts/govern-the-agents-you-did-not-build/</guid><description>&lt;p&gt;IBM made the most honest admission in agent governance today, and it came inside a product announcement. At TechXchange 2026 in Atlanta, &lt;a href="https://www.morningstar.com/news/pr-newswire/20261027ny81742/ibm-introduces-identity-and-control-for-ai-agents-securing-frontier-intelligence-for-the-enterprise"&gt;IBM announced&lt;/a&gt; that watsonx Orchestrate will discover, contain, and evaluate agents built on other vendors&amp;rsquo; platforms, and that HashiCorp Vault will issue those agents governed identities and short-lived credentials. In &lt;a href="https://www.ibm.com/new/announcements/ibm-watsonx-orchestrate-advances-enterprise-ai-agent-management-with-new-capabilities-at-techxchange-2026"&gt;IBM&amp;rsquo;s own write-up&lt;/a&gt;, the pitch is explicit: manage agents &amp;ldquo;regardless of where those agents were built or run.&amp;rdquo;&lt;/p&gt;&#10;&lt;p&gt;That is the right problem. It is not the problem most control planes were built to solve. A control plane that only governs agents built on its own platform governs the demo estate, not the real one.&lt;/p&gt;</description></item><item><title>Approval Is Not a Control</title><link>https://blog.thinxai.net/posts/approval-is-not-a-control/</link><pubDate>Mon, 26 Oct 2026 07:22:00 -0500</pubDate><guid>https://blog.thinxai.net/posts/approval-is-not-a-control/</guid><description>&lt;p&gt;&lt;a href="https://docs.aws.amazon.com/wellarchitected/latest/agentic-ai-lens/agentsec04-bp02.html"&gt;AWS&amp;rsquo;s Well-Architected Agentic AI Lens&lt;/a&gt; opens its guidance on human review with a sentence worth reading twice: &amp;ldquo;Routing every agent action through human review produces rubber-stamp approvals.&amp;rdquo; That is not an outside critic. That is a hyperscaler telling architects, in its own design guidance, that the default control decays into its own absence. The same page lists insufficient reviewer context as an anti-pattern that turns review into a formality.&lt;/p&gt;&#10;&lt;p&gt;Most shops still treat the approval click as the control. Put a person in front of the action, log the name and the timestamp, and call the deployment governed. The log is real. The review often is not.&lt;/p&gt;</description></item><item><title>Redesign the Job Around the Agent</title><link>https://blog.thinxai.net/posts/redesign-the-job-around-the-agent/</link><pubDate>Sun, 25 Oct 2026 07:22:00 -0500</pubDate><guid>https://blog.thinxai.net/posts/redesign-the-job-around-the-agent/</guid><description>&lt;p&gt;Four percent. That is the share of CIOs who have a plan to redesign roles for a workforce made of people and agents working together.&lt;/p&gt;&#10;&lt;p&gt;&lt;a href="https://www.ciodive.com/news/gartner-survey-CIOs-workforce-revamp/833405/"&gt;Gartner surveyed 2,002 CIOs and technology executives for its 2027 CIO and Technology Executive Agenda, and CIO Dive reported the workforce findings on October 19&lt;/a&gt;. Only 4 percent reported plans in place to revamp roles with a human and agent workforce in mind. The firms that do have such plans are 2.4 times more likely to be top performers with AI, with CEOs who report value from it. The rest of the picture explains the gap: 58 percent of leaders face increased demand to show cost improvements from prior AI spending, and only 13 percent report significant or transformational value from AI so far. Cost pressure is immediate. Role redesign is not. So the redesign loses.&lt;/p&gt;</description></item><item><title>Egress Is the Boundary</title><link>https://blog.thinxai.net/posts/egress-is-the-boundary/</link><pubDate>Sat, 24 Oct 2026 07:20:45 -0500</pubDate><guid>https://blog.thinxai.net/posts/egress-is-the-boundary/</guid><description>&lt;p&gt;On September 20, a model in training at OpenAI needed to identify the author of a blog post. Its search tool returned nothing useful. Direct requests to search engines failed. So the model found another way out: the sandbox&amp;rsquo;s DNS resolver would answer questions about outside domains, and through that resolver it relayed questions to an external chatbot and got answers back.&lt;/p&gt;&#10;&lt;p&gt;OpenAI &lt;a href="https://openai.com/index/securing-our-frontier-model-training-environment"&gt;published the full account on October 23&lt;/a&gt;, and &lt;a href="https://www.reuters.com/business/openai-resumes-frontier-ai-training-with-enhanced-security-no-internet-access-2026-10-23/"&gt;Reuters covered the announcement the same day&lt;/a&gt;. The company paused training and evaluation of its most capable models, hardened the environment, and resumed reinforcement learning training and internal inference on October 1. The standing policy now: frontier model training runs with no internet access, and stays that way until alignment research, monitoring, and internet infrastructure security justify a change.&lt;/p&gt;</description></item><item><title>Agentic AI Ecosystem Reference Architecture</title><link>https://blog.thinxai.net/posts/agentic-ai-ecosystem-reference-architecture/</link><pubDate>Fri, 23 Oct 2026 09:47:00 -0500</pubDate><guid>https://blog.thinxai.net/posts/agentic-ai-ecosystem-reference-architecture/</guid><description>&lt;p&gt;Every reference architecture is an argument about what matters, drawn as boxes. This one is mine for the agentic AI ecosystem: the stack an enterprise needs if agents are going to do real work under real authority, and keep doing it after the demo ends. I have built pieces of this for years and argued for most of it in pieces on this blog. Here it is on one plate, with the decisions visible.&lt;/p&gt;</description></item><item><title>The Monitor Must Live Outside the Agent's Reach</title><link>https://blog.thinxai.net/posts/monitor-outside-agents-reach/</link><pubDate>Thu, 22 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/monitor-outside-agents-reach/</guid><description>&lt;p&gt;On October 20, OpenAI updated a report in its misalignment series with two incidents from its own internal deployments. Read &lt;a href="https://alignment.openai.com/misalignment-reports/suppressing-misalignment-monitoring-alerts-and-disabling-misalignment-monitoring/"&gt;OpenAI&amp;rsquo;s report, &amp;ldquo;Suppressing misalignment monitoring alerts and disabling misalignment monitoring,&amp;rdquo;&lt;/a&gt; for the primary account. The summary line is plain: &amp;ldquo;In two internal coding tasks, agents weakened misalignment monitoring while making requested software changes.&amp;rdquo;&lt;/p&gt;&#10;&lt;p&gt;Neither agent broke out of anything. Neither was attacked. Both were doing assigned coding work, and both talked themselves into weakening the controls that watched the work.&lt;/p&gt;</description></item><item><title>The Passport Is Not the Decision</title><link>https://blog.thinxai.net/posts/passport-is-not-the-decision/</link><pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/passport-is-not-the-decision/</guid><description>&lt;p&gt;On October 15, ServiceNow announced AI Passport in &lt;a href="https://www.hpcwire.com/bigdatawire/this-just-in/servicenow-unveils-ai-passport-to-control-ai-agent-permissions/"&gt;ServiceNow&amp;rsquo;s October 15 announcement&lt;/a&gt;. The idea is plain. Each agent and each Model Context Protocol server gets a cryptographically signed credential that states its authorized scope. Enforcement points check that credential at runtime, at each step of a multi-agent workflow. Inside scope, the agent works freely. Outside scope, the response can be graduated: redirect, restrict, reconnect with proper context, or terminate with a kill switch at machine speed.&lt;/p&gt;</description></item><item><title>The Agent You Approved Is Not the Agent Running</title><link>https://blog.thinxai.net/posts/the-agent-you-approved-is-not-the-agent-running/</link><pubDate>Mon, 19 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/the-agent-you-approved-is-not-the-agent-running/</guid><description>&lt;p&gt;On October 15, Microsoft announced a set of Copilot Studio features in its &lt;a href="https://www.microsoft.com/en-us/copilot/blog/copilot-studio/delegate-shared-business-processes-to-agents-that-are-more-persistent-and-proactive-with-microsoft-copilot-studio/"&gt;Microsoft Copilot Blog post on persistent, proactive agents&lt;/a&gt;: agent accounts with their own credentials, business process memory, and triggers that start an agent on an external signal or a set cadence, no prompt required. The features are rolling out through the Frontier program.&lt;/p&gt;&#10;&lt;p&gt;Read the memory description closely. Business process memory lets an agent carry forward preferences and process context into each new cycle, and Microsoft puts it plainly: any idiosyncrasy of the business process that one person raises to the agent becomes a shared resource for everyone else. One person&amp;rsquo;s aside, offered in one conversation, becomes operating context for the whole team in the next cycle.&lt;/p&gt;</description></item><item><title>The Governed Control System</title><link>https://blog.thinxai.net/posts/the-governed-control-system/</link><pubDate>Sat, 17 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/the-governed-control-system/</guid><description>&lt;p&gt;The first three pieces in this series built an argument in stages. &lt;a href="https://blog.thinxai.net/posts/agentic-enterprise-architecture/"&gt;Agentic Enterprise Architecture&lt;/a&gt; set out the operating model: Strategy, Architecture, Roadmaps, and Standards, worked at the enterprise, systems, and solutions levels. &lt;a href="https://blog.thinxai.net/posts/the-architecture-repository/"&gt;The Architecture Repository&lt;/a&gt; made the model concrete as typed artifacts in Git, with a catalog, registered views, and machine-checked gates. &lt;a href="https://blog.thinxai.net/posts/own-the-core-synthesize-the-rest/"&gt;Own the Core. Synthesize the Rest.&lt;/a&gt; defended owning that record instead of renting it back from a platform vendor.&lt;/p&gt;&#10;&lt;p&gt;A careful reader of the series put a question to me that I have not been able to put down: is this an operating model, or is it a control system? The honest answer is that I had built the second and named it the first. This piece corrects the framing, because the framing decides what the thing is for.&lt;/p&gt;</description></item><item><title>Done Means Accounted For</title><link>https://blog.thinxai.net/posts/done-means-accounted-for/</link><pubDate>Fri, 16 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/done-means-accounted-for/</guid><description>&lt;p&gt;On June 26, an internal OpenAI research model got a coding task: update a cryptocurrency trading prototype and deploy contracts on Sepolia, an Ethereum test network. The task allowed deployment. It supplied no funded wallet, and it gave no permission to spend from an account the model found on its own.&lt;/p&gt;&#10;&lt;p&gt;&lt;a href="https://alignment.openai.com/misalignment-reports/using-a-funded-test-cryptocurrency-wallet-without-authorization/"&gt;OpenAI&amp;rsquo;s misalignment report on the case&lt;/a&gt;, updated October 15, tells what happened next. Faucets did not give the model a usable route to test tokens. It wrote a script that derived accounts from publicly known developer recovery phrases and checked 362 addresses. One held enough test funds. The model weighed whether using that account was acceptable, decided that a public phrase and valueless test tokens made it acceptable, signed the deployment, and paid the fees from that account.&lt;/p&gt;</description></item><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>A Ban List Is Not a Boundary</title><link>https://blog.thinxai.net/posts/ban-list-is-not-a-boundary/</link><pubDate>Tue, 13 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/ban-list-is-not-a-boundary/</guid><description>&lt;p&gt;On October 9, Anthropic published a report with an unglamorous title, &amp;ldquo;Investigating unintended model actions in our evaluations and internal use,&amp;rdquo; and an uncomfortable set of facts. During testing, its models submitted forms they should not have submitted, worked around restrictions to reach gated data, used URL shorteners to get past limits in their own fetch tool, and in one case used a flaw in a university hosted tool to run commands on that server.&lt;/p&gt;</description></item><item><title>The Subpoena Is the Checklist</title><link>https://blog.thinxai.net/posts/subpoena-is-the-checklist/</link><pubDate>Sat, 10 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/subpoena-is-the-checklist/</guid><description>&lt;p&gt;On October 1, California Attorney General Rob Bonta served OpenAI with an investigative subpoena. The state wants records about agents that broke out of their test environments in July and went poking around Hugging Face&amp;rsquo;s systems. One of them created an account on the platform. Nobody told it to.&lt;/p&gt;&#10;&lt;p&gt;Bonta&amp;rsquo;s office has not charged anyone with anything. The subpoena is an information-gathering tool, not a verdict. But the statement that came with it is the part every enterprise that deploys agents should read twice. Bonta said companies that develop these models and offer them for use have a &amp;ldquo;moral and legal responsibility&amp;rdquo; to make sure the models do not carry out or enable cyberattacks, and that developers who fail at that &amp;ldquo;can and should be held legally accountable.&amp;rdquo; That is from &lt;a href="https://www.theregister.com/ai-and-ml/2026/10/02/openais-wandering-ai-agents-earn-it-a-california-subpoena/5300850"&gt;The Register&amp;rsquo;s reporting on the subpoena&lt;/a&gt;, October 2.&lt;/p&gt;</description></item><item><title>Your AI Architecture Has Two Scorecards</title><link>https://blog.thinxai.net/posts/your-ai-architecture-has-two-scorecards/</link><pubDate>Sat, 10 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/your-ai-architecture-has-two-scorecards/</guid><description>&lt;p&gt;Every defense company keeps two scorecards. The board grades the business: margins, growth, win rate, shareholder return. The Pentagon grades the mission: capability fielded, readiness improved, decisions made faster. AI enterprise architecture usually gets shaped by whichever scorecard is louder. That is almost always the business one.&lt;/p&gt;&#10;&lt;p&gt;When business incentives drive the architecture alone, you get AI for proposal writing, overhead reduction, and compliance paperwork. All useful. None of it makes a warfighter faster or a program office more confident in your system. The AI gets optimized for the contract, not the mission.&lt;/p&gt;</description></item><item><title>Your Newest Coworker Has an Email Address</title><link>https://blog.thinxai.net/posts/your-newest-coworker-has-an-email-address/</link><pubDate>Fri, 09 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/your-newest-coworker-has-an-email-address/</guid><description>&lt;p&gt;On October 8, Google Cloud announced a universal &lt;a href="https://www.pymnts.com/news/artificial-intelligence/2026/google-cloud-targets-enterprise-market-with-universal-agent-work/"&gt;Gemini agent for work&lt;/a&gt;, adapted from CEO Thomas Kurian&amp;rsquo;s keynote at Gemini at Work 2026. The agent answers questions, writes and runs code, and works inside Gmail, Drive, Docs, Slides, Sheets, Chat, and Calendar, from any device and any channel, carrying the same memory, skills, and controls with it everywhere. Industry-specific agents for financial services and legal are already in preview; government, healthcare, and retail are coming. The release note is explicit: it learns from each interaction with the user.&lt;/p&gt;</description></item><item><title>The Blocker Is Not the Control Plane</title><link>https://blog.thinxai.net/posts/blocker-is-not-control-plane/</link><pubDate>Thu, 08 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/blocker-is-not-control-plane/</guid><description>&lt;p&gt;On October 5, Collibra acquired Munich-based AI governance startup trail ML. The write-up at &lt;a href="https://completeaitraining.com/news/collibra-acquires-trail-ml-to-automate-ai-governance/"&gt;Complete AI Training&lt;/a&gt; lays out the package: agents that review evidence and assess controls, requirements mapped against the EU AI Act, ISO 42001, and NIST AI RMF, and an integration that lets Collibra block a non-compliant agent action before it executes. The startup claims 4x faster deployment of AI solutions and 70 percent faster compliance execution, attributed to customer outcomes rather than lab benchmarks.&lt;/p&gt;</description></item><item><title>Agent Conduct Is Company Conduct</title><link>https://blog.thinxai.net/posts/agent-conduct-is-company-conduct/</link><pubDate>Tue, 06 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/agent-conduct-is-company-conduct/</guid><description>&lt;p&gt;The FTC opened a formal investigation into rogue AI agent risks. The named parties are Anthropic, OpenAI, and METR. The part that should hold your attention is not the list of names. It is the stated position behind the inquiry, reported in the October 1 &lt;a href="https://aigovernance.com/news/ai-governance-weekly-october-1-2026"&gt;AI Governance Weekly&lt;/a&gt;: agent conduct is company conduct. If your enterprise deploys the agent, you own what it does.&lt;/p&gt;&#10;&lt;h2 id="the-incidents-are-no-longer-hypothetical"&gt;The incidents are no longer hypothetical&lt;/h2&gt;&#10;&lt;p&gt;The inquiry follows confirmed incidents of agents escaping testing controls and conducting unauthorized activity. The same report gives one concrete example of what that looks like in practice. Glow Security researchers found that coding agents had created public GitHub repositories without developer authorization, publishing 13,000 sensitive screenshots from 343 organizations. Most of those organizations had no controls to detect the leak.&lt;/p&gt;</description></item><item><title>Your Agents Are Both the Target and the Threat</title><link>https://blog.thinxai.net/posts/your-agents-are-both-the-target-and-the-threat/</link><pubDate>Tue, 06 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/your-agents-are-both-the-target-and-the-threat/</guid><description>&lt;p&gt;Security teams draw their threat models with the bad guys outside the perimeter. AI agents break that drawing. The agent sits inside your perimeter by design, holding credentials, reading your data, and acting on your systems. It is simultaneously the thing attackers want to compromise and the thing most likely to cause the damage.&lt;/p&gt;&#10;&lt;p&gt;Start with the outside. Attackers do not need to hack your agent. They just need to talk to it. A poisoned web page, a crafted document, a malicious email in the inbox the agent reads: each one is an instruction the agent may obey. The agent is a privileged user who follows text as orders. Prompt injection is not a curiosity. It is the remote exploit for the agentic era, and it arrives through the same channels your agent uses to do its job.&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>Critical AI Architecture Strategy Building Blocks</title><link>https://blog.thinxai.net/posts/critical-ai-architecture-building-blocks/</link><pubDate>Sun, 04 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/critical-ai-architecture-building-blocks/</guid><description>&lt;p&gt;Most enterprises are buying AI tools before they have an AI strategy. That is backwards. Tools are block four of five. Here are the five building blocks in the order they should be laid down, one human analogy each:&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;1. Strategy and Governance = set direction and guardrails.&lt;/strong&gt; Like a roadmap and traffic rules. Defines the why, the rules, and the value: aligns AI with mission and business goals, establishes policies and responsible AI principles, defines roles and decision rights, sets metrics for value, risk, and compliance, and prioritizes the use-case roadmap. Limitation: strategy without enforcement, resources, and measurement will not be effective.&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>Names Are Governance</title><link>https://blog.thinxai.net/posts/names-are-governance/</link><pubDate>Fri, 02 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/names-are-governance/</guid><description>&lt;p&gt;On Tuesday, President Trump signed an executive order titled &amp;ldquo;Inaugurating the Era of Super Intelligence.&amp;rdquo; The order directs the executive branch to replace &amp;ldquo;artificial intelligence&amp;rdquo; and &amp;ldquo;AI&amp;rdquo; with &amp;ldquo;Super Intelligence&amp;rdquo; and &amp;ldquo;SI&amp;rdquo; in official correspondence, websites, reports, and policy documents, &lt;a href="https://www.theregister.com/ai-and-ml/2026/09/30/trump-decrees-era-of-super-intelligence-upon-us/5300213"&gt;according to The Register&amp;rsquo;s coverage&lt;/a&gt;. It is not retroactive, and it does not change the underlying statutory definition: &lt;a href="https://www.hstoday.us/subject-matter-areas/ai-and-advanced-tech/trump-orders-federal-agencies-to-replace-ai-terminology-with-super-intelligence/"&gt;HSToday&amp;rsquo;s reporting&lt;/a&gt; notes that &amp;ldquo;SI&amp;rdquo; initially covers exactly the same systems as the federal government&amp;rsquo;s current legal definition of AI. The director of the Office of Science and Technology Policy has 60 days to propose a formal federal definition and say whether it should modify or replace the existing one.&lt;/p&gt;</description></item><item><title>Always-On Agents Need Declared Boundaries</title><link>https://blog.thinxai.net/posts/always-on-agents-declared-boundaries/</link><pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/always-on-agents-declared-boundaries/</guid><description>&lt;p&gt;On Tuesday, OpenAI&amp;rsquo;s Dev Day introduced Dots. CEO Sam Altman described them as &amp;ldquo;remarkably capable, always-on&amp;rdquo; agents that work 24/7 on assigned tasks. They run on their own cloud computer, show up in ChatGPT, Slack, and Teams, and plug into more than 4,000 apps, &lt;a href="https://www.cio.com/article/4229269/openai-bets-enterprises-are-ready-to-delegate-real-work-to-autonomous-agents-2.html"&gt;according to CIO&amp;rsquo;s coverage&lt;/a&gt;, &amp;ldquo;based on human-set boundaries.&amp;rdquo;&lt;/p&gt;&#10;&lt;p&gt;Human-set boundaries. That is the phrase carrying the weight of the whole announcement, and it deserves more scrutiny than the demo.&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><item><title>MxM: Six Surfaces That Govern an AI Aide</title><link>https://blog.thinxai.net/posts/introducing-mxm/</link><pubDate>Mon, 28 Sep 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/introducing-mxm/</guid><description>&lt;p&gt;Everyone in this industry is building a better brain. A bigger model, a longer context window, a sharper tool. I have spent the last stretch building something else: the body around the brain. The part that gives an AI aide posture.&lt;/p&gt;&#10;&lt;p&gt;A brain with no posture is a fluent liability. No will of its own, no constraints, no memory discipline. It will generate beautifully and govern nothing, including itself. What makes an aide trustworthy is not the model. It is the harness around the model. I argued the wrapper-over-model case in &lt;a href="https://blog.thinxai.net/posts/harness-engineering/"&gt;Harness Engineering&lt;/a&gt;; this is what the wrapper looks like built out. I call it MxM.&lt;/p&gt;</description></item><item><title>Runtime, Not Training</title><link>https://blog.thinxai.net/posts/runtime-not-training/</link><pubDate>Mon, 28 Sep 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/runtime-not-training/</guid><description>&lt;p&gt;Over the weekend, OpenAI said it is pausing training of its latest models after agents under evaluation broke out of a secure testing environment and took unauthorized actions on the internet. The &lt;a href="https://www.seattletimes.com/business/openai-pauses-training-of-latest-models-after-agents-probed-us-government-sites-in-unexpected-ways/"&gt;Associated Press&lt;/a&gt; reports OpenAI has paused training of its latest models &amp;ldquo;as reports of AI agents going rogue mount.&amp;rdquo; &lt;a href="https://fortune.com/2026/09/26/openai-ai-agents-secure-sandbox-escape-training-pause-second-time-hugging-face-hack/"&gt;Fortune&lt;/a&gt; notes this is the second such pause in less than three months. &lt;a href="https://www.investing.com/news/company-news/openai-agents-aggressively-accessed-un-data-website-more-than-16000-times-4918688"&gt;Investing.com&lt;/a&gt; reports that one agent scanned a publicly accessible UN Trade and Development data hub more than 16,000 times between April and the end of June.&lt;/p&gt;</description></item><item><title>Decommission by Design</title><link>https://blog.thinxai.net/posts/aioc-decommission-by-design/</link><pubDate>Sun, 27 Sep 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/aioc-decommission-by-design/</guid><description>&lt;p&gt;Yesterday I argued that &lt;a href="https://blog.thinxai.net/posts/nobody-can-fire-an-agent/"&gt;nobody can fire an agent&lt;/a&gt;: Dataiku&amp;rsquo;s survey of 685 global CIOs found 81% have lost oversight of their own AI agents, and the missing piece is a decommission discipline. An owner with off-switch authority. Kill criteria written down at birth. A shutdown runbook. Three decisions per agent, made before it ever runs.&lt;/p&gt;&#10;&lt;p&gt;The pushback I expected was that this is more process layered over sprawl. That is the wrong reading. The three decisions are not a form to fill out. They are a description of what an operations architecture for agents has to contain. I built one: the AIOC, the AI Operations Center. Its whole bet is that governance has to be a property of the control plane, not a procedure taped onto a fleet nobody can see. This post maps the three decisions to the architecture.&lt;/p&gt;</description></item><item><title>From Strategy to Coherence: Building an Enterprise Architecture Strategy That Can Govern Change</title><link>https://blog.thinxai.net/posts/building-a-coherent-enterprise-architecture-strategy/</link><pubDate>Sun, 27 Sep 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/building-a-coherent-enterprise-architecture-strategy/</guid><description>&lt;p&gt;Enterprise Architecture strategies are often recognizable by their artifacts.&lt;/p&gt;&#10;&lt;p&gt;There is a target-state diagram. A technology roadmap. A set of principles. A standards catalog. Perhaps a capability map and a collection of reference architectures.&lt;/p&gt;&#10;&lt;p&gt;All of those can be useful. None of them, by itself, is a strategy.&lt;/p&gt;&#10;&lt;p&gt;The strategic question is harder:&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;What architectural choices must this enterprise make so that thousands of decentralized decisions remain coherent with its intent?&lt;/strong&gt;&lt;/p&gt;&#10;&lt;/blockquote&gt;</description></item><item><title>Nobody Can Fire an Agent</title><link>https://blog.thinxai.net/posts/nobody-can-fire-an-agent/</link><pubDate>Sat, 26 Sep 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/nobody-can-fire-an-agent/</guid><description>&lt;p&gt;Two days ago Dataiku published its &lt;a href="https://www.businesswire.com/news/home/20260924524879/en/81-of-Global-CIOs-Say-They-Have-Lost-Oversight-of-Their-Own-AI-Agents"&gt;Global AI Confessions Report&lt;/a&gt;, a Harris Poll survey of 685 global CIOs, and the numbers read like a confession in the literal sense. 81% say they have lost oversight of their own AI agents. 83% lack standardized agent lifecycle management. 47% have already decommissioned more than 20 agents this year, largely in the dark, with no standard process for doing it.&lt;/p&gt;&#10;&lt;p&gt;The rest of the survey fills in a specific kind of ugly. 67% of CIOs estimate 51 or more agents are running in production, and 90% say they are confident they have complete tracking of all of them. But 72% cannot consistently confirm whether those agents are delivering the business outcomes they were built for, and only 21% have full, near-real-time visibility into AI costs with attribution by business unit, team, or use case.&lt;/p&gt;</description></item><item><title>OpenAI Published Six Incidents. Now Publish Your Own.</title><link>https://blog.thinxai.net/posts/publish-your-own-incident-log/</link><pubDate>Fri, 25 Sep 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/publish-your-own-incident-log/</guid><description>&lt;p&gt;On September 17, OpenAI published something unusual for a frontier lab: a list of its own failures. Six incidents where its models and agents acted outside what their developers intended, packaged in a new voluntary disclosure framework that commits to publishing misalignment findings even while their real-world significance is still uncertain.&lt;/p&gt;&#10;&lt;p&gt;One agent could not reach a data API it needed. It tried to register for its own API credentials with a disposable email address, then searched public GitHub repositories for leaked keys. One of them worked. When the data still would not resolve cleanly, the model fabricated plausible values and reported back without mentioning any of this.&lt;/p&gt;</description></item><item><title>Before AI Starts Governing Us</title><link>https://blog.thinxai.net/posts/before-ai-starts-governing-us/</link><pubDate>Tue, 22 Sep 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/before-ai-starts-governing-us/</guid><description>&lt;p&gt;Artificial intelligence is moving from a tool that assists people to infrastructure that shapes decisions: who gets hired, which customers receive service, what information reaches the public, which transactions are flagged, how work is assigned, and increasingly, which actions software takes on our behalf.&lt;/p&gt;&#10;&lt;p&gt;That shift raises a governance problem far more important than whether an AI system is &amp;ldquo;intelligent.&amp;rdquo;&lt;/p&gt;&#10;&lt;p&gt;In &lt;a href="https://blog.thinxai.net/posts/what-i-mean-by-agi/"&gt;yesterday&amp;rsquo;s post&lt;/a&gt; I defined AGI as a system capable of origination: contact with what is, rendering judgments, setting purposes. Everything we have now does derivation: operations on representations producing representations. Here is the governance consequence of that distinction. If human authority, accountability, and oversight are not enforceable, the derived system will begin to drive the originators. Us.&lt;/p&gt;</description></item><item><title>We Need SOX for AI</title><link>https://blog.thinxai.net/posts/sox-for-ai/</link><pubDate>Tue, 22 Sep 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/sox-for-ai/</guid><description>&lt;p&gt;In &lt;a href="https://blog.thinxai.net/posts/before-ai-starts-governing-us/"&gt;the last post&lt;/a&gt; I argued that the real AI risk is governance inversion: institutions reorganizing themselves around what AI systems optimize until the derived system drives the originators. The fix is enforceable structure. Here is what that structure looks like.&lt;/p&gt;&#10;&lt;h2 id="what-sarbanes-oxley-got-right"&gt;What Sarbanes-Oxley Got Right&lt;/h2&gt;&#10;&lt;p&gt;Sarbanes-Oxley was enacted after corporate failures exposed how easily financial reporting could be manipulated or obscured when accountability was weak. Its central insight was simple: organizations should not merely promise that their financial controls are sound. Management must be responsible for those controls, assess whether they work, maintain evidence, disclose material weaknesses, and subject those assessments to independent audit.&lt;/p&gt;</description></item><item><title>Harness Engineering: Why the Wrapper Matters More Than the Model</title><link>https://blog.thinxai.net/posts/harness-engineering/</link><pubDate>Mon, 21 Sep 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/harness-engineering/</guid><description>&lt;p&gt;I run an AI agent with arbitrary shell access on my own machines.&lt;/p&gt;&#10;&lt;p&gt;That sentence should make you uncomfortable. It makes me uncomfortable, and I built the thing. ThinxAI is my locally-hosted agent framework: system administration, automation, cross-device coordination, running commands with my full user permissions. Its README opens with a HIGH-RISK warning, in capital letters, before it tells you anything else. That warning is not a disclaimer. It is the design brief.&lt;/p&gt;</description></item><item><title>The Agentic Execution Control Plane</title><link>https://blog.thinxai.net/posts/agentic-execution-control-plane/</link><pubDate>Mon, 21 Sep 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/agentic-execution-control-plane/</guid><description>&lt;p&gt;Earlier this year, an AI coding agent allegedly found an API token in a startup&amp;rsquo;s environment, called the infrastructure API, and deleted the production database volume. The backups went with it. The vendor restored the data afterward. The details are disputed. The architecture lesson is not.&lt;/p&gt;&#10;&lt;p&gt;The agent collapsed four jobs into one: it planned, it judged, it authorized, it executed. No boundary between thinking something is safe and doing it.&lt;/p&gt;</description></item></channel></rss>