<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Mohit Rane - Letters from a Founding Architect</title><description>Founding Architect designing Context Intelligence, Decision Architecture, Security Governance, and Enterprise AI platforms that survive complexity, preserve human judgment, and scale responsibly.</description><link>https://mohitrane.com/</link><language>en-us</language><item><title>Enterprise AI fails at four places</title><link>https://mohitrane.com/writing/enterprise-ai-fails-at-four-places/</link><guid isPermaLink="true">https://mohitrane.com/writing/enterprise-ai-fails-at-four-places/</guid><description>When an enterprise AI initiative fails, the post-mortem usually blames the model. It is almost never the model. The failures cluster at four predictable seams: context, governance, evaluation, and operating model.</description><pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate><category>Enterprise AI</category><category>enterprise-ai</category><category>failure-modes</category><category>governance</category><category>evaluation</category></item><item><title>Scaling judgment without diluting it</title><link>https://mohitrane.com/writing/scaling-judgment-without-diluting-it/</link><guid isPermaLink="true">https://mohitrane.com/writing/scaling-judgment-without-diluting-it/</guid><description>A founder&apos;s intuition is the company&apos;s most valuable asset and the hardest to transfer. Turning it into systems others can apply means resisting the urge to flatten it into rules that miss the point.</description><pubDate>Thu, 14 May 2026 00:00:00 GMT</pubDate><category>Leadership</category><category>judgment</category><category>scaling</category><category>leadership</category><category>intuition</category></item><item><title>Context has a half-life</title><link>https://mohitrane.com/writing/context-has-a-half-life/</link><guid isPermaLink="true">https://mohitrane.com/writing/context-has-a-half-life/</guid><description>Context is not a static asset you assemble once. It decays from the moment it is created, and the only reliable defense is to capture it at the moment of decision, when it is still true.</description><pubDate>Thu, 23 Apr 2026 00:00:00 GMT</pubDate><category>Context Intelligence</category><category>context</category><category>decay</category><category>capture</category><category>provenance</category></item><item><title>What survives when every tool changes</title><link>https://mohitrane.com/writing/what-survives-when-every-tool-changes/</link><guid isPermaLink="true">https://mohitrane.com/writing/what-survives-when-every-tool-changes/</guid><description>Frameworks, vendors, and models all have a shelf life measured in quarters. The work that compounds is the architecture underneath - the part designed to outlive the implementations that happen to express it today.</description><pubDate>Wed, 08 Apr 2026 00:00:00 GMT</pubDate><category>Future Systems</category><category>architecture</category><category>durability</category><category>abstraction</category><category>tooling</category></item><item><title>Accountability is not a checkbox</title><link>https://mohitrane.com/writing/accountability-is-not-a-checkbox/</link><guid isPermaLink="true">https://mohitrane.com/writing/accountability-is-not-a-checkbox/</guid><description>Human in the loop and approval workflows feel like governance, but without legible reasoning and durable decision records they are accountability theater - a signature on a choice no one can actually defend.</description><pubDate>Tue, 17 Mar 2026 00:00:00 GMT</pubDate><category>Security Governance</category><category>accountability</category><category>governance</category><category>human-in-the-loop</category><category>audit</category></item><item><title>Decisions are designed artifacts</title><link>https://mohitrane.com/writing/decisions-are-designed-artifacts/</link><guid isPermaLink="true">https://mohitrane.com/writing/decisions-are-designed-artifacts/</guid><description>Most organizations treat decisions as events that happen and then vanish. Treating them instead as designed objects - with inputs, owners, evidence, and records - is the difference between an organization that learns and one that repeats itself.</description><pubDate>Thu, 26 Feb 2026 00:00:00 GMT</pubDate><category>Decision Architecture</category><category>decisions</category><category>design</category><category>records</category><category>accountability</category></item><item><title>The model was never the moat</title><link>https://mohitrane.com/writing/the-model-was-never-the-moat/</link><guid isPermaLink="true">https://mohitrane.com/writing/the-model-was-never-the-moat/</guid><description>Every enterprise can buy the same frontier model. The durable advantage lives in the governed context that surrounds it - what the system knows, why it knows it, and who is accountable for the knowing.</description><pubDate>Wed, 11 Feb 2026 00:00:00 GMT</pubDate><category>Context Intelligence</category><category>context</category><category>moat</category><category>enterprise-ai</category><category>governance</category></item><item><title>What is a founding architect</title><link>https://mohitrane.com/writing/what-is-a-founding-architect/</link><guid isPermaLink="true">https://mohitrane.com/writing/what-is-a-founding-architect/</guid><description>A role defined not by the code it writes or the org it runs, but by the first principles and decision systems it sets down before either exists. A working definition.</description><pubDate>Mon, 19 Jan 2026 00:00:00 GMT</pubDate><category>Founding Architect</category><category>founding-architect</category><category>first-principles</category><category>decision-systems</category><category>role</category></item></channel></rss>