<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Architecture on Thinx-Tank</title><link>https://blog.thinxai.net/tags/architecture/</link><description>Recent content in Architecture on Thinx-Tank</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 21 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.thinxai.net/tags/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Data Access Is Not Process Context</title><link>https://blog.thinxai.net/posts/data-access-is-not-process-context/</link><pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/data-access-is-not-process-context/</guid><description>&lt;p&gt;On October 20, ARIS launched Process Context for Enterprise AI. In &lt;a href="https://uktechnews.co.uk/2026/10/20/aris-launches-process-context-for-enterprise-ai-reinforcing-position-as-the-essential-platform-for-ai-ecosystem/"&gt;ARIS&amp;rsquo;s October 20 announcement&lt;/a&gt;, the company describes the product as a layer that gives agents the business understanding they need to do work, not just access to business data. The research behind it was conducted by The Hackett Group in collaboration with ARIS. It surveyed 200 respondents at large and multinational organizations. Eighty-two percent agreed that process context is required for deploying AI agents. Only 21 percent reported comprehensive, real-time visibility into how work flows across their enterprise. Organizations using process context tools were more than five times as likely to report measurable return from their AI investments.&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>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>Generation Is Not Inquiry</title><link>https://blog.thinxai.net/posts/generation-is-not-inquiry/</link><pubDate>Wed, 23 Sep 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/generation-is-not-inquiry/</guid><description>&lt;p&gt;We increasingly hear that artificial intelligence systems “run inference loops.” The phrase sounds stronger than the underlying mechanism usually warrants.&lt;/p&gt;&#10;&lt;p&gt;To a machine-learning engineer, &lt;em&gt;inference&lt;/em&gt; can simply mean executing a trained model against new input. To a logician, scientist, or ordinary reader, inference suggests something richer: reasoning from premises, weighing evidence, drawing conclusions, testing explanations, and perhaps revising a conclusion when the evidence proves it wrong.&lt;/p&gt;&#10;&lt;p&gt;Those are different things.&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>