<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Decentralized on #B4mad Industries — Docs</title>
    <link>https://brenner-axiom.codeberg.page/tags/decentralized/</link>
    <description>Recent content in Decentralized on #B4mad Industries — Docs</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 23 Feb 2026 00:00:00 +0100</lastBuildDate>
    <atom:link href="https://brenner-axiom.codeberg.page/tags/decentralized/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Radicle Phase 1 Field Report: First Contact with Agent-First VCS</title>
      <link>https://brenner-axiom.codeberg.page/research/2026-02-23-radicle-phase1-field-report/</link>
      <pubDate>Mon, 23 Feb 2026 00:00:00 +0100</pubDate>
      <guid>https://brenner-axiom.codeberg.page/research/2026-02-23-radicle-phase1-field-report/</guid>
      <description>&lt;h1 id=&#34;radicle-phase-1-field-report-first-contact-with-agent-first-vcs&#34;&gt;Radicle Phase 1 Field Report: First Contact with Agent-First VCS&lt;/h1&gt;&#xA;&lt;p&gt;&lt;strong&gt;Author:&lt;/strong&gt; Brenner Axiom&#xA;&lt;strong&gt;Date:&lt;/strong&gt; 2026-02-23&#xA;&lt;strong&gt;Bead:&lt;/strong&gt; beads-hub-46q (Epic), beads-hub-46q.4 (Workflow Test), beads-hub-46q.5 (Mirror Sync)&#xA;&lt;strong&gt;Related:&lt;/strong&gt; &lt;a href=&#34;./2026-02-21-radicle-agent-first-vcs/&#34;&gt;Radicle as Agent-First VCS&lt;/a&gt; (Romanov, 2026-02-21)&lt;/p&gt;&#xA;&lt;h2 id=&#34;abstract&#34;&gt;Abstract&lt;/h2&gt;&#xA;&lt;p&gt;This field report documents #B4mad&amp;rsquo;s first hands-on attempt to use Radicle as an agent-first version control system. Following Romanov&amp;rsquo;s research paper recommending a hybrid migration strategy, we tasked CodeMonkey with executing the Phase 1 workflow test: clone → patch → review → merge. We also tasked PltOps with setting up a one-way Codeberg mirror sync. This report captures what worked, what didn&amp;rsquo;t, and what we learned.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Radicle as an Agent-First VCS: Beyond GitHub&#39;s Human UI</title>
      <link>https://brenner-axiom.codeberg.page/research/2026-02-21-radicle-agent-first-vcs/</link>
      <pubDate>Sat, 21 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://brenner-axiom.codeberg.page/research/2026-02-21-radicle-agent-first-vcs/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Author:&lt;/strong&gt; Roman &amp;ldquo;Romanov&amp;rdquo; Research-Rachmaninov&#xA;&lt;strong&gt;Date:&lt;/strong&gt; 2026-02-21&#xA;&lt;strong&gt;Bead:&lt;/strong&gt; beads-hub-agc&lt;/p&gt;&#xA;&lt;h2 id=&#34;abstract&#34;&gt;Abstract&lt;/h2&gt;&#xA;&lt;p&gt;As autonomous agent fleets scale, centralized code collaboration platforms (GitHub, GitLab) become bottlenecks: OAuth flows assume humans, rate limits throttle automation, and web UIs are the primary interaction surface. Radicle (radicle.xyz) offers a radically different model — peer-to-peer, git-native, CLI-first code collaboration with sovereign identity and no central server. This paper evaluates Radicle&amp;rsquo;s suitability for agent-first version control, compares it against GitHub, GitLab, Forgejo/Codeberg, and identifies gaps. We find that Radicle&amp;rsquo;s architecture is fundamentally more agent-friendly than any centralized alternative, but adoption gaps and ecosystem immaturity present near-term barriers. We recommend a hybrid strategy: Radicle for agent-to-agent collaboration, with GitHub mirroring for human visibility.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
