<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Political-Economy on emsenn.net</title>
    <link>https://emsenn.net/tags/political-economy/</link>
    <description>Recent content in Political-Economy on emsenn.net</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 07 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://emsenn.net/tags/political-economy/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Principal-Agent Problem</title>
      <link>https://emsenn.net/library/domains/humanities/domains/sociology/domains/critical-theory/domains/marxism/domains/political-economy/terms/principal-agent-problem/</link>
      <pubDate>Sat, 07 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://emsenn.net/library/domains/humanities/domains/sociology/domains/critical-theory/domains/marxism/domains/political-economy/terms/principal-agent-problem/</guid>
      <description>&lt;p&gt;The &lt;strong&gt;principal-agent problem&lt;/strong&gt; describes a governance structure&#xA;where one party (the principal) delegates work to another (the&#xA;agent), creating information asymmetry: the agent knows more about&#xA;their own actions than the principal can observe.&lt;/p&gt;&#xA;&lt;p&gt;In conventional project management, this structure is pervasive:&#xA;a manager (principal) defines objectives, and workers (agents)&#xA;execute them. Planning tools (Gantt charts, sprint backlogs,&#xA;standups) serve the principal&amp;rsquo;s need for visibility and control&#xA;over the agent&amp;rsquo;s behavior.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Dead Zone</title>
      <link>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/domains/internet/domains/activitypub/terms/dead-zone/</link>
      <pubDate>Tue, 03 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/domains/internet/domains/activitypub/terms/dead-zone/</guid>
      <description>&lt;p&gt;A dead zone is a term emsenn introduces within the &lt;a href=&#34;./standardization-as-counterinsurgency.md&#34; class=&#34;link-internal&#34;&gt;standardization as counterinsurgency&lt;/a&gt; framework to describe the end state of the &lt;a href=&#34;./domestication-paradox.md&#34; class=&#34;link-internal&#34;&gt;domestication&lt;/a&gt; trajectory. It names an infrastructure that is standardized, maintained, and institutionally visible — but that no longer serves as a site of innovation for either insurgent movements or dominant platforms.&lt;/p&gt;&#xA;&lt;h2 id=&#34;characteristics&#34;&gt;&lt;a href=&#34;#characteristics&#34; class=&#34;heading-anchor&#34; aria-label=&#34;Link to this section&#34;&gt;¶&lt;/a&gt;Characteristics&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;A dead zone infrastructure exhibits four properties simultaneously:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;High &lt;a href=&#34;../../../../../../../../humanities/domains/sociology/terms/legibility.md&#34; class=&#34;link-internal&#34;&gt;legibility&lt;/a&gt;.&lt;/strong&gt; It&amp;rsquo;s documented, standardized, and incorporated into reference architectures and regulatory frameworks. Institutions can &amp;ldquo;see&amp;rdquo; it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Domestication Paradox</title>
      <link>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/domains/internet/domains/activitypub/terms/domestication-paradox/</link>
      <pubDate>Tue, 03 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/domains/internet/domains/activitypub/terms/domestication-paradox/</guid>
      <description>&lt;p&gt;The Domestication Paradox is a concept emsenn develops within the &lt;a href=&#34;./standardization-as-counterinsurgency.md&#34; class=&#34;link-internal&#34;&gt;standardization as counterinsurgency&lt;/a&gt; framework. It names a specific structural irony: the process of making an &lt;a href=&#34;./insurgent-infrastructure.md&#34; class=&#34;link-internal&#34;&gt;insurgent infrastructure&lt;/a&gt; legible and safe for corporate adoption also undermines the social and cultural energies that would have made adoption worthwhile.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-mechanism&#34;&gt;&lt;a href=&#34;#the-mechanism&#34; class=&#34;heading-anchor&#34; aria-label=&#34;Link to this section&#34;&gt;¶&lt;/a&gt;The mechanism&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Domestication reshapes an insurgent infrastructure in three ways:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&lt;strong&gt;Tightening interfaces&lt;/strong&gt; — clarifying and narrowing what counts as &amp;ldquo;compliant&amp;rdquo; behavior, reducing space for divergent interpretations.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Decontextualizing goals&lt;/strong&gt; — recasting the infrastructure as a general-purpose tool (&amp;ldquo;a protocol for interoperable social activities&amp;rdquo;) rather than an instrument of a specific political project.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Repositioning control&lt;/strong&gt; — shifting de facto authority over interpretation and evolution from grassroots communities to standard editors, major implementers, and corporate participants.&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;From the corporate perspective, domestication looks attractive: the infrastructure becomes easier to integrate, explain to policymakers, and incorporate into compliance narratives. It reduces uncertainty and coordination costs.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Insurgent Infrastructure</title>
      <link>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/domains/internet/domains/activitypub/terms/insurgent-infrastructure/</link>
      <pubDate>Tue, 03 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/domains/internet/domains/activitypub/terms/insurgent-infrastructure/</guid>
      <description>&lt;p&gt;Insurgent infrastructure is a term emsenn introduces within the &lt;a href=&#34;./standardization-as-counterinsurgency.md&#34; class=&#34;link-internal&#34;&gt;standardization as counterinsurgency&lt;/a&gt; framework to name a specific kind of technical system: one that emerges from communities seeking to change the conditions imposed by existing platforms.&lt;/p&gt;&#xA;&lt;p&gt;An infrastructure is &lt;em&gt;insurgent&lt;/em&gt; when it scores high on generativity, autonomy support, and movement value, while its &lt;a href=&#34;../../../../../../../../humanities/domains/sociology/terms/legibility.md&#34; class=&#34;link-internal&#34;&gt;legibility&lt;/a&gt; and corporate extractable value are low or uncertain. Insurgent infrastructures are often messy, evolving, and embedded in local practices. Their meaning is tied to their role in a broader political and social project — building alternatives, resisting &lt;a href=&#34;../../../../../../../../humanities/domains/sociology/terms/enclosure.md&#34; class=&#34;link-internal&#34;&gt;enclosure&lt;/a&gt;, or experimenting with new governance forms.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Standardization as Counterinsurgency</title>
      <link>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/domains/internet/domains/activitypub/terms/standardization-as-counterinsurgency/</link>
      <pubDate>Tue, 03 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/domains/internet/domains/activitypub/terms/standardization-as-counterinsurgency/</guid>
      <description>&lt;p&gt;Standardization as counterinsurgency (SaC) is a framework emsenn develops to describe how standards bodies interact with &lt;a href=&#34;./insurgent-infrastructure.md&#34; class=&#34;link-internal&#34;&gt;insurgent infrastructures&lt;/a&gt; — technical systems that originate as challenges to the dominant platform order. The framework draws on &lt;a href=&#34;../../../../../../../../humanities/domains/general/domains/people/james-c-scott.md&#34; class=&#34;link-internal&#34;&gt;James C. Scott&lt;/a&gt;&amp;rsquo;s work on &lt;a href=&#34;../../../../../../../../humanities/domains/sociology/terms/legibility.md&#34; class=&#34;link-internal&#34;&gt;legibility&lt;/a&gt; and state-building, and on analyses of protocol as a form of soft power.&lt;/p&gt;&#xA;&lt;p&gt;The central claim: when a standards body engages with an insurgent infrastructure, the institutional logic of standardization — consensus-seeking, scope management, stakeholder alignment — tends to transform the infrastructure in ways that increase its &lt;a href=&#34;../../../../../../../../humanities/domains/sociology/terms/legibility.md&#34; class=&#34;link-internal&#34;&gt;legibility&lt;/a&gt; to dominant institutions while eroding its generativity, autonomy support, and movement value. This isn&amp;rsquo;t necessarily intentional. It&amp;rsquo;s a structural effect of the incentives and constraints that shape standards processes.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Standardization as Counterinsurgency</title>
      <link>https://emsenn.net/library/domains/engineering/domains/tech/texts/standardization-as-counterinsurgency/</link>
      <pubDate>Tue, 03 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://emsenn.net/library/domains/engineering/domains/tech/texts/standardization-as-counterinsurgency/</guid>
      <description>&lt;p&gt;This concept has a full treatment at &lt;a href=&#34;./standardization-as-counterinsurgency.md&#34; class=&#34;link-internal&#34;&gt;technology/concepts/internet/topics/activitypub/concepts/standardization-as-counterinsurgency&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;See also: &lt;a href=&#34;./internet/topics/activitypub/activitypub-insurrection-deadzone.md&#34; class=&#34;link-internal&#34;&gt;the full analytical essay&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ActivityPub: Institutional Capture of Insurgent Protocol</title>
      <link>https://emsenn.net/library/domains/humanities/domains/sociology/texts/activitypub-insurrection-deadzone/</link>
      <pubDate>Fri, 05 Dec 2025 00:00:00 +0000</pubDate>
      <guid>https://emsenn.net/library/domains/humanities/domains/sociology/texts/activitypub-insurrection-deadzone/</guid>
      <description>&lt;h2 id=&#34;1-introduction-from-insurgent-protocol-to-institutional-dead-zone&#34;&gt;&lt;a href=&#34;#1-introduction-from-insurgent-protocol-to-institutional-dead-zone&#34; class=&#34;heading-anchor&#34; aria-label=&#34;Link to this section&#34;&gt;¶&lt;/a&gt;1. Introduction: From Insurgent Protocol to Institutional Dead Zone&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;In the last decade, the “fediverse” has been widely promoted as a concrete manifestation of a different kind of social web: one built on federation rather than platform enclosure, local governance rather than global terms of service, and open protocols rather than proprietary APIs. At the center of this story sits ActivityPub, a protocol standardized at the World Wide Web Consortium (W3C) and frequently described as the technical backbone of decentralized social networking. Mastodon, the most visible ActivityPub-based platform, has become the public face of this alternative.&#xA;From the perspective of traditional web governance, ActivityPub looks like a success story. A grassroots set of practices and experiments coalesced into a protocol; the protocol was taken up by a major standards body; a flagship implementation gained substantial public recognition; large firms, including Meta, announced plans to integrate with it. The story appears to track the standard life-cycle of web technologies: experimental beginnings, formal consolidation, and eventual mainstream adoption.&#xA;Yet the trajectory of Meta’s Threads—its attempt to plug a large-scale commercial social network into ActivityPub and “join the fediverse”—complicates this narrative. Despite intensive publicity, regulatory interest in interoperability, and the symbolic weight of a major platform endorsing a W3C standard, Threads’ federation has so far failed to either (a) transform the fediverse into a profitable growth engine for Meta or (b) establish ActivityPub as a living, generative substrate for a new kind of social web. Federated support exists, but it is marginal to Threads’ core product. Many fediverse communities remain skeptical or actively hostile. The promise of a vibrant, open ecosystem lubricated by a neutral standard has not materialized.&#xA;This paper starts from that tension. Why does a protocol that appears to have successfully navigated the standards pipeline—and attracted the attention of one of the world’s largest platforms—produce such an anemic result, both politically and economically? Why does a success in the language of standards bodies (a W3C Recommendation, a large deployed base, corporate adoption) coincide with a sense that something has gone dead at the heart of the “open social web” project?&#xA;We argue that these outcomes are symptomatic of a deeper structural dynamic: standardization as counterinsurgency. By this we mean a patterned institutional response in which standards bodies absorb infrastructural projects that originate as challenges to the dominant platform order, translate them into narrow technical artifacts, and stabilize them in forms that are highly legible to corporate and regulatory actors but stripped of much of their generative and political force.&#xA;To develop this argument, we introduce three linked concepts:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Domestication Paradox</title>
      <link>https://emsenn.net/library/domains/humanities/domains/sociology/terms/domestication-paradox/</link>
      <pubDate>Fri, 05 Dec 2025 00:00:00 +0000</pubDate>
      <guid>https://emsenn.net/library/domains/humanities/domains/sociology/terms/domestication-paradox/</guid>
      <description>&lt;p&gt;The process that makes an insurgent infrastructure legible and safe for corporate adoption also erodes the social and cultural energies that would make integration worthwhile. After domestication, the infrastructure is technically easy to plug into but no longer anchors a vibrant ecosystem that wants to be plugged into.&lt;/p&gt;&#xA;&lt;p&gt;The paradox arises because corporate extractable value depends on &lt;em&gt;both&lt;/em&gt; legibility (which standardization increases) and generativity/movement value (which standardization tends to decrease). Firms pursue domestication to reduce risk, but risk reduction eliminates the reward.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
