<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MxM on Thinx-Tank</title><link>https://blog.thinxai.net/tags/mxm/</link><description>Recent content in MxM on Thinx-Tank</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 16 Nov 2026 19:20:00 -0600</lastBuildDate><atom:link href="https://blog.thinxai.net/tags/mxm/index.xml" rel="self" type="application/rss+xml"/><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>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>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>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></channel></rss>