<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Open-Source on Thinx-Tank</title><link>https://blog.thinxai.net/tags/open-source/</link><description>Recent content in Open-Source on Thinx-Tank</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 17 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.thinxai.net/tags/open-source/index.xml" rel="self" type="application/rss+xml"/><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></channel></rss>