<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Swarochish Chekuri</title>
    <link>https://swarochish.com</link>
    <atom:link href="https://swarochish.com/feed.xml" rel="self" type="application/rss+xml"/>
    <description>Writing, research and notes on reducing the distance between intent and execution.</description>
    <language>en-GB</language>
    <lastBuildDate>Fri, 14 Aug 2026 09:00:00 +0000</lastBuildDate>
    <item>
      <title>A General Theory of Human-System Interaction</title>
      <link>https://swarochish.com/research/human-system-interaction</link>
      <guid isPermaLink="true">https://swarochish.com/research/human-system-interaction</guid>
      <pubDate>Thu, 14 Aug 2026 09:00:00 +0000</pubDate>
      <description>Felt ease treated as a regulation problem rather than a design problem. Five channels, complexity as allocation, and friction classified by what it produces.</description>
    </item>
    <item>
      <title>Trust Across Boundaries</title>
      <link>https://swarochish.com/research/trust-across-boundaries</link>
      <guid isPermaLink="true">https://swarochish.com/research/trust-across-boundaries</guid>
      <pubDate>Fri, 01 Aug 2026 09:00:00 +0000</pubDate>
      <description>An eight-layer model of trust with strict dependency ordering, spanning human, agent-human and agent-agent interaction.</description>
    </item>
    <item>
      <title>Broken at the Seams</title>
      <link>https://swarochish.com/research/broken-at-the-seams</link>
      <guid isPermaLink="true">https://swarochish.com/research/broken-at-the-seams</guid>
      <pubDate>Fri, 01 Aug 2026 09:00:00 +0000</pubDate>
      <description>Multi-agent systems fail where control, context or commitment crosses a boundary. Ten design principles for that layer.</description>
    </item>
    <item>
      <title>The distance between intent and execution</title>
      <link>https://swarochish.com/writing/distance-between-intent-and-execution</link>
      <guid isPermaLink="true">https://swarochish.com/writing/distance-between-intent-and-execution</guid>
      <pubDate>Fri, 01 Aug 2026 09:00:00 +0000</pubDate>
      <description>Why the gap between wanting an outcome and having it survives every improvement in speed.</description>
    </item>
    <item>
      <title>State, not persona</title>
      <link>https://swarochish.com/notes#n09</link>
      <guid isPermaLink="true">https://swarochish.com/notes#n09</guid>
      <pubDate>Fri, 01 Aug 2026 09:00:00 +0000</pubDate>
      <description>Personas are a planning tool that quietly becomes a runtime model, and as a runtime model they are wrong in a particular way. They assign a person a fixed identity when the thing that actually varies is their situation.</description>
    </item>
    <item>
      <title>A warning will not fix a slip</title>
      <link>https://swarochish.com/notes#n08</link>
      <guid isPermaLink="true">https://swarochish.com/notes#n08</guid>
      <pubDate>Fri, 01 Aug 2026 09:00:00 +0000</pubDate>
      <description>Three kinds of failure, three different remedies, and applying the wrong one reliably fails. A slip is a correct intention executed wrongly, and it wants undo, forcing functions and better defaults. A mistake is a correct execution of a wrong intention, and it wants the mental model repaired rather </description>
    </item>
    <item>
      <title>Friction should be classified by what it produces</title>
      <link>https://swarochish.com/notes#n07</link>
      <guid isPermaLink="true">https://swarochish.com/notes#n07</guid>
      <pubDate>Fri, 01 Aug 2026 09:00:00 +0000</pubDate>
      <description>Friction is treated as a quantity to be reduced, which makes it impossible to reason about the friction that is doing work. Some of it produces nothing and should go. Some produces attention, deliberation, consent, skill or error containment, and removing it makes the system feel better and behave w</description>
    </item>
    <item>
      <title>Who absorbs what was removed</title>
      <link>https://swarochish.com/notes#n06</link>
      <guid isPermaLink="true">https://swarochish.com/notes#n06</guid>
      <pubDate>Fri, 01 Aug 2026 09:00:00 +0000</pubDate>
      <description>Simplification programmes are usually measured on the party that got simpler. That is the wrong side of the ledger. Complexity has a floor set by the task, and below that floor the only thing a system can do is move work from one party to another.</description>
    </item>
    <item>
      <title>A closed question is not a finished one</title>
      <link>https://swarochish.com/notes#n05</link>
      <guid isPermaLink="true">https://swarochish.com/notes#n05</guid>
      <pubDate>Fri, 01 Aug 2026 09:00:00 +0000</pubDate>
      <description>The mechanism that closed the natural language generation problem exists and is widely available. The next version of Sherlock my co-founder and I wanted is now possible.</description>
    </item>
    <item>
      <title>The answer arrived from somewhere else</title>
      <link>https://swarochish.com/notes#n04</link>
      <guid isPermaLink="true">https://swarochish.com/notes#n04</guid>
      <pubDate>Fri, 01 Aug 2026 09:00:00 +0000</pubDate>
      <description>Natural language generation was the weak link at Penser. Everything up to the finding worked. Saying the finding back to a person in ordinary language did not.</description>
    </item>
    <item>
      <title>Most enterprise architecture is an artefact of a vanishing constraint</title>
      <link>https://swarochish.com/notes#n03</link>
      <guid isPermaLink="true">https://swarochish.com/notes#n03</guid>
      <pubDate>Fri, 01 Aug 2026 09:00:00 +0000</pubDate>
      <description>The shape of business software was set when computation was expensive, integration was painful, and every capability had to arrive as a separate application with its own screens, its own data and its own login.</description>
    </item>
    <item>
      <title>Once and ten thousand times are different engineering problems</title>
      <link>https://swarochish.com/notes#n02</link>
      <guid isPermaLink="true">https://swarochish.com/notes#n02</guid>
      <pubDate>Fri, 01 Aug 2026 09:00:00 +0000</pubDate>
      <description>Doing something once tolerates a person watching, correcting, and quietly handling the case nobody anticipated. Doing it ten thousand times does not.</description>
    </item>
    <item>
      <title>Autonomy is earned, not granted</title>
      <link>https://swarochish.com/notes#n01</link>
      <guid isPermaLink="true">https://swarochish.com/notes#n01</guid>
      <pubDate>Fri, 01 Aug 2026 09:00:00 +0000</pubDate>
      <description>The permission a system holds should track the consequence of what it does. A summarisation can go wrong quietly and cheaply. A payment cannot. The more consequential the action, the more permissions, observability, determinism and reversibility the system needs before it acts unsupervised.</description>
    </item>
  </channel>
</rss>
