<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Swartzism</title>
    <atom:link href="https://logicinczo.github.io/swartzism/feed.xml" rel="self" type="application/rss+xml"/>
    <link>https://logicinczo.github.io/swartzism/</link>
    <description>A doctrine of information power, built from the record of Aaron Swartz. Axioms, ethics of scale, and the PII boundary — applied to public records, paywalls, procurement, and accountability. Apersonal by design: the doctrine belongs to no author, only to a record and an argument.
</description>
    <pubDate>Wed, 14 Oct 2026 23:58:04 +0000</pubDate>
    
      <item>
        <title>Version 0.0.1: A Request for Comments</title>
        <link>https://logicinczo.github.io/swartzism/2026/10/version-0-0-1-a-request-for-comments/</link>
        <guid isPermaLink="true">https://logicinczo.github.io/swartzism/2026/10/version-0-0-1-a-request-for-comments/</guid>
        <description>&lt;p&gt;Today the doctrine ships — not as a finished thing, but as an opening position. Version 0.0.1 of Swartzism is published as a Request for Comments: five axioms, an ethics of scale, one boundary, five works, and a process for changing all of it except the last.&lt;/p&gt;

&lt;p&gt;Read &lt;a href=&quot;/swartzism/manifesto/&quot;&gt;the Manifesto&lt;/a&gt;. Then read &lt;a href=&quot;/swartzism/principles/&quot;&gt;the Principles&lt;/a&gt; — the analytical machine underneath: every claim about the record carries a source, and one fabricated citation has already been caught, corrected, and logged. Then read &lt;a href=&quot;/swartzism/governance/&quot;&gt;the Governance&lt;/a&gt; — how the text changes, what never changes, and why.&lt;/p&gt;

&lt;p&gt;Three commitments come with the version number:&lt;/p&gt;

&lt;ol&gt;
  &lt;li&gt;&lt;strong&gt;The boundary is constitutional.&lt;/strong&gt; Liberate the world’s knowledge; defend each person’s life. Everything else in the text is revisable by argument. The boundary is not revisable by coalition, cost-benefit, or mood.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;The text must survive its own attacks.&lt;/strong&gt; A version that has not survived a published attempt to destroy it is not stable, whatever its number. The review log is the doctrine eating its own cooking — and Pass 2 is now public business.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;No one owns it.&lt;/strong&gt; The doctrine is apersonal: arguments are judged, not authors. It publishes under its own name, takes help, not direction, and carries no signatures.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The profession test governs its texts: a doctrine that taxes its professors shrinks to a church of martyrs. This one intends to grow — which is why 0.0.1 is an invitation, not a proclamation.&lt;/p&gt;

&lt;p&gt;Attack it where it is weakest. &lt;a href=&quot;/swartzism/governance/&quot;&gt;That is what the comment process is for.&lt;/a&gt;&lt;/p&gt;
</description>
        <pubDate>Wed, 14 Oct 2026 00:00:00 +0000</pubDate>
      </item>
    
      <item>
        <title>The PII Question: How Swartzism Treats Data About People</title>
        <link>https://logicinczo.github.io/swartzism/2026/08/the-pii-question/</link>
        <guid isPermaLink="true">https://logicinczo.github.io/swartzism/2026/08/the-pii-question/</guid>
        <description>&lt;p&gt;The objection to any information-liberation doctrine writes itself: &lt;em&gt;if you’re for freeing data, you must be fine with leaking people’s data too.&lt;/em&gt; Swartzism answers with a boundary that does not move:&lt;/p&gt;

&lt;blockquote&gt;
  &lt;p&gt;&lt;strong&gt;Liberate the world’s knowledge. Defend each person’s life.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Data about the world and data about a person are different kinds of things. They are not both “data.” The doctrine is deliberately asymmetric about them.&lt;/p&gt;

&lt;h2 id=&quot;the-two-column-test&quot;&gt;The two-column test&lt;/h2&gt;

&lt;p&gt;Every data project, leak, or archive gets sorted into one of two columns:&lt;/p&gt;

&lt;table&gt;
  &lt;thead&gt;
    &lt;tr&gt;
      &lt;th&gt;Column&lt;/th&gt;
      &lt;th&gt;What it is&lt;/th&gt;
      &lt;th&gt;Swartzism’s rule&lt;/th&gt;
    &lt;/tr&gt;
  &lt;/thead&gt;
  &lt;tbody&gt;
    &lt;tr&gt;
      &lt;td&gt;World-data&lt;/td&gt;
      &lt;td&gt;Dockets, gazettes, scientific literature, corporate registries, government records&lt;/td&gt;
      &lt;td&gt;Liberate. The public cannot govern what it cannot inspect.&lt;/td&gt;
    &lt;/tr&gt;
    &lt;tr&gt;
      &lt;td&gt;Person-data&lt;/td&gt;
      &lt;td&gt;Names, biometrics, financial records, medical histories, locations, communications&lt;/td&gt;
      &lt;td&gt;Protect. The holder of this data holds power over the person it describes.&lt;/td&gt;
    &lt;/tr&gt;
  &lt;/tbody&gt;
&lt;/table&gt;

&lt;p&gt;The first question about any contested dataset is not &lt;em&gt;“should this be public?”&lt;/em&gt; — it is &lt;em&gt;“who does this data describe?”&lt;/em&gt; The test is not “was this information obtained legally?” — the &lt;a href=&quot;https://en.wikipedia.org/wiki/Aaron_Swartz#PACER_case&quot;&gt;PACER download&lt;/a&gt; was a Terms-of-Service violation, and Swartzism still treats it as justified. The test is: whose data is it, and what does exposing it do to the person it describes?&lt;/p&gt;

&lt;h2 id=&quot;why-the-boundary-is-load-bearing&quot;&gt;Why the boundary is load-bearing&lt;/h2&gt;

&lt;p&gt;The doctrine has no chance without trust. Institutions will always argue that openness is a slippery slope to surveillance. Every time someone calling themselves a “liberator” dumps ordinary people’s data, they prove the institutions right. The boundary is not a policy choice within Swartzism; it is the load-bearing wall of the whole argument. It does not move.&lt;/p&gt;

&lt;p&gt;The asymmetry is the point, not an inconsistency: &lt;strong&gt;the powerful’s secrets are ours to expose; the weak’s data is theirs to keep.&lt;/strong&gt; A custodian who hoards knowledge is the enemy. A liberator who leaks lives is worse.&lt;/p&gt;

&lt;h2 id=&quot;leaks-that-fail-the-test&quot;&gt;Leaks that fail the test&lt;/h2&gt;

&lt;p&gt;Consider a leaked customer database: millions of bank records, phone numbers, and addresses dumped to the open internet. The thief may call it “exposure.” Swartzism calls it what it is — &lt;strong&gt;the transfer of personal data from one holder to a thousand holders&lt;/strong&gt;, each of whom can now impersonate, defraud, harass, or sell. &lt;sup id=&quot;fnref:1&quot; role=&quot;doc-noteref&quot;&gt;&lt;a href=&quot;#fn:1&quot; class=&quot;footnote&quot; rel=&quot;footnote&quot;&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;

&lt;p&gt;A PII leak is not civil disobedience. Civil disobedience targets a structure of power; a PII dump targets the people the structure was already mistreating. It amplifies the harm rather than dismantling the cause. The victims of a bank or Aadhaar-style breach are not the institution — the institution has already been paid to care. The victims are the account holders whose data now circulates as currency in fraud markets.&lt;/p&gt;

&lt;p&gt;When a leak of personal data surfaces, the doctrine’s instruction is clear:&lt;/p&gt;

&lt;ol&gt;
  &lt;li&gt;&lt;strong&gt;Do not redistribute.&lt;/strong&gt; Not one row. The data describes persons; propagation is the second harm.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Work for takedown and remediation.&lt;/strong&gt; The affected people come first.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Strike the system that collected and exposed it.&lt;/strong&gt; Investigate the custodian, the contract, the security failures, the regulator asleep at the switch. That is where the accountability work lives — in the &lt;em&gt;system&lt;/em&gt;, not in the rows.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;This is not timidity; it is the boundary working as designed. The research targets the leak as an event — who collected it, how it was secured, who failed, who profited. Never the people inside it.&lt;/p&gt;

&lt;h2 id=&quot;the-hard-case-accountability-data-about-the-powerful&quot;&gt;The hard case: accountability data about the powerful&lt;/h2&gt;

&lt;p&gt;There is one genuinely hard case: official misconduct that is &lt;em&gt;only provable through personal data&lt;/em&gt;. A minister’s abuse documented via records that include personal details.&lt;/p&gt;

&lt;p&gt;The line has to be drawn per-case. A police officer’s substantiated misconduct finding is a public record about the exercise of public power; publishing it is world-data. &lt;sup id=&quot;fnref:2&quot; role=&quot;doc-noteref&quot;&gt;&lt;a href=&quot;#fn:2&quot; class=&quot;footnote&quot; rel=&quot;footnote&quot;&gt;2&lt;/a&gt;&lt;/sup&gt; The same officer’s home address, family, or financial details are person-data; publishing them is a target painted on a human being. The difference is the difference between the badge and the man. Swartzism holds the line at the badge.&lt;/p&gt;

&lt;p&gt;Where release is the only path to accountability, the doctrine permits it only when all four conditions hold:&lt;/p&gt;

&lt;ol&gt;
  &lt;li&gt;&lt;strong&gt;Imminence and gravity&lt;/strong&gt; — the harm being exposed is ongoing or severe;&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Minimality&lt;/strong&gt; — the least personal data that proves the act;&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Asymmetry&lt;/strong&gt; — the subject holds power over the people affected;&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Process&lt;/strong&gt; — a documented proportionality decision by more than one person, reviewable later.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The purpose of these conditions is not to block release. It is to make the release &lt;em&gt;defensible&lt;/em&gt; — because an accountability act that harms the innocent discredits the doctrine, not just the act.&lt;/p&gt;

&lt;h2 id=&quot;the-consequence&quot;&gt;The consequence&lt;/h2&gt;

&lt;p&gt;This is why Swartzism is not “piracy with a sad story attached,” and why it is not naive about power. It takes a side that confuses both the corporate enforcer and the careless “liberator”: knowledge of the world is a commons, and the privacy of persons is absolute — and the two commitments are one doctrine, not two.&lt;/p&gt;

&lt;p&gt;That discipline is what lets the practice projects — the police-accountability archive, the hospital registry audit, the exam-tech investigation — do their work without becoming part of the problem they document.&lt;/p&gt;

&lt;p&gt;The next stress test: what happens when the two columns collide inside a single system — an Aadhaar, a UPI, a national registry. That is where the doctrine meets Indian DPI, and where it will have to earn its keep.&lt;/p&gt;

&lt;div class=&quot;footnotes&quot; role=&quot;doc-endnotes&quot;&gt;
  &lt;ol&gt;
    &lt;li id=&quot;fn:1&quot; role=&quot;doc-endnote&quot;&gt;
      &lt;p&gt;https://en.wikipedia.org/wiki/Data_breach &lt;a href=&quot;#fnref:1&quot; class=&quot;reversefootnote&quot; role=&quot;doc-backlink&quot;&gt;&amp;#8617;&lt;/a&gt;&lt;/p&gt;
    &lt;/li&gt;
    &lt;li id=&quot;fn:2&quot; role=&quot;doc-endnote&quot;&gt;
      &lt;p&gt;https://www.aaronswartzday.org/bad-apple-announcement/ &lt;a href=&quot;#fnref:2&quot; class=&quot;reversefootnote&quot; role=&quot;doc-backlink&quot;&gt;&amp;#8617;&lt;/a&gt;&lt;/p&gt;
    &lt;/li&gt;
  &lt;/ol&gt;
&lt;/div&gt;
</description>
        <pubDate>Mon, 03 Aug 2026 12:30:00 +0000</pubDate>
      </item>
    
      <item>
        <title>What Is Swartzism?</title>
        <link>https://logicinczo.github.io/swartzism/2026/08/what-is-swartzism/</link>
        <guid isPermaLink="true">https://logicinczo.github.io/swartzism/2026/08/what-is-swartzism/</guid>
        <description>&lt;p&gt;The word does not exist in the record. Aaron Swartz never named a movement, never wrote a manifesto that founded an “-ism”, never claimed disciples. “Swartzism” is a construction — a name for the question: &lt;strong&gt;what does the record imply?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;So the honest opening move is to define the term the way this blog will use it, and then say what it is &lt;em&gt;not&lt;/em&gt;.&lt;/p&gt;

&lt;h2 id=&quot;the-raw-material&quot;&gt;The raw material&lt;/h2&gt;

&lt;p&gt;Swartz left behind an unusually legible body of work: essays on &lt;a href=&quot;http://www.aaronsw.com/weblog/&quot;&gt;Raw Thought&lt;/a&gt; written between 2002 and his death in 2013, the &lt;a href=&quot;https://archive.org/details/GuerillaOpenAccessManifesto&quot;&gt;Guerrilla Open Access Manifesto&lt;/a&gt; (2008), the open-access advocacy, the &lt;a href=&quot;https://en.wikipedia.org/wiki/Aaron_Swartz#PACER_case&quot;&gt;PACER protest&lt;/a&gt; with Carl Malamud, the JSTOR mass download of 4.8 million articles that led to his prosecution and suicide, and the &lt;a href=&quot;https://github.com/joshleitzel/rawthought&quot;&gt;Semmelweis essay&lt;/a&gt; on how hard it is to see what is in front of you. (The &lt;a href=&quot;https://www.aaronswartzday.org/bad-apple-announcement/&quot;&gt;Bad Apple&lt;/a&gt; police-accountability tool suite, launched in 2021 by the Aaron Swartz Day Police Surveillance Project, carries his name and ethos — a separate project, built in his memory.)&lt;/p&gt;

&lt;p&gt;A doctrine built from this record has to be built &lt;em&gt;from&lt;/em&gt; it: every claim traceable to a source, every failure admitted.&lt;/p&gt;

&lt;h2 id=&quot;three-axioms-one-boundary&quot;&gt;Three axioms, one boundary&lt;/h2&gt;

&lt;p&gt;The doctrine this blog will argue for rests on three claims and one boundary.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Knowledge about the world is a commons.&lt;/strong&gt; Facts, laws, research, records — these are produced collectively and their enclosure is a harm. The &lt;a href=&quot;https://archive.org/details/GuerillaOpenAccessManifesto&quot;&gt;manifesto&lt;/a&gt; was about scientific literature, but the logic extends: when a society’s own records (court filings, gazettes, registries) are priced and gated, the society is taxing itself on its own memory.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Information is power, and power must be accountable.&lt;/strong&gt; The PACER action treated the &lt;em&gt;free flow&lt;/em&gt; of judicial records as a form of accountability. The Bad Apple project treated the &lt;em&gt;documentation&lt;/em&gt; of police misconduct as accountability. Information-as-power cuts both ways: it is why institutions hoard it, and why publics should pry it loose.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Privacy is a power too — held by the powerless.&lt;/strong&gt; This is the boundary, and it is load-bearing. Data &lt;em&gt;about persons&lt;/em&gt; is not a commons. The person described has a claim that the institution describing them does not. When a leak contains personal data, the doctrine’s instruction is not “liberate it” — it is &lt;em&gt;protect it, and investigate the system that leaked it.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;That last point is the one people get wrong about Swartzism, so it deserves its own post. &lt;a href=&quot;/swartzism/2026/08/the-pii-question/&quot;&gt;Read it next&lt;/a&gt;.&lt;/p&gt;

&lt;h2 id=&quot;what-swartzism-is-not&quot;&gt;What Swartzism is not&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Not hagiography.&lt;/strong&gt; Swartz was &lt;a href=&quot;https://en.wikipedia.org/wiki/Aaron_Swartz#Arrest_and_prosecution&quot;&gt;arrested in 2011 after a physical confrontation&lt;/a&gt; over a hidden camera at an MIT network closet — an escalation that did not serve his cause. A doctrine that requires its subject to be flawless is an idol, not an argument. The record includes the failures; the argument has to survive them.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Not “steal everything.”&lt;/strong&gt; The boundary above is the entire point. Swartzism without the PII boundary is just piracy with a sad story attached.&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Not a cult.&lt;/strong&gt; No membership, no orthodoxy, no leader. An argument that can be stress-tested is the only kind worth having.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The name is a convenience. The argument is the thing.&lt;/p&gt;
</description>
        <pubDate>Mon, 03 Aug 2026 12:25:00 +0000</pubDate>
      </item>
    
  </channel>
</rss>
