<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Enterprise Architecture on Thinx-Tank</title><link>https://blog.thinxai.net/tags/enterprise-architecture/</link><description>Recent content in Enterprise Architecture on Thinx-Tank</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 23 Oct 2026 09:47:00 -0500</lastBuildDate><atom:link href="https://blog.thinxai.net/tags/enterprise-architecture/index.xml" rel="self" type="application/rss+xml"/><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>Agentic Enterprise Architecture</title><link>https://blog.thinxai.net/posts/agentic-enterprise-architecture/</link><pubDate>Sat, 17 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/agentic-enterprise-architecture/</guid><description>&lt;p&gt;A newly stood up enterprise architecture org gets a brief window that an established one does not: it can choose how it will work before the habits choose for it. The default habits are well known. Architects interview stakeholders, build models in a proprietary tool, present decks to a review board, file the artifacts, and watch them go stale from the day they are approved. Within two years the repository describes an estate that no longer exists, and the org&amp;rsquo;s real product becomes the review meeting itself.&lt;/p&gt;</description></item><item><title>Own the Core. Synthesize the Rest.</title><link>https://blog.thinxai.net/posts/own-the-core-synthesize-the-rest/</link><pubDate>Sat, 17 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/own-the-core-synthesize-the-rest/</guid><description>&lt;p&gt;In &lt;a href="https://blog.thinxai.net/posts/the-architecture-repository/"&gt;The Architecture Repository&lt;/a&gt;, I published the concrete structure of the architecture repository: numbered baselines, typed artifacts, policy checks, human ratification in the tooling. The responses it draws tend to arrive as two questions. First: where are the diagrams, the dashboards, the impact analysis, the portal? Second, right behind it: so the alternative is a commercial EA platform, and you are against buying one?&lt;/p&gt;&#10;&lt;p&gt;Both questions assume the repository is competing with a platform. It is not. It is the core the platform would have owned. This piece is about the difference.&lt;/p&gt;</description></item><item><title>The Architecture Repository</title><link>https://blog.thinxai.net/posts/the-architecture-repository/</link><pubDate>Sat, 17 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/the-architecture-repository/</guid><description>&lt;p&gt;In &lt;a href="https://blog.thinxai.net/posts/agentic-enterprise-architecture/"&gt;Agentic Enterprise Architecture&lt;/a&gt;, I laid out a position: an operating model (Strategy, Architecture, Roadmaps, and Standards at the enterprise, systems, and solutions levels), artifacts held as code, and agents operating the practice under human ratification. A position without an artifact is an opinion. This piece is the artifact: the Git repository the model lives in, structured so that the claims in the first piece are checkable rather than aspirational.&lt;/p&gt;&#10;&lt;h2 id="where-the-shape-comes-from"&gt;Where the shape comes from&lt;/h2&gt;&#10;&lt;p&gt;The layout borrows its grammar from the repository template I use for my own working repos. Not the contents, which are built for a different job, but three structural rules that have held up under daily use.&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>Enterprise Architecture: Human-Curated, AI-Enabled</title><link>https://blog.thinxai.net/posts/human-curated-ai-enabled-enterprise-architecture/</link><pubDate>Sun, 27 Sep 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/human-curated-ai-enabled-enterprise-architecture/</guid><description>&lt;p&gt;An enterprise architect spends a surprising amount of time finding out what the enterprise already knows. Strategy sits in one place, application inventories in another, and the reason for a standard may live in someone&amp;rsquo;s memory. Before evaluating a change, we have to assemble enough of that picture to understand its consequences.&lt;/p&gt;&#10;&lt;p&gt;I put together this short video for a developing architect. Its central idea is that Enterprise Architecture maintains intentional coherence as an enterprise changes. GenAI can help with the information work around that responsibility. People still own the judgment.&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></channel></rss>