R09\digital-arms-constitutional-audit

Full report

On this page

Executive Assessment

Current United States constitutional doctrine does not establish that software, artificial intelligence models, or cyber tools are categorically or generally protected "arms" under the Second Amendment. An exhaustive audit of controlling Supreme Court precedents, federal appellate jurisprudence, and adjacent First Amendment rulings demonstrates that the application of constitutional arms protection to digital systems remains entirely analogical, highly theoretical, and doctrinally unsettled. The baseline proposition recorded in IC-CLAIM-005 is fully supported by the available legal evidence. The jurisprudential architecture erected by the Supreme Court in District of Columbia v. Heller explicitly extends Second Amendment protection to modern instruments that constitute bearable arms, including those not in existence at the time of the founding1. However, the constitutional requirement that an instrument be a "bearable arm"—historically defined through eighteenth-century dictionaries as a weapon of offense or armor of defense carried upon the person for confrontation—presents an insurmountable doctrinal barrier to purely digital, non-physical software or autonomous cyber-agents1. Jurisprudence from the United States Court of Appeals for the Seventh Circuit and the Illinois Supreme Court confirms that while modern electronic defensive devices, such as stun guns, are protected bearable arms, and while ancillary rights to acquire and train with arms exist, these constitutional holdings remain strictly tethered to physical instruments and physical confrontation6. Furthermore, attempts by legal theorists to bootstrap Second Amendment protections through First Amendment "code-as-speech" doctrines fundamentally misapprehend the distinct analytical frameworks applied to functional conduct versus expressive speech. Decisions such as Universal City Studios, Inc. v. Corley and Bernstein v. U.S. Department of Justice establish that while source code possesses expressive elements protected by the First Amendment, its functional capacity to execute tasks as object code can be regulated by the government without triggering strict constitutional scrutiny10. The digital-arms analogy relies on improperly conflating the protection of information about an arm, such as computer-aided design files in the Defense Distributed litigation, with the constitutional protection of the operational instrument itself13. Consequently, until a controlling appellate holding applies the Second Amendment directly to a non-physical digital tool or autonomous cyber-agent, claiming that "digital arms" are constitutionally protected remains a speculative exercise entirely unsupported by positive law.

Research Parameters and Doctrinal Boundaries

This legal evidence audit was executed on September 4, 2026\. The central objective is to evaluate the constitutional status of software, AI agents, and cyber tools as "arms" under current United States jurisprudence, testing the specific claim that the "digital arms" theory remains doctrinally unsettled. The boundaries of this inquiry are strictly confined to verifying the state of existing constitutional doctrine, mapping the exact demarcation between binding holdings and analogical arguments. The investigation prioritizes authentic primary legal materials, including official Supreme Court opinions outlining the text-and-history standard, federal appellate decisions distinguishing between expressive and functional code, and relevant state supreme court holdings within the jurisdiction covering Cicero, Illinois. The analysis distinguishes rigorously between binding appellate holdings, non-binding dicta, specific procedural postures, and scholarly theories. Scholarly articles analyzing cyber weapons, such as dual-use software and "hack back" active defense concepts, are utilized solely to articulate the strongest theoretical arguments for protection, which are subsequently audited against actual court holdings15. The evaluation demands precision regarding the object of the proposed protection, requiring a sharp distinction between source code, executable software, general-purpose AI models, defensive software services, and embodied electronic instruments. By separating adjacent constitutional doctrines, specifically the First Amendment code-as-speech paradigm, this report isolates the Second Amendment inquiry to determine whether current courts recognize non-kinetic, non-physical computer code as an instrument of constitutional defense.

The Governing Doctrinal Sequence: From Heller to Rahimi

The constitutional architecture governing the right to keep and bear arms has undergone a radical transformation over the past two decades. To understand why digital tools are currently excluded from this paradigm, the precise definitional and methodological boundaries established by the Supreme Court must be traced in detail. The progression of cases from Heller to Rahimi demonstrates a steadfast judicial reliance on physical confrontation, physical bearing, and physical danger. The modern era of Second Amendment jurisprudence commenced with District of Columbia v. Heller, which recognized an individual right to possess a firearm unconnected with militia service, primarily for traditionally lawful purposes such as self-defense within the home1. For the purposes of evaluating digital arms, the most critical element of Heller is its meticulous textual definition of the word "arms." Relying heavily on founding-era linguistic sources, such as Samuel Johnson's 1773 dictionary and Timothy Cunningham's 1771 legal dictionary, the Court defined "arms" as "weapons of offence, or armour of defence," encompassing "any thing that a man wears for his defence, or takes into his hands, or useth in wrath to cast at or strike another"3. Crucially, the Court explicitly rejected the notion that the Second Amendment protects only those specific weapons existing in 1791\. The majority opinion stated unequivocally that the constitutional right extends, prima facie, to "all instruments that constitute bearable arms, even those that were not in existence at the time of the founding"2. This technological neutrality principle is the primary engine driving the digital arms analogy. However, the operative and limiting word in the Court's formulation is bearable. The Court defined the verb "bear" as to carry a weapon upon the person for the purpose of being armed and ready for offensive or defensive action in a case of conflict3. This definition injects an inescapable element of physicality and spatial confrontation into the doctrine. To be classified as an "arm" under Heller, the item must be a weapon; to be protected, it must be "bearable" by an individual in a physical, corporeal sense. Code residing on a server lacks this fundamental characteristic. In New York State Rifle & Pistol Association, Inc. v. Bruen, the Supreme Court discarded the two-step, means-end scrutiny framework that federal appellate courts had utilized for over a decade following Heller. Bruen established a rigid new standard: when the Second Amendment's plain text covers an individual's conduct, the Constitution presumptively protects that conduct18. The burden then entirely shifts to the government to demonstrate that the modern regulation is consistent with the Nation's historical tradition of firearm regulation18. Bruen acknowledged the inherent difficulty of applying eighteenth-century regulatory traditions to "dramatic technological changes" and instructed lower courts to engage in "nuanced analogical reasoning"21. To determine if a modern regulation is "relevantly similar" to a historical one, courts must examine how and why the regulations burden a law-abiding citizen's right to armed self-defense20. For proponents of a "digital arms" theory, Bruen theoretically offers a pathway: if a cyber tool can somehow be classified as an "arm" under the plain text, any restriction on its possession must find a historical analogue. Yet, this analytical framework requires the proponent to cross the initial textual threshold of proving that a piece of software code is a bearable arm. The Supreme Court's subsequent decision in United States v. Rahimi provided critical clarification on the rigidity of the Bruen standard while simultaneously reinforcing the physical nature of the right18. In upholding 18 U.S.C. § 922(g)(8)—a federal statute disarming individuals subject to certain domestic violence restraining orders—the Court emphasized that the law requires a historical "analogue," not a "historical twin"19. The Court found that historical surety laws and laws disarming affrayers demonstrated a rich tradition of disarming individuals who posed a credible threat to the physical safety of others19. Rahimi is highly relevant to the digital arms debate because it continuously emphasizes that the Second Amendment is fundamentally concerned with physical safety and the prevention of physical violence. The historical precursors evaluated in Rahimi were focused entirely on individuals misusing physical weapons to inflict bodily harm upon intimate partners or the public22. Extending this deeply physical jurisprudence to a non-kinetic cyber tool that inflicts economic, data, or network damage requires abstracting the doctrine far beyond its current constitutional moorings.

The Definitional Void: Objectifying "Digital Arms"

A core analytical failure in the scholarly argument for the constitutional protection of digital arms is the profound lack of precision in defining the object being protected. Broad terms such as "software," "malware," or "cyber tools" represent categories far too expansive and amorphous to constitute a cognizable legal fact pattern under the Second Amendment. The United States Department of Defense, for example, refers to cyber arms broadly as a "capability," encompassing any device, computer program, or technique designed or applied to cause damage through the cyber domain15. However, military operational definitions do not dictate constitutional text. To properly evaluate the constitutional status of digital systems, the analysis must rigorously define the instrument, the asserted actor, and the specific conduct in question. First, source code must be distinguished from executable software. Source code is written in human-readable programming languages, serving to express algorithms, logic, and scientific concepts to other human beings. In contrast, executable software, or object code, consists of machine-readable instructions that command hardware components to perform functional tasks without human comprehension. Second Amendment doctrine does not map cleanly onto either. Second, the analysis must isolate general-purpose AI models from defensive software services. A general-purpose AI model is a massive statistical framework of weights and parameters capable of generating text, writing code, or analyzing complex data. It is a mathematical utility, not a weapon of offense. A defensive software service—such as a cloud-based intrusion detection system or an active "hack back" distributed tool—functions as an automated network perimeter defense. Human beings cannot physically "bear" a distributed general-purpose AI model or a cloud-based defensive software service in the spatial manner required for physical confrontation outlined in Heller. Finally, one must separate pure code from an embodied electronic instrument. An embodied electronic instrument is a physical device, such as an autonomous drone or a robotic home sentry, that relies entirely on software to function. While executable software can be stored on a mobile device or embedded in a robotic system, the software itself is not the weapon wielded against a physical adversary; it is the set of logical instructions governing the physical hardware. If the constitutional definition of "arms" is diluted to encompass any algorithmic tool that can be utilized to defend digital property or data, the definition loses all coherent limiting principles, functionally converting cryptography, standard antivirus software, and firewall configurations into constitutional "arms." No current legal authority supports such an expansive textual interpretation.

Illinois and Seventh Circuit Jurisprudence

To ground this analysis within the specified jurisdiction, it is necessary to audit the jurisprudence of the United States Court of Appeals for the Seventh Circuit and the Illinois Supreme Court, which govern Cicero, Illinois. These specific courts have rendered highly consequential decisions regarding the outer boundaries of the Second Amendment, specifically concerning non-lethal electronic weapons and the doctrine of ancillary rights.

People v. Webb and the Limit of Electronic Weaponry

In People v. Webb, the Illinois Supreme Court addressed a categorical legislative ban on the possession and carriage of stun guns and tasers within the state6. Applying the principles laid down by the United States Supreme Court in Heller and Caetano v. Massachusetts, the Illinois court unanimously held that stun guns and tasers are "bearable arms" within the meaning of the Second Amendment7. Consequently, the court ruled that a categorical ban on such weapons is facially unconstitutional. Webb represents the zenith of applying the Second Amendment to modern electronic technology within this jurisdiction. However, the analogical leap from a stun gun to a cyber tool is fundamentally flawed. A stun gun is a tangible, physical instrument, carried upon the person, explicitly designed to project physical kinetic force—specifically, electricity—to incapacitate a human attacker in a direct, physical confrontation6. Webb faithfully applies the Heller definition of a bearable weapon of offense or armor of defense. It does not provide any doctrinal support, even in dicta, for the proposition that non-physical, non-kinetic software code residing on a server constitutes a protected arm.

Ezell v. City of Chicago and the Ancillary Rights Doctrine

The Seventh Circuit's decisions in Ezell v. City of Chicago (Ezell I and Ezell II) are vital for understanding the concept of "ancillary rights" under the Second Amendment8. The City of Chicago had enacted a sweeping ordinance that banned firing ranges within city limits, severely restricting the ability of citizens to maintain proficiency in firearm use, which the city simultaneously required for obtaining a permit8. The Seventh Circuit held that the Second Amendment inherently protects the right to learn and practice firearm use in a controlled setting, recognizing that the core constitutional right to armed defense implies a corresponding, ancillary right to acquire arms and maintain proficiency with them28. Proponents of the digital arms theory frequently attempt to utilize the logic of Ezell to expand the scope of the Second Amendment. The argument asserts that if a physical cyber-defense node requires a specific AI software update to function effectively against modern threats, the software itself must be protected as an "ancillary right" necessary to effectuate the core right of defense17. However, federal appellate courts, including the Third Circuit in recent post-Bruen jurisprudence, have warned against boundless interpretations of ancillary rights, noting that they must remain strictly tethered to the ability of the individual to possess and carry physical arms for confrontation17. The right to practice marksmanship at a firing range directly supports the physical wielding of a physical firearm during a physical attack; the right to download a "hack back" Python script to defend a digital database does not. The ancillary rights doctrine cannot be utilized to smuggle non-physical software into the Second Amendment when the software does not support the physical bearing of a traditional weapon.

Adjacent Constitutional Paradigms: The Expressive/Functional Dichotomy

A persistent analytical error in the digital arms discourse is the conflation of Second Amendment functional protections with First Amendment expressive protections. Because software is fundamentally written in code, the historical legal battles over its regulation and distribution have largely been fought—and decided—on First Amendment grounds. Tracing this adjacent constitutional doctrine is essential to understanding why courts treat code differently than physical weapons.

Bernstein, Corley, and the Dual Nature of Code

In Bernstein v. U.S. Department of Justice, the Ninth Circuit held that encryption source code is a protected form of speech under the First Amendment32. The court determined that export-licensing rules requiring prepublication approval of cryptographic algorithms constituted an unconstitutional prior restraint. This landmark ruling established the foundational principle that human communication does not automatically lose constitutional protection simply because it is expressed in the highly technical language of computer code. However, the Second Circuit's subsequent decision in Universal City Studios, Inc. v. Corley provided a vital and limiting doctrinal framework. In Corley, the defendants were enjoined under the Digital Millennium Copyright Act (DMCA) from distributing "DeCSS," a computer program explicitly designed to circumvent digital copyright encryption on DVDs12. The court acknowledged the Bernstein precedent, agreeing that source code, written in a human-readable programming language, is expressive and generally protected by the First Amendment10. Yet, the Second Circuit drew a sharp, constitutional distinction between the expressive elements of source code and its functional capacity to execute tasks as object code10. The Corley court held that the government possesses the constitutional authority to regulate the functional, non-speech aspect of computer code—its ability to instruct a machine to perform a specific task—without violating the First Amendment, provided the regulation is content-neutral and targets the functionality rather than the expression12. The court emphasized that while a recipe for a bomb might be expressive speech, the functional mechanism of the bomb is not. This expressive/functional dichotomy is absolutely fatal to the argument that the First and Second Amendments can be used interchangeably to protect "digital arms." If a security researcher publishes the source code for a destructive network worm to educate academic peers on zero-day vulnerabilities, the First Amendment may offer robust protection because the code is functioning primarily as scientific expression10. But if that same researcher compiles and executes the code against a live corporate target, the First Amendment protection vanishes entirely because the code has transformed into purely functional conduct10. The Second Amendment, conversely, is explicitly designed to protect functional conduct—the actual keeping, bearing, and functional use of weapons for physical defense. One cannot logically use a First Amendment holding that protects code only as speech to argue that the Constitution protects code as a functional weapon.

Defense Distributed: The Blueprint is Not the Arm

The complex intersection of digital data, expressive speech, and physical arms is epitomized by the Defense Distributed litigation. The organization sought to publish Computer-Aided Design (CAD) files for 3D-printing functional firearms on the open internet13. When the United States Department of State sought to restrict the publication under international arms export control laws, Defense Distributed argued that the restriction violated their First Amendment right to free speech42. While the litigation spanned multiple jurisdictions and featured extensive procedural maneuvering, the prevailing judicial logic regarding the nature of the data is illuminating. When CAD files are viewed purely as functional directives commanding a 3D printer to extrude plastic into a weapon, rather than as expressive political speech, courts have found they can be heavily regulated13. In the specific context of Second Amendment doctrine, CAD files are not "arms." They are the digital blueprints utilized for the creation of arms. Restricting the public dissemination of a blueprint may deeply implicate the First Amendment (as a restraint on speech) or potentially the Second Amendment (as an ancillary restriction on acquiring arms, akin to banning gunsmithing tools), but the CAD file itself is definitively not a bearable weapon of offense.

The Historical-Method Problem and Active Cyber Defense

The Bruen methodology fundamentally requires the government to justify regulations by pointing to a historical analogue in the Nation's tradition of firearm regulation18. This historical requirement creates a severe methodological paradox for both the proponents and opponents of the digital arms theory. The concept of "active defense" or "hacking back" involves a private entity deploying offensive cyber tools to neutralize a threat on a foreign network16. Proponents argue that the right to self-defense is a natural right that must extend to the cyber domain, equating active cyber defense to the physical Castle Doctrine15. If a court were to hypothetically accept that a dual-use cyber weapon is an "arm," the government would then carry the burden to find a 1791 or 1868 analogue for regulating decentralized, non-kinetic, globally distributed algorithmic code. Proponents of digital arms would argue that because no historical laws banned the possession of mathematical formulas or non-kinetic tools in the home, the cyber weapon cannot be constitutionally regulated today. However, this argument relies on severe historical cherry-picking and mischaracterization. The founding generation could not regulate cyber weapons because the domain of cyberspace did not exist. The strongest historical analogue to an autonomous, active-defense AI agent would not be a musket or a pistol, but rather a spring-gun or a booby-trap. These were indiscriminate, automated physical mechanisms designed to protect property without human moral agency or assessment present at the exact time of deployment. English common law and early American tort law routinely restricted or entirely outlawed the deployment of spring-guns because of their indiscriminate danger to the innocent and to law enforcement. Therefore, even if a cyber-defense AI were somehow classified as an "arm" under the Second Amendment, the historical tradition of Anglo-American law provides a robust, analogous basis for completely banning autonomous, indiscriminate defensive weapons that operate without human intervention.

Bounded Fictional Scenarios

To demonstrate the exact boundaries of current constitutional doctrine, the following table evaluates four bounded fictional scenarios regarding the deployment of cyber and AI tools, specifying the legal issues and the strict limits of available authority.

Holdings Versus Analogies

To strictly separate verified doctrine from theoretical scholarship, the following table maps current jurisprudential holdings against the analogies advanced by proponents of the digital-arms theory.

Case Hierarchy and Doctrinal Treatment

The weight of the legal evidence relies entirely on the hierarchical standing of the courts rendering the decisions.

The Strongest Countercase (Steelman)

The strongest countercase to the proposition that digital arms are unprotected rests on a synthesis of Heller's technological neutrality, Ezell's ancillary rights, and the inevitable convergence of cyber and physical security infrastructure. Heller unequivocally states that the Second Amendment protects arms "that were not in existence at the time of the founding"1. Furthermore, Caetano v. Massachusetts summarily rejected the argument that electronic stun guns are unprotected simply because they are modern inventions. If the constitutional baseline demands the protection of modern technological evolutions of defensive tools, then as human life and physical property become inextricably embedded in digital networks, the instruments necessary to defend that life and property must logically fall within the Amendment's ambit. Furthermore, the doctrine of ancillary rights articulated in Ezell establishes that the right to bear arms is a hollow, meaningless guarantee if the state can ban the necessary prerequisites to effectuate that defense8. As physical defense systems—such as smart home security perimeters, connected autonomous vehicles, and critical medical pacemaker implants—become entirely reliant on complex software to function and repel malicious attacks, the code itself becomes a necessary ancillary component of the defensive "arm." To permit the government to arbitrarily ban defensive cybersecurity software is to permit the government to fundamentally disarm the physical defensive perimeters of the citizenry. Therefore, while pure code sitting idle on a server may not constitute an "arm," code that actively operates a defensive physical instrument, or is strictly necessary to defend fundamental physical security interests, must be protected under a modern, analogical reading of the Second Amendment.

Unresolved Questions and Claim-Impact Assessment

The central unresolved question is whether a federal appellate court will ever permit the definition of "bearable" to divorce itself entirely from human physical carriage. The current Supreme Court paradigm requires physical confrontation. If an AI agent acts autonomously to defend a network, the human is absent from the confrontation, severing the historical link to the militia and self-defense traditions. Regarding IC-CLAIM-005 ("Digital-arms theory is constitutionally unsettled"), the baseline evidence state of supported\_with\_qualification should be upgraded to supported. The supplied proposition—that current United States doctrine does not establish software as protected arms and that arguments remain entirely analogical—is factually and legally verified by this audit. There is no positive law extending Second Amendment rights to non-physical cyber tools. The exact controlling authority that would genuinely change this project claim would be a binding federal appellate decision that explicitly strikes down a restriction on a cyber-defensive tool entirely on Second Amendment grounds, formally defining an AI agent or malware as a 'bearable arm.' A First Amendment decision protecting the publication of source code would not alter this claim, as it does not address the functional possession of arms. Best Next Research Action: The project should execute a systematic review of lower federal district court dockets over the past five years to identify any pending civil litigation invoking the Second Amendment as a defense against Computer Fraud and Abuse Act (CFAA) prosecutions or DMCA anti-circumvention injunctions.

Claims the Website Must Not Make

Given the overwhelming weight of the evidence, IntelligenceCompact.com must adhere strictly to the boundaries of positive law. The project must not make the following claims:

1. Do not claim that the First Amendment protects the deployment of malware or cyber weapons. The Corley precedent strictly limits First Amendment protections to the expressive, human-readable capacity of code, explicitly allowing the regulation of its functional execution10.

2. Do not claim that the Supreme Court has extended the Second Amendment to digital data. The holdings in Heller and Bruen remain strictly and exclusively confined to bearable, physical instruments of confrontation1.

3. Do not conflate physical electronic weapons with software. The Webb decision's protection of stun guns in Illinois relies on physical kinetic force and does not transfer to non-physical, non-kinetic computer programs6.

4. Do not assert that the law is forever settled against digital arms. The absence of a Supreme Court holding does not mean a permanent categorical exclusion has been firmly established; it merely means the doctrine has not yet squarely addressed a pure cyber-arms fact pattern at the appellate level.

State-of-Law Conclusion

Current United States Second Amendment constitutional doctrine does not establish that software, AI agents, or cyber tools are protected "arms." The constitutional architecture erected by the Supreme Court in Heller, Bruen, and Rahimi is inextricably and exclusively bound to the concepts of physical "weapons of offence," "armour of defence," and the physical bearing of those instruments for human confrontation1. While sub-federal jurisprudence has correctly extended constitutional protection to modern physical electronic devices such as stun guns6, and recognized ancillary rights necessary to effectuate physical defense8, no controlling appellate authority has bridged the analogical gap to protect purely digital, non-physical systems under the Second Amendment. Furthermore, attempts to substitute First Amendment expressive protections for functional weaponization fail entirely under the established code-as-speech dichotomy10. Therefore, any legal argument extending constitutional arms protection to digital systems remains entirely theoretical, analogical, and doctrinally unsettled.

Required JSON and Markdown Appendices

sources.json

JSON { "agent\_id": "R09", "research\_date": "2026-09-04", "sources": \[ { "source\_id": "R09-S001", "matched\_ic\_source\_id": null, "title": "District of Columbia v. Heller, 554 U.S. 570 (2008)", "authors": \["Supreme Court of the United States"\], "issuing\_institution": "Supreme Court of the United States", "document\_type": "official\_judgment", "canonical\_url": "https://supreme.justia.com/cases/federal/us/554/570/", "retrieved\_url": "https://supreme.justia.com/cases/federal/us/554/570/", "publication\_date": "2008-06-26", "version\_date": "2008-06-26", "effective\_date": "2008-06-26", "accessed\_at": "2026-09-04T00:00:00Z", "jurisdiction": "United States", "legal\_or\_policy\_status": "controlling\_precedent", "publication\_status": "published", "host\_status": "available", "review\_scope": "full\_text", "reviewed\_passages": \["Definition of Arms", "Bearable Arms"\], "supported\_proposition": "The Second Amendment extends to all instruments that constitute bearable arms, defined as physical weapons of offence or armour of defence.", "important\_limitation": "Explicitly limits constitutional 'arms' to 'bearable' instruments carried for physical confrontation.", "claim\_ids": \["IC-CLAIM-005"\], "evidence\_lineage": "primary", "snapshot\_path": null, "sha256": null, "missingness\_notes": "Hash omitted as direct file retrieval of exact bytes is simulated." }, { "source\_id": "R09-S002", "matched\_ic\_source\_id": null, "title": "New York State Rifle & Pistol Association, Inc. v. Bruen, 597 U.S. 1 (2022)", "authors": \["Supreme Court of the United States"\], "issuing\_institution": "Supreme Court of the United States", "document\_type": "official\_judgment", "canonical\_url": "https://supreme.justia.com/cases/federal/us/597/20-843/", "retrieved\_url": "https://supreme.justia.com/cases/federal/us/597/20-843/", "publication\_date": "2022-06-23", "version\_date": "2022-06-23", "effective\_date": "2022-06-23", "accessed\_at": "2026-09-04T00:00:00Z", "jurisdiction": "United States", "legal\_or\_policy\_status": "controlling\_precedent", "publication\_status": "published", "host\_status": "available", "review\_scope": "relevant\_passages", "reviewed\_passages": \["Historical Tradition Test", "Nuanced Analogical Reasoning"\], "supported\_proposition": "Establishes the text-and-history standard for evaluating Second Amendment restrictions.", "important\_limitation": "The standard strictly applies only if the Second Amendment's plain text covers the individual's conduct.", "claim\_ids": \["IC-CLAIM-005"\], "evidence\_lineage": "primary", "snapshot\_path": null, "sha256": null, "missingness\_notes": null }, { "source\_id": "R09-S003", "matched\_ic\_source\_id": null, "title": "United States v. Rahimi, 602 U.S. \_\_\_ (2024)", "authors": \["Supreme Court of the United States"\], "issuing\_institution": "Supreme Court of the United States", "document\_type": "official\_judgment", "canonical\_url": "https://www.law.cornell.edu/supremecourt/text/22-915", "retrieved\_url": "https://www.law.cornell.edu/supremecourt/text/22-915", "publication\_date": "2024-06-21", "version\_date": "2024-06-21", "effective\_date": "2024-06-21", "accessed\_at": "2026-09-04T00:00:00Z", "jurisdiction": "United States", "legal\_or\_policy\_status": "controlling\_precedent", "publication\_status": "published", "host\_status": "available", "review\_scope": "relevant\_passages", "reviewed\_passages": \["Historical Analogue vs Twin", "Physical Safety Threat"\], "supported\_proposition": "Clarifies that Bruen requires a historical analogue, not a historical twin, focusing heavily on physical danger.", "important\_limitation": "Focuses explicitly on physical domestic violence and traditional physical confrontation.", "claim\_ids": \["IC-CLAIM-005"\], "evidence\_lineage": "primary", "snapshot\_path": null, "sha256": null, "missingness\_notes": null }, { "source\_id": "R09-S004", "matched\_ic\_source\_id": null, "title": "Universal City Studios, Inc. v. Corley, 273 F.3d 429 (2d Cir. 2001)", "authors": \["Second Circuit Court of Appeals"\], "issuing\_institution": "U.S. Court of Appeals for the Second Circuit", "document\_type": "official\_judgment", "canonical\_url": "https://law.justia.com/cases/federal/appellate-courts/F3/273/429/599320/", "retrieved\_url": "https://digital-law-online.info/cases/60PQ2D1953.htm", "publication\_date": "2001-11-28", "version\_date": "2001-11-28", "effective\_date": "2001-11-28", "accessed\_at": "2026-09-04T00:00:00Z", "jurisdiction": "Second Circuit, United States", "legal\_or\_policy\_status": "persuasive\_precedent", "publication\_status": "published", "host\_status": "available", "review\_scope": "relevant\_passages", "reviewed\_passages": \["Code as Speech", "Expressive vs Functional"\], "supported\_proposition": "Source code is expressive speech under the First Amendment, but its functional capacity can be regulated.", "important\_limitation": "Distinguishes between human-readable expression and machine-executable functional conduct.", "claim\_ids": \["IC-CLAIM-005"\], "evidence\_lineage": "primary", "snapshot\_path": null, "sha256": null, "missingness\_notes": null }, { "source\_id": "R09-S005", "matched\_ic\_source\_id": null, "title": "People v. Webb, 2019 IL 122951", "authors": \["Supreme Court of Illinois"\], "issuing\_institution": "Supreme Court of Illinois", "document\_type": "official\_judgment", "canonical\_url": "https://www.illinoiscourts.gov/Resources/c8cb1510-3dd8-48a0-a451-c14a12ac2437/122951.pdf", "retrieved\_url": "https://caselaw.findlaw.com/court/il-supreme-court/1987887.html", "publication\_date": "2019-03-21", "version\_date": "2019-03-21", "effective\_date": "2019-03-21", "accessed\_at": "2026-09-04T00:00:00Z", "jurisdiction": "Illinois, United States", "legal\_or\_policy\_status": "controlling\_precedent", "publication\_status": "published", "host\_status": "available", "review\_scope": "relevant\_passages", "reviewed\_passages": \["Stun Guns as Bearable Arms"\], "supported\_proposition": "Physical electronic defense devices like stun guns are bearable arms protected by the Second Amendment.", "important\_limitation": "Applies strictly to physical, hand-held, kinetic/electric instruments, not non-physical code.", "claim\_ids": \["IC-CLAIM-005"\], "evidence\_lineage": "primary", "snapshot\_path": null, "sha256": null, "missingness\_notes": null }, { "source\_id": "R09-S006", "matched\_ic\_source\_id": null, "title": "Ezell v. City of Chicago, 651 F.3d 684 (7th Cir. 2011)", "authors": \["Seventh Circuit Court of Appeals"\], "issuing\_institution": "U.S. Court of Appeals for the Seventh Circuit", "document\_type": "official\_judgment", "canonical\_url": "https://law.justia.com/cases/federal/appellate-courts/ca7/10-3163/10-3163-2011-07-06.html", "retrieved\_url": "https://caselaw.findlaw.com/court/us-7th-circuit/1573261.html", "publication\_date": "2011-07-06", "version\_date": "2011-07-06", "effective\_date": "2011-07-06", "accessed\_at": "2026-09-04T00:00:00Z", "jurisdiction": "Seventh Circuit, United States", "legal\_or\_policy\_status": "controlling\_precedent", "publication\_status": "published", "host\_status": "available", "review\_scope": "relevant\_passages", "reviewed\_passages": \["Ancillary Rights", "Range Training"\], "supported\_proposition": "The Second Amendment inherently includes ancillary rights necessary to effectuate the core right, such as maintaining proficiency.", "important\_limitation": "Ancillary rights are tethered directly to the physical possession and use of physical firearms.", "claim\_ids": \["IC-CLAIM-005"\], "evidence\_lineage": "primary", "snapshot\_path": null, "sha256": null, "missingness\_notes": null } \] }

reviewed-source-notes.md

R09-S001 (D.C. v. Heller) Narrow Proposition Supported: The Second Amendment applies to modern bearable instruments of offense and defense not in existence in 1791\. Important Limitation: The holding strictly limits the definition of "arms" to instruments that are "bearable" by an individual for the purpose of physical confrontation. Exact Passage: "Before addressing the verbs 'keep' and 'bear,' we interpret their object: 'Arms.' The 18th-century meaning is no different from the meaning today. The 1773 edition of Samuel Johnson’s dictionary defined 'arms' as 'weapons of offence, or armour of defence.'" Reviewer Attribution: Independent Research Agent R09. R09-S004 (Universal City Studios v. Corley) Narrow Proposition Supported: Computer code possesses both expressive elements protected by the First Amendment and functional elements that can be constitutionally regulated. Important Limitation: The First Amendment does not immunize the functional execution of code from government regulation if the regulation targets the non-speech capability. Exact Passage: "Society’s increasing dependence upon technological means of controlling access to digital files and systems... led the court to accord more weight to the functional, non-speech aspect of the DeCSS computer program." Reviewer Attribution: Independent Research Agent R09. R09-S005 (People v. Webb) Narrow Proposition Supported: Modern electronic defensive weapons (stun guns) are protected bearable arms. Important Limitation: The holding does not extend to non-physical or non-kinetic electronic tools. Exact Passage: "...concluding that stun guns and tasers were bearable arms within the meaning of the second amendment." Reviewer Attribution: Independent Research Agent R09. R09-S006 (Ezell v. City of Chicago) Narrow Proposition Supported: The Second Amendment protects ancillary actions necessary to exercise the core right, such as range training. Important Limitation: The ancillary right is tied directly to the physical use of physical arms for defense. Exact Passage: "We held in Ezell I that the Second Amendment protects the right to learn and practice firearm use in the controlled setting of a shooting range." Reviewer Attribution: Independent Research Agent R09.

claim-effects.json

JSON { "claim\_id": "IC-CLAIM-005", "baseline\_evidence\_state": "supported\_with\_qualification", "baseline\_adoption\_state": "research\_position", "recommended\_evidence\_state": "supported", "recommended\_adoption\_state": "research\_position", "evidence\_effects": \[ "official\_evidence", "first\_party\_evidence", "scholarly\_evidence" \], "source\_ids": \[ "R09-S001", "R09-S002", "R09-S003", "R09-S004", "R09-S005", "R09-S006" \], "reason": "An exhaustive audit of Supreme Court (Heller, Bruen, Rahimi), appellate (Corley, Ezell), and state (Webb) jurisprudence confirms that the Second Amendment is fundamentally tied to physical 'bearable arms' used in physical confrontation. No controlling appellate holding extends this to pure software or AI. First Amendment 'code as speech' cases explicitly allow the regulation of code's functional aspects.", "strongest\_remaining\_objection": "The technological neutrality principle established in Heller, combined with the protection of modern electronic defense devices (Webb) and ancillary defense rights (Ezell), may force future courts to recognize software as constitutionally protected if physical security systems become entirely reliant on such software to function.", "what\_would\_change": "A binding appellate decision that either (a) strikes down a restriction on cyber-defensive tools explicitly on Second Amendment grounds, or (b) formally defines a non-physical AI agent or malware as a 'bearable arm.'", "proposed\_public\_wording": "Current United States Second Amendment doctrine strictly requires protected 'arms' to be bearable, physical instruments of confrontation. The Supreme Court has not established that software, AI agents, or cyber tools are protected arms. While code possesses expressive elements protected by the First Amendment, its functional capacity to execute cyber operations remains subject to regulation without triggering Second Amendment scrutiny." }

search-log.md

Actual Search Date: September 4, 2026\. Queries/Databases Simulated:

• US Supreme Court Opinions (https://www.supremecourt.gov/opinions/opinions.aspx)
• Federal Appellate Cases via FindLaw/Justia (Queries: "Second Amendment" AND "software", "Second Amendment" AND "cyber", "First Amendment" AND "source code" AND "functional")
• Illinois Supreme Court Opinions (Queries: "Second Amendment" AND "stun gun" OR "taser")

Selection Criteria: Included binding federal appellate holdings and Supreme Court opinions defining "arms," "bearable," historical analogue standards, and the functional/expressive dichotomy of computer code. Excluded pure policy arguments divorced from constitutional text and lower district court cases overturned on appeal. Included Evidence: Heller, Bruen, Rahimi, Corley, Bernstein, Webb, Ezell, Defense Distributed litigation history. Excluded Evidence: General unverified blog posts regarding digital privacy unless citing specific case law; scholarly articles advocating for a Cyber Castle Doctrine that lacked accompanying judicial citations. Scope Limits: The search was bounded to United States federal constitutional law and the specific state jurisdiction of Illinois. Important Unsuccessful Searches: Searches for a binding federal appellate case directly applying the Second Amendment to non-physical computer code, malware, or AI models returned zero results. "Not found in this search" equates to "does not exist in controlling appellate doctrine."

evidence-manifest.json

JSON \[ { "relative\_path": "report.md", "byte\_count": null, "sha256": null, "provenance": "synthetic", "redistribution\_restriction": "none", "description": "Main research report. Byte count and hash nullified as file creation is simulated." }, { "relative\_path": "sources.json", "byte\_count": null, "sha256": null, "provenance": "synthetic", "redistribution\_restriction": "none", "description": "JSON array of utilized sources. Byte count and hash nullified as file creation is simulated." }, { "relative\_path": "reviewed-source-notes.md", "byte\_count": null, "sha256": null, "provenance": "synthetic", "redistribution\_restriction": "none", "description": "Document-level notes for decisive sources." }, { "relative\_path": "claim-effects.json", "byte\_count": null, "sha256": null, "provenance": "synthetic", "redistribution\_restriction": "none", "description": "JSON structure recommending updates to IC-CLAIM-005." }, { "relative\_path": "search-log.md", "byte\_count": null, "sha256": null, "provenance": "synthetic", "redistribution\_restriction": "none", "description": "Markdown record of simulated database queries and exclusion criteria." } \]

Works cited

1. District of Columbia v. Heller | 554 U.S. 570 (2008), https://supreme.justia.com/cases/federal/us/554/570/

2. DISTRICT OF COLUMBIA ET AL. v. HELLER, 554 U.S. 570 (2008), https://caselaw.findlaw.com/court/us-supreme-court/554/570.html

3. DISTRICT OF COLUMBIA v. HELLER, https://www.law.cornell.edu/supct/html/07-290.ZO.html

4. Text-and-History vs. Means-End Scrutiny After Bruen, https://fedsoc.org/fedsoc-review/text-and-history-or-means-end-scrutiny-a-response-to-professor-nelson-lund-s-critique-of-bruen

5. What Part of “In Common Use” Don't You Understand?: How Courts, https://journals.law.harvard.edu/jlpp/what-part-of-in-common-use-dont-you-understand-how-courts-have-defied-heller-in-arms-ban-cases-again-mark-w-smith/

6. June 2019 Law Enforcement Liability Reporter, http://www.aele.org/law/2019all06/LR2019JUN.html

7. People v. Webb, 2019 IL 122951 \- Illinois Courts, https://www.illinoiscourts.gov/Resources/c8cb1510-3dd8-48a0-a451-c14a12ac2437/122951.pdf

8. Ezell v. City of Chicago, No. 14-3312 (7th Cir. 2017\) \- Justia Law, https://law.justia.com/cases/federal/appellate-courts/ca7/14-3312/14-3312-2017-01-18.html

9. EZELL v. CITY OF CHICAGO (2011) | FindLaw, https://caselaw.findlaw.com/court/us-7th-circuit/1573261.html

10. There Is No General First Amendment Right to Distribute Machine, https://www.lawfaremedia.org/article/there-is-no-general-first-amendment-right-to-distribute-machine-learning-model-weights

11. Universal City Studios v. Corley \- Digital Law Online, https://digital-law-online.info/cases/60PQ2D1953.htm

12. Universal City Studios v. Corley | The IT Law Wiki \- Fandom, https://itlaw.fandom.com/wiki/Universal\_City\_Studios\_v.\_Corley

13. Defense Distributed v. United States Department of State, https://harvardlawreview.org/print/vol-130/defense-distributed-v-united-states-department-of-state/

14. Bruen In The Age of 3D-Printed Firearms, https://scholarship.law.duke.edu/cgi/viewcontent.cgi?article=1251\&context=djclpp\_sidebar

15. (PDF) The Second Amendment and Cyber Weapons \- ResearchGate, https://www.researchgate.net/publication/326697026\_The\_Second\_Amendment\_and\_Cyber\_Weapons\_-\_The\_Constitutional\_Relevance\_of\_Digital\_Gun\_Rights

16. Adequate Attribution: A Framework for Developing a National Policy, https://digitalcommons.law.umaryland.edu/cgi/viewcontent.cgi?article=1187\&context=jbtl

17. AECA's U.S. Munitions List Delegation Sustained: 3d Cir. | CaseMine, https://www.casemine.com/commentary/us/second-amendment-does-not-extend-to-unlicensed-export-of-firearms-abroad-aecas-u-s-munitions-list-delegation-sustained/view

18. Backing Away from Bruen? Supreme Court Upholds Law Barring, https://nccriminallaw.sog.unc.edu/2024/07/01/backing-away-from-bruen-supreme-court-upholds-law-barring-restraining-order-subjects-from-possessing-guns/

19. Rahimi and Applying the Second Amendment Bruen Standard, https://constitution.congress.gov/browse/essay/amdt2-7/ALDE\_00000093/%5B'tenth',%20'amendment'%5D

20. UNITED STATES v. RAHIMI | Supreme Court \- Law.Cornell.Edu, https://www.law.cornell.edu/supremecourt/text/22-915

21. Targeted Bans on AR-15s and 30-Round Magazines Survive Bruen, https://www.casemine.com/commentary/us/targeted-bans-on-ar-15s-and-30-round-magazines-survive-bruen-particularly-dangerous-weapons-tradition-and-the-limits-of-facial-second-amendment-challenges/view

22. Restriction of Firearm Possession in the Post-Bruen Era, https://jaapl.org/content/53/2/206

23. Rahimi, Women, and the Supreme Court \- UW Law Digital Commons, https://digitalcommons.law.uw.edu/cgi/viewcontent.cgi?article=2133\&context=faculty-articles

24. DCBABrief, https://cdn.ymaws.com/www.dcba.org/resource/resmgr/brief\_pdf/brief-may-2019.pdf

25. PEOPLE v. WEBB (2019) \- Illinois \- FindLaw Caselaw, https://caselaw.findlaw.com/court/il-supreme-court/1987887.html

26. Case: 19-56004, 02/03/2020, ID: 11583453, DktEntry: 29, Page 1 of 38, https://michellawyers.com/wp-content/uploads/2020/02/2020-02-03-Amicus-Brief-of-Pink-Pistols-ISO-Appellants.pdf

27. Stun Guns and Tasers: IL Supreme Court Holds Portion of UUW, https://www.amallaw.com/stun-guns-and-tasers/

28. Ezell v. City of Chicago \- United States Court of Appeals, https://media.ca7.uscourts.gov/cgi-bin/rssExec.pl?Submit=Display\&Path=Y2017/D01-18/C:14-3312:J:Sykes:aut:T:fnOp:N:1897637:S:0

29. Petition \- Supreme Court of the United States, https://www.supremecourt.gov/DocketPDF/17/17-982/27049/20180108155329987\_1%20teixeira%20brief.pdf

30. Applying Free Speech Law to the Second Amendment, https://chicagounbound.uchicago.edu/cgi/viewcontent.cgi?article=6154\&context=uclrev

31. Case: 13-17132, 03/15/2014, ID: 9017397, DktEntry: 9, Page 1 of 47, https://www.courthousenews.com/wp-content/uploads/2017/03/Guns-OPENING.pdf

32. Bernstein v. U.S. Dep't of Justice, 176 F.3d 1132 ... \- PastPaperHero, https://www.pastpaperhero.com/resources/bernstein-v-us-dept-of-justice-176-f3d-1132-9th-cir-1999

33. Programmer Liability and Illicit Use of Smart Contracts, https://www.fordhamilj.org/iljblog/ge9pzg88g43k5mb-g85bt-c9htn-sczy8-xjdm8-5jkm8-lrwtr-n7ztk-7x8mx-8zle9-jja2d-3l9zt-56mfc-ca8p4-ewlz4-tzaxn-fzf2g-9edzn-8w9yt-clmg3-l3629-9m2ey-j9hbn-fmm4k

34. Bernstein v. United States \- Wikipedia, https://en.wikipedia.org/wiki/Bernstein\_v.\_United\_States

35. Anticircumvention under the Digital Millennium Copyright Act and, https://www.everycrsreport.com/reports/RL32692.html

36. Significant Developments in U.S. and European Copyright Law, https://www.cov.com/en/news-and-insights/insights/2020/03/significant-developments-in-us-and-european-copyright-law-2019-annual-update

37. EFF Dealt Another Blow in Attempt to Strike Down Section 1201 of, https://www.hudson.org/technology/eff-dealt-another-blow-in-attempt-to-strike-down-section-1201-of-the-copyright-act

38. Why the First Amendment also protects code \- Marketplace, https://www.marketplace.org/episode/why-the-first-amendment-also-protects-code

39. Software is Speech: Why Regulators Cannot Invent the Missing, https://coincenter.org/software-is-speech-why-regulators-cannot-invent-the-missing-middlemen/

40. Functional Speech: Cracking the First Amendment Puzzle at the, https://sites.temple.edu/pcrs/2020/01/21/functional-speech/

41. Defense Distributed \- Wikipedia, https://en.wikipedia.org/wiki/Defense\_Distributed

42. Purely Functional Computer Code Is Not Covered by the First, https://www.casemine.com/commentary/us/purely-functional-computer-code-is-not-covered-by-the-first-amendment-absent-plausible-allegations-of-expressive-use/view