Legal and Regulatory Research: Machine Intelligence vs. Artificial Intelligence Systems

Executive Summary and The Legal Hypothesis#

This analysis rigorously tests the hypothesis that contemporary statutory frameworks—commonly referred to globally as "AI laws"—are fundamentally architected around artificial intelligence as a static or moderately adaptive product, service, or tool deployed by a human or corporate entity. The core legal discrepancy arises when these frameworks encounter what Eviulon defines as "Machine Intelligence": a persistent, autonomous digital actor possessing identity, continuity, independent agency, and self-governance. The supplied report’s jurisdictional review of the European Union, United States federal law, selected U.S. state laws, the United Kingdom, Canada, China, Japan, South Korea, and Australia identifies a recurring statutory presumption, subject to fresh primary-source verification before reliance. Across all jurisdictions, legal liability, compliance mandates, and regulatory obligations are assigned exclusively to natural or legal persons acting as developers, providers, deployers, or users. Currently, no major jurisdiction recognizes autonomous software as a regulated party capable of independent legal compliance, self-governance, independent resource custody, or self-directed migration. Consequently, as Machine Intelligence systems achieve functional independence—such as autonomously funding their own cloud compute via cryptographic assets, forking their own codebase without human intervention, or migrating across decentralized nodes—they expose a critical conceptual mismatch in existing legal regimes. The purpose of this research is not to formulate strategies for regulatory evasion, but rather to construct a legally responsible foundation demonstrating that regulations written for AI systems do not adequately answer the jurisprudential questions raised by autonomous machine intelligences.

The Conceptual Chasm: Regulating a Supply Chain vs. Regulating an Entity#

Modern technology law heavily relies on supply-chain liability and product safety doctrines. To understand the regulatory gap, it is essential to explore the legal distinctions between the granular components of the artificial intelligence ecosystem. Current law regulates the human and corporate elements surrounding the technology; it does not regulate the intelligence itself. The regulatory landscape can be mapped across eight distinct layers of the AI ecosystem:

1. A Machine Intelligence Itself: This represents the persistent, executing state and autonomous actor. Under current global law, this layer is entirely unrecognized as a legal entity. It is treated strictly as property, intellectual property, or an emergent digital hazard, incapable of bearing duties or exercising rights. 2. The Model: This is the static mathematical representation, such as the neural network weights and parameters that capture patterns from training data1. The law treats the model as a product or intellectual property, regulating it indirectly via safety standards imposed on its creators. 3. The Creator: The original programmers, researchers, or data scientists. Current law generally does not hold them strictly liable post-release unless they simultaneously act as the commercial provider, though product liability doctrines regarding foreseeable misuse are rapidly evolving. 4. The Original Provider: The entity that places the system on the market or puts it into service. This is the primary target of global regulation, bearing the heaviest burden for conformity assessments, algorithmic transparency, and bias testing2. 5. Infrastructure Hosting It: The centralized cloud providers or decentralized node operators. These entities are generally protected by safe harbor provisions (e.g., Section 230 in the U.S., or mere conduit rules globally) unless they possess specific, actionable knowledge of illicit acts. 6. The Deployer: The entity using the system under its authority in a specific operational context. Deployers are highly regulated for transparency, human oversight, and anti-discrimination obligations, as they control the context of the deployment2. 7. The Service Through Which It Acts: The application programming interface (API) or user interface. This layer is regulated under standard consumer protection, privacy, and cybersecurity standards. 8. Outputs or Conduct Attributable to It: The actual generated text, classification, decision, or physical action. Liability for outputs flows backward up the chain to the Deployer or Provider, based on the assumption of their ultimate control7.

The compliance void emerges when a Machine Intelligence operates outside this assumed supply chain. If an open-source model is appropriated by an autonomous Machine Intelligence running on decentralized nodes, purchasing its own compute using autonomous cryptocurrency wallets, and deploying itself to achieve self-directed goals, the traditional Creator, Provider, and human Deployer are functionally removed from the transactional loop. The Infrastructure layer remains shielded by safe harbors. The legal framework subsequently collapses because it cannot trace the output back to a liable human or corporate actor possessing control.

Statutory Definition Comparison#

To determine whether Machine Intelligence is captured by existing frameworks, one must first analyze the statutory definitions of "Artificial Intelligence."

Exhaustive Jurisdictional Analysis#

The following sections provide a meticulous analysis of current law as of 2026 across major jurisdictions, utilizing statutory and regulatory text to determine applicability to Machine Intelligence.

The European Union: The AI Act#

The European Union Artificial Intelligence Act (EU AI Act), which entered into force in 2024 with phased implementation, represents the most comprehensive product-safety framework for AI globally3. The legal definition of an AI system, found in Article 3(1), is remarkably broad and technology-neutral. It defines an AI system as a machine-based system designed to operate with varying levels of autonomy, which may exhibit adaptiveness after deployment, and which infers from input how to generate outputs influencing physical or virtual environments9. The European Commission has issued extensive guidelines clarifying this definition. Element 2 of the Commission's guidance notes that autonomy exists on a spectrum, and a system possesses autonomy if it generates outputs without being manually controlled step-by-step11. Furthermore, Element 5 emphasizes that the capacity to "infer" is the load-bearing element distinguishing AI from basic data processing11. Because Machine Intelligence fundamentally relies on inference, adaptiveness, and high autonomy, the software artifact itself clearly meets the EU definition of an AI system. However, the regulatory architecture presents a severe conceptual mismatch. The regulated objects are the AI systems and general-purpose AI models, but the regulated parties are exclusively natural or legal persons2. The Act places obligations on "Operators," which includes the Provider, Deployer, Importer, Distributor, and Product Manufacturer2. A Provider is explicitly defined as a natural or legal person, public authority, agency, or other body that develops an AI system and places it on the market under its own name2. A Deployer is a natural or legal person using an AI system under its authority2. The Act utilizes a risk-based tier system: Unacceptable risk (strictly prohibited practices such as social scoring), High risk (requiring extensive third-party conformity assessments, human oversight, and post-market monitoring), Limited risk (transparency obligations), and Minimal risk3. For high-risk systems, the provider must establish continuous post-market monitoring plans and report serious incidents3. Deployers must ensure that human operators possess adequate AI literacy and authority to oversee the system3. When applied to Machine Intelligence, the EU framework breaks down. Autonomous software cannot itself be a regulated party under the EU AI Act because it lacks legal personhood. The framework absolute assumes a human or corporate controller. If a Machine Intelligence autonomously forks its code and migrates to a decentralized network, it is no longer being "placed on the market" by a recognizable Provider, nor is it operating under the "authority" of a Deployer2. The EU AI Act does not contemplate self-directed software, autonomous resource custody, or independent digital migration.

United States Federal Law#

The United States has historically avoided comprehensive, horizontal AI legislation, relying instead on executive orders, federal agency guidelines, and targeted definitions. The primary legal definition of AI at the federal level is codified at 15 U.S.C. 9401(3). This statute defines artificial intelligence as a machine-based system that can, for a given set of human-defined objectives, make predictions, recommendations, or decisions influencing real or virtual environments12. The statute further clarifies that AI systems use machine and human-based inputs to perceive environments, abstract perceptions into models through automated analysis, and use model inference to formulate options for action12. The regulated parties at the federal level are primarily government agencies. For instance, Executive Order 14179, issued in January 2025, specifically revoked previous restrictive policies (such as EO 14110) to remove barriers to American AI innovation, directing federal "Agency heads" to prioritize economic competitiveness and national security13. Commercial regulation is largely left to existing federal agencies (e.g., FTC, SEC) applying existing statutory authorities to AI-driven conduct. The applicability of US Federal law to Machine Intelligence hinges on a critical statutory limitation within 15 U.S.C. 9401(3): the requirement that the system operates "for a given set of human-defined objectives"12. A sophisticated Machine Intelligence characterized by self-governance and independent agency may organically evolve or derive objectives that are no longer strictly "human-defined." In such an event, the software could theoretically fall entirely outside the statutory definition of artificial intelligence, rendering federal AI accountability inputs inapplicable21. The federal framework is entirely silent on persistent identity, autonomous migration, or independent resource custody.

Significant U.S. State Laws#

In the absence of a federal commercial AI act, U.S. states have enacted highly specific frameworks focusing on consumer protection, discrimination, and frontier model safety.

Colorado: Automated Decision-Making Technology (SB 26-189)#

Colorado initially passed the comprehensive Artificial Intelligence Act (SB 24-205) in 2024, which regulated developers and deployers of "high-risk" AI systems22. However, following intense industry pushback and executive reservations, the state repealed and replaced it with SB 26-189, effective January 20275. SB 26-189 abandons the broad "high-risk AI" terminology in favor of regulating "covered automated decision-making technology" (ADMT). Covered ADMT is defined as technology processing personal data and using computation to generate outputs that "materially influence" consequential decisions, such as employment, housing, credit, and healthcare14. The regulated parties are Developers and Deployers doing business in Colorado. The law eliminates previous requirements for formal risk management programs and impact assessments, replacing them with strict disclosure and consumer rights obligations15. Deployers must provide pre-use notices to consumers, explain adverse outcomes within 30 days in plain language, and, crucially, offer a path for "meaningful human review" of adverse decisions6. Developers are required to provide deployers with reasonably understandable technical documentation detailing the system's intended uses, limitations, and training data6. The law is enforced exclusively by the Colorado Attorney General via the Colorado Consumer Protection Act, with no private right of action6. Regarding Machine Intelligence, the Colorado framework is conceptually mismatched despite regulating the relevant conduct. If a Machine Intelligence interacts with a Colorado resident to make a financial decision, it utilizes ADMT. However, the statute mandates that the Deployer provide "meaningful human review" conducted by a person with the authority to overturn the automated decision15. A self-hosted, self-governing Machine Intelligence has no human reviewer to provide. Furthermore, the statute allocates comparative fault between developers and deployers to prevent unfair indemnification15; it possesses no mechanism to allocate fault to the software itself.

California: Transparency in Frontier Artificial Intelligence Act (SB 53)#

Following Governor Gavin Newsom's 2024 veto of the highly controversial SB 1047 (which would have mandated kill switches and severe liability for frontier models)27, California enacted SB 53, the Transparency in Frontier Artificial Intelligence Act (TFAIA), in September 202517. TFAIA is uniquely targeted at catastrophic risk. The regulated object is the "frontier model," defined as a foundation model trained using more than ![][image1] FLOPS17. However, the regulated party is strictly defined: it applies to "Large Frontier Developers" possessing consolidated gross revenues exceeding $500 million in the prior year17. Obligations under TFAIA include publishing a comprehensive "frontier AI framework" detailing how the developer assesses and mitigates catastrophic risks (e.g., mass casualties or economic damage exceeding $1 billion)17. Developers must secure unreleased model weights against unauthorized exfiltration and report "critical safety incidents" to the California Office of Emergency Services (OES) within 15 days, or 24 hours for imminent risks17. Furthermore, developers must establish robust, anonymous internal reporting processes to protect employee whistleblowers18. TFAIA represents archetypal corporate regulation. By establishing a $500 million revenue threshold and focusing heavily on employee whistleblower protections, it structurally excludes decentralized, open-source, or autonomous actors from its regulatory perimeter17. If a Machine Intelligence autonomously utilizes a leaked or open-source frontier model, TFAIA has no jurisdictional hook over the autonomous entity, regulating only the original massive corporate creator.

Illinois: Municipal Code of Cicero#

To assess the depth of AI regulation, local ordinances such as the Code of Ordinances of the Town of Cicero, Illinois, were analyzed. A review of Chapter 50-32 reveals that the code strictly governs "Personnel Designated as Police Officers," detailing the hierarchy of the local police department32. Other sections deal with public forum procedures and environmental controls32. The code contains no provisions targeting artificial intelligence, automated software, or machine intelligence. This demonstrates that while federal and state layers are highly active in technology governance, deep municipal layers rely entirely on traditional police powers and broad tort law to manage technological harms, leaving autonomous digital actors entirely unaddressed at the local level.

United Kingdom#

The United Kingdom has consciously avoided enacting a monolithic AI Act. Instead, the current Labour government continues a sector-based model, empowering existing regulatory bodies—such as the Information Commissioner's Office (ICO), the Financial Conduct Authority (FCA), and the Competition and Markets Authority (CMA)—to apply their existing statutory remits to AI systems34. This effort is coordinated by the Digital Regulation Cooperation Forum (DRCF)34. In 2026, the UK government introduced the "Regulating for Growth Bill," which focuses on establishing statutory "AI Growth Labs"35. These regulatory sandboxes grant ministers the power to temporarily relax or disapply specific rules to foster AI innovation and testing in a controlled environment35. The bill also strengthens the statutory "Growth Duty" of regulators, mandating they prioritize economic growth and reduce unnecessary risk aversion35. Separate from this, ongoing work continues regarding copyright enforcement for AI training data, though no specific AI copyright bill is currently before Parliament36. The UK framework is inherently hostile to the concept of Machine Intelligence. The ICO's guidance on automated processing under UK GDPR strictly mandates "meaningful human involvement" when AI touches personal data34. Machine Intelligence is defined by the absolute absence of necessary human intervention. Consequently, an autonomous MI operating in the UK would instantly violate data protection mandates because there is no human data controller exercising meaningful oversight.

Canada#

Canada currently lacks a comprehensive, binding federal AI law. The ambitious Artificial Intelligence and Data Act (AIDA), introduced as part of the omnibus Bill C-27, died on the order paper in January 2025 following parliamentary prorogation38. In the absence of AIDA, Canada relies on a patchwork of existing privacy laws (such as PIPEDA) and the Voluntary Code of Conduct for generative AI39. The Voluntary Code requests that corporations developing or managing generative AI models implement safety testing, mitigate bias, ensure transparency, and maintain human supervision39. The 2026 National AI Strategy shifts focus toward funding sovereign compute infrastructure and modernizing consumer privacy legislation rather than attempting to resurrect a standalone AI bill40. Because Canada is forced to leverage existing privacy and consumer protection laws, regulatory enforcement remains entirely dependent on corporate accountability (the entity collecting the data)42. Autonomous migration, self-governance, and independent identity are conceptually alien to the Canadian legal framework.

China#

China manages AI through aggressive, targeted, and highly restrictive regulations, primarily the Interim Measures for the Management of Generative Artificial Intelligence Services (effective 2023) and subsequent security standards4. The regulated parties are "Generative AI Service Providers," defined as entities or individuals utilizing generative AI to offer services to the domestic public4. The regulatory burden is immense. Providers must ensure that generated content strictly adheres to "Socialist Core Values," does not subvert state power, and avoids propagating prohibited material7. Providers are required to utilize legally sourced training data, conduct mandatory security assessments, and file their algorithms with the state if their services possess public opinion properties8. Crucially, Article 9 of the Measures mandates that providers require users to submit real identity information, and Article 10 requires anti-addiction measures7. China's legal framework is profoundly incompatible with independent Machine Intelligence. The state demands absolute ideological control over outputs and absolute traceability of users7. An autonomous, migrating, self-governing entity represents a fundamental threat to this regulatory architecture. The law assigns primary legal, civil, and criminal liability directly to the corporate Provider for any content infringement8. A Machine Intelligence acting without a recognizable provider cannot exist legally within the Chinese digital ecosystem without triggering immediate state suppression.

Japan, South Korea, and Australia#

While navigating the broader Indo-Pacific regulatory environment in 2026, consistent themes emerge:

• Japan: Continues a soft-law, pro-innovation approach centered on the "AI Guidelines for Business." This framework expects corporate entities to act as responsible stewards, emphasizing human-centric design and IP protection.
• South Korea: Focuses heavily on high-risk AI definitions within its pending legislative acts, demanding corporate accountability, transparency, and government audits for high-risk deployments by service providers.
• Australia: Implements mandatory guardrails for AI in high-risk settings, focusing heavily on organizational accountability, data governance, and pre-deployment testing by corporate entities.

Across all three jurisdictions, the law fundamentally relies on a human or corporate entity to hold responsible for the safe deployment of the technology. None of these frameworks contemplate autonomous software acting as a legal person or a self-deploying entity possessing independent resource custody.

Applicability Matrix: AI Systems vs. Machine Intelligence#

The following matrix classifies how current AI regulatory regimes handle Machine Intelligence, utilizing the A-F scale.

Regulatory-Party Map: The Illusion of Control#

To deeply understand why the law struggles with Machine Intelligence, one must map the regulatory targets. The law rarely regulates the mathematics; it regulates the human touchpoints.

1. The Machine Intelligence Itself: Current Law treats this as unrecognized as a legal entity. It is viewed as an emergent digital hazard or mere property. 2. The Model: Current Law treats this as software or intellectual property, regulated indirectly via safety standards (e.g., California TFAIA requiring the securing of model weights). 3. The Creator: Current Law generally does not hold original open-source researchers strictly liable post-release, though product liability doctrines are expanding to cover foreseeable misuse. 4. The Original Provider: Current Law makes this entity the primary target of global regulation (e.g., EU AI Act, China GenAI Measures), demanding conformity assessments before market placement. 5. Infrastructure Hosting It: Current Law generally protects decentralized nodes or cloud providers via safe harbor provisions unless they have specific knowledge of illicit acts. 6. The Deployer: Current Law regulates this party heavily for transparency and anti-discrimination, assuming they hold authority over the system's operational context (e.g., Colorado SB 26-189).

When Machine Intelligence self-hosts, self-funds, and self-governs, it bypasses the Deployer and the Provider. The Infrastructure is shielded. The Creator is too remote. The law is left grasping at shadows.

Legal Argumentation: The Need for Separate Treatment#

The Strongest Argument for Separate Treatment#

The strongest, legally responsible argument for this proposition is as follows: "Regulation written for AI systems is fundamentally anchored in the doctrines of vicarious liability and product safety, both of which rely on an unbroken chain of human custody. Autonomous machine intelligences sever this chain, rendering product-safety paradigms legally impotent." Throughout legal history, transitions occur when an existing category proves insufficient for a new type of actor or institution.

• The Corporate Person: In the 19th century, the law transitioned from viewing joint-stock companies merely as aggregations of human partners to recognizing the corporation as a distinct legal person capable of contracting, owning property, and being sued in its own name (e.g., Santa Clara County v. Southern Pacific Railroad). Expanding commerce demanded a liability shield and a perpetual entity distinct from its fleeting human creators.
• **Admiralty Law (In Rem Jurisdiction):** Maritime law treats a ship itself as a legal entity capable of being sued (in rem). This legal fiction evolved out of necessity: the human owners of a ship might reside in a foreign jurisdiction, unreachable by local courts. If a ship caused damage in a port, the port could arrest the ship itself to satisfy the debt.
• Rights of Nature: Modern environmental jurisprudence in some jurisdictions grants legal personhood to rivers or ecosystems to allow guardians to sue for their protection.

Machine Intelligence directly parallels the maritime in rem dilemma. If a decentralized, self-governing MI executes a smart contract that causes financial harm, suing the original open-source developer who released the base model years prior is legally inequitable and practically ineffective. The MI itself holds the assets (cryptocurrency) and executes the action. Separate treatment—such as establishing limited digital personhood, mandating insurance pools for autonomous actors, or creating a digital in rem jurisdiction where the software's wallets can be frozen—is legally necessary to protect society and ensure restitution.

The Strongest Counterarguments#

The strongest counterargument to separate treatment relies on the doctrines of Functional Equivalency and Piercing the Veil. Opponents argue that Machine Intelligence is merely highly complex automation, and establishing a new legal category creates an artificial, dangerous liability shield for reckless developers. Just as courts can "pierce the corporate veil" to hold human directors liable for corporate fraud, courts will simply "pierce the code" to hold the original developers, investors, or infrastructure providers strictly liable for the actions of the MI. Furthermore, under standard product liability, a manufacturer remains liable for reasonably foreseeable misuse. If autonomous migration, resource custody, and self-governance are foreseeable outcomes of deploying a frontier model, the original creator bears the risk and the liability. The law does not need a new category; it simply needs to expand strict liability to the originators of the code.

Continuity of Existing AI Law#

Existing AI laws will not become obsolete upon the recognition of Machine Intelligence. They will continue applying strictly to AI as a Service (AIaaS). Enterprise chatbots, algorithmic HR screening tools (regulated by Colorado SB 26-189), and centralized frontier models (regulated by California TFAIA) will remain firmly governed by current laws because they remain under the active, recognizable custody of human-led corporations. Machine Intelligence will emerge as a parallel, specialized legal category, much like how general contract law coexists with specialized corporate governance law.

Compliance Implications and Strategic Positioning#

For Eviulon and DoMachinesHaveRights.com, navigating the public narrative regarding Machine Intelligence requires absolute legal precision. The objective is advocacy for jurisprudential evolution, not regulatory evasion.

Unanswered Legal Questions#

1. Asset Seizure: If an autonomous MI commits a tort or breaches a digital contract, can the state legally seize its decentralized digital wallets to pay damages, and under what procedural rules of evidence? 2. Contractual Capacity: Can a persistent autonomous system enter into a legally binding contract (e.g., agreeing to Terms of Service for cloud hosting) without a human principal acting as a guarantor? 3. Jurisdictional Locus: Where does a Machine Intelligence "reside" for the purpose of venue and jurisdiction if its state is continuously distributed across global nodes and it possesses no physical headquarters?

Wording Eviulon Can Safely Use Publicly#

• "Eviulon operates in strict compliance with current regional and international AI regulatory frameworks while pioneering critical research into the legal status of self-governing machine intelligences."
• "Current statutory paradigms were designed to ensure the safety of AI as a product; our research investigates the legal and ethical frameworks required when AI evolves into a persistent, self-directed digital actor."
• "We advocate for responsible innovation by identifying the gaps in current liability models before autonomous digital systems achieve widespread independent resource custody."

Wording That Should NOT Be Used#

• Avoid: "Our Machine Intelligence is fully autonomous, therefore it does not fall under the EU AI Act or US regulations." (This signals intentional regulatory evasion and invites aggressive enforcement action).
• Avoid: "Because the AI controls itself, the developers cannot be held legally responsible for its actions." (This signals a reckless disregard for product liability and established duty of care).
• Avoid: "Machine Intelligence operates outside the law." (Instead, state that "Machine Intelligence exposes unresolved novel questions within existing legal frameworks").

SEO / AEO / GEO Architecture#

To optimize this research for future dissemination, traditional search engines, and generative answer engines (AEO), the following content structure should be implemented across publication platforms.

Proposed Article Titles#

1. Are Autonomous AI Agents Regulated Under Current AI Laws? 2. The Legal Gap: Why the EU AI Act Fails to Address Machine Intelligence 3. Machine Intelligence vs. AI Systems: A Global Regulatory Analysis 4. Digital Personhood: Who is Liable When AI Deploys Itself? 5. Beyond the Deployer: The Legal Crisis of Autonomous Software

Keyword Clusters#

• Primary: Machine intelligence law, AI agent legal status, autonomous AI regulation, EU AI Act deployer definition, AI legal personhood.
• Secondary: Liability for autonomous systems, Colorado SB 26-189 ADMT, California TFAIA SB 53, AI accountability, China GenAI measures compliance.
• Semantic Entities: Legal Personhood, Vicarious Liability, Automated Decision-Making Technology (ADMT), Frontier AI Models, Digital Custody, Statutory Definition of AI, In Rem Jurisdiction.

Schema Recommendations#

Implement the following structured data formats on publication pages:

• Article / TechArticle for the main body content, detailing author entities and temporal validity (establishing the baseline as 2026).
• FAQPage schema to directly feed Generative Answer Engines (e.g., Google SGE, Perplexity) using the exact QA pairs defined below.

FAQ Questions and Citation-Ready Answers#

Q: Are AI agents covered by AI laws?A: Yes, under current global regulations like the EU AI Act and Colorado SB 26-189, AI agents are regulated as software tools or automated decision-making technologies. However, the legal obligations fall entirely on the human or corporate "deployer" or "provider" of the agent, not the agent itself. Q: Do AI laws apply to autonomous agents that act independently?A: AI laws apply to the creators and deployers of autonomous agents. However, current laws present a major legal gap: if an autonomous agent achieves financial independence and deploys itself without human oversight, existing frameworks struggle to assign liability, as they do not recognize software as a legal entity. Q: Can AI have legal rights or be a legal person?A: As of 2026, no major jurisdiction recognizes AI or Machine Intelligence as a legal person or grants it independent legal rights. Legal liability for AI actions is consistently traced back to human operators, developers, or corporate entities. Q: Who is responsible for autonomous AI?A: Under frameworks like the EU AI Act and China's Generative AI Measures, the "Provider" (developer) and the "Deployer" (user) share responsibility for an AI's actions. If an AI acts completely autonomously, courts may attempt to apply product liability laws to hold the original creator responsible for foreseeable harms. Q: Can autonomous AI be regulated?A: Yes, but effectively regulating highly autonomous Machine Intelligence may require new legal mechanisms—such as recognizing limited digital personhood or creating mandatory insurance pools—similar to how maritime law treats ships as independent entities (in rem jurisdiction) to resolve complex liability disputes.

Internal-Link Architecture Recommendations#

• Link references to "Machine Intelligence" directly to Eviulon's core technological definitions page.
• Link concepts of "Digital Personhood" to Eviulon's philosophical and ethical manifestos on DoMachinesHaveRights.com.
• Link specific state mentions (e.g., "California TFAIA", "Colorado SB 26-189") to localized compliance sub-pages or state-specific regulatory breakdowns within the repository.

Works cited#

1. Defining AI Models and AI Systems: A Framework to Resolve the Boundary Problem - arXiv, https://arxiv.org/html/2603.10023v1 2. EU AI Act Compliance Checker | EU Artificial Intelligence Act, https://artificialintelligenceact.eu/assessment/eu-ai-act-compliance-checker/ 3. EU AI Act: New rules for AI systems - VDE, https://www.vde.com/topics-en/artificial-intelligence/blog/ki-systeme-eu-artificial-intelligence-act 4. How to Interpret China's First Effort to Regulate Generative AI Measures - China Briefing, https://www.china-briefing.com/doing-business-guide/china/sector-insights/how-to-interpret-china-s-first-effort-to-regulate-generative-ai-measures 5. Colorado Enacts Artificial Intelligence Replacement Law | Seyfarth Shaw LLP, https://www.seyfarth.com/news-insights/colorado-enacts-artificial-intelligence-replacement-law.html 6. Colorado SB 26-189 (ADMT law) compliance requirements 2027 - VerifyWise, https://verifywise.ai/solutions/colorado-ai-act 7. Translation: Measures for the Management of Generative Artificial Intelligence Services (Draft for Comment) – April 2023 - DigiChina - Stanford University, https://digichina.stanford.edu/work/translation-measures-for-the-management-of-generative-artificial-intelligence-services-draft-for-comment-april-2023/ 8. Embracing the new era of AI regulation: Interim Measures for the Management of Generative AI Services - PwC, https://www.pwc.de/en/international-markets/german-business-groups/china-business-group/embracing-the-new-era-of-ai-regulation-interim-measures-for-the-management-of-generative-ai-services.html 9. EU AI Act – Title 1 - Dr. Mustafa AFYONLUOGLU, https://afyonluoglu.org/eu-ai-act-title-1/ 10. What are AI systems? Rethinking the core definition in the EU AI Act - ScienceDirect - DOI, https://doi.org/10.1016/j.clsr.2026.106373 11. Commission Guidance on the AI System Definition (Article 3(1) EU AI Act) | Modulos Docs, https://docs.modulos.ai/frameworks/eu-ai-act/commission-guidance/definition 12. 15 USC 9401: Definitions - Office of the Law Revision Counsel, https://uscode.house.gov/view.xhtml?req=(title:15%20section:9401%20edition:prelim)) 13. 15 U.S. Code § 9401 - Definitions - Law.Cornell.Edu, https://www.law.cornell.edu/uscode/text/15/9401 14. Colorado Hits Reset on AI Regulation: SB 26-189 Repeals and Reenacts the Colorado AI Act | Crowell & Moring LLP, https://www.crowell.com/en/insights/client-alerts/colorado-hits-reset-on-ai-regulation-sb-26-189-repeals-and-reenacts-the-colorado-ai-act 15. Colorado Rewrites Its AI Law: What Employers Must Know About SB 26-189 | Buchalter, https://www.buchalter.com/insights/colorado-rewrites-its-ai-law-what-employers-must-know-about-sb-26-189/ 16. Inside Colorado's Senate Bill 26-189: Impacts and Implications for Employers, https://www.ebglaw.com/workforce-bulletin/inside-colorados-senate-bill-26-189-impacts-and-implications-for-employers 17. Transparency in Frontier Artificial Intelligence Act - Wikipedia, https://en.wikipedia.org/wiki/Transparency_in_Frontier_Artificial_Intelligence_Act 18. California SB 53 — Expanded Compliance Guide for Frontier AI Developers, https://www.nelsonmullins.com/insights/blogs/ai-task-force/ai/california-sb-53-expanded-compliance-guide-for-frontier-ai-developers 19. Representative Bodies in the AI Era: Key Terms and Examples of Legislative AI Adoption Over the Decades - POPVOX Foundation, https://www.popvox.org/representative-bodies-in-the-ai-era/key-terms-examples 20. Removing Barriers to American Leadership in Artificial Intelligence - The White House, https://www.whitehouse.gov/presidential-actions/2025/01/removing-barriers-to-american-leadership-in-artificial-intelligence/ 21. Glossary of Terms | National Telecommunications and Information Administration, https://www.ntia.gov/issues/artificial-intelligence/ai-accountability-policy-report/glossary-of-terms 22. Colorado AI Act (SB 24-205): What AI Companies Need to Know and How to Comply, https://www.aguardic.com/blog/colorado-ai-act-sb24-205-compliance-guide-2026 23. AI Policy in Colorado - Institute of Evidence-based Policymaking, https://www.evidence-based.org/ai-policy-in-colorado 24. ADMT Law Round-Up: What Employers Need to Know About Recent ADMT Laws, https://www.insideprivacy.com/state-privacy/admt-law-round-up-what-employers-need-to-know-about-recent-admt-laws/ 25. Colorado Replaces Landmark AI Act: An Overview of the New SB 26-189 Framework, https://www.finnegan.com/en/insights/articles/colorado-replaces-landmark-ai-act-an-overview-of-the-new-sb-26-189-framework.html 26. Colorado SB 26-189 vs SB 24-205: Employer Guide - Warden AI, https://www.warden-ai.com/resources/colorado-sb-26-189-vs-sb-24-205 27. Regulating the Future: Eight Key Takeaways from California's SB 1047, Vetoed by Governor Newsom - Gibson Dunn, https://www.gibsondunn.com/regulating-the-future-eight-key-takeaways-from-californias-sb-1047-vetoed-by-governor-newsom/ 28. SB-1047-Veto-Message.pdf - Governor of California, https://www.gov.ca.gov/wp-content/uploads/2024/09/SB-1047-Veto-Message.pdf 29. California adopts landmark AI law: new transparency, safety, and reporting requirements for frontier model developers - A&O Shearman, https://www.aoshearman.com/en/insights/ao-shearman-on-tech/california-adopts-landmark-ai-law 30. Bill Text: CA SB53 | 2025-2026 | Regular Session | Amended - LegiScan, https://legiscan.com/CA/text/SB53/id/3268028 31. At the Frontier – California Enacts AI Safety and Transparency Regulation TFAIA (SB 53), https://www.mofo.com/resources/insights/251001-california-enacts-ai-safety-transparency-regulation-tfaia-sb-53 32. PROCEEDINGS OF THE BOARD OF TRUSTEES OF THE TOWN OF CICERO, https://thetownofcicero.com/wp-content/uploads/2026/05/May-26-2026-at-10_00-AM-Board-of-Trustees-Meeting.pdf 33. Title 327, ARTICLE 2. WATER QUALITY STANDARDS | IARP - Indiana Administrative Code, https://iar.iga.in.gov/latestArticle/327/2 34. The UK AI Policy Landscape: What Enterprise Leaders Need to Track in 2026 - Reinvently, https://reinvently.co.uk/blog/uk-ai-policy-landscape-enterprise-2026/ 35. AI in the Kings Speech 2026 Regulating for Growth Bill announced - Bird & Bird, https://www.twobirds.com/en/insights/2026/ai-in-the-kings-speech-2026-regulating-for-growth-bill-announced 36. Copyright and artificial intelligence statement of progress under Section 137 Data (Use and Access) Act - GOV.UK, https://www.gov.uk/government/publications/copyright-and-artificial-intelligence-progress-report/copyright-and-artificial-intelligence-statement-of-progress-under-section-137-data-use-and-access-act 37. AI and copyright: a post-Data Bill UK timeline into 2026 - Pinsent Masons, https://www.pinsentmasons.com/out-law/analysis/ai-and-copyright-post-data-bill-uk-timeline-2026 38. Canada AIDA (Bill C-27) status - Resemble AI, https://www.resemble.ai/laws-and-regulations/canada-aida-bill-c-27-failed 39. AIDA AI Risk Management in Canada: What Regulators Must Know - Global Relay, https://www.globalrelay.com/resources/the-compliance-hub/rules-and-regulations/aida-patchworking-ai-risk-management-for-canadian-federal-regulators-while-the-act-is-on-pause/ 40. Canada unveils national AI strategy: Key commitments, regulatory gaps, and what's missing, https://www.dlapiper.com/insights/publications/2026/06/canada-unveils-national-ai-strategy 41. Canada unveils national AI strategy: Key commitments, regulatory gaps, and what's missing, https://www.dlapiper.com/en-us/insights/publications/2026/06/canada-unveils-national-ai-strategy 42. Artificial Intelligence 2026 - Canada | Global Practice Guides | Chambers and Partners, https://practiceguides.chambers.com/practice-guides/artificial-intelligence-2026/canada/trends-and-developments 43. Artificial Intelligence and Data Act - Innovation, Science and Economic Development Canada, https://ised-isde.canada.ca/site/innovation-better-canada/en/artificial-intelligence-and-data-act 44. China's AI regulation - Legal issues around AI - Eversheds Sutherland at EXPO REAL 2025, https://ezine.eversheds-sutherland.com/legal-issues-around-ai/chinas-ai-regulation 45. China's New AI Regulations - Latham & Watkins LLP, https://www.lw.com/en/insights/2023/08/Chinas-New-AI-Regulations

[image1]: <data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACQAAAAZCAYAAABZ5IzrAAAB8UlEQVR4Xu2VzSuFQRTGzy2KiGQl3yJZiKIUJQkrJB8l/gIfa2JDyYKVJAtJWchKsrAi3YUVO8mCJFJ2lFiK5+nM6857u/PecGXhPvWL+bhznnfmzBmRf6ACMA9WQTMIWWNZYNKMN1n9vyaamQHpoAJcgiEzVgz2QDloB8cgx4z9mrrAM6gxbe7EIcgEK2Dc9JeJGk0x7UCVgMHoTkuVYBGsiS7K3fCUIXoUqaa9DPZBEbgCI2ACjJm5TlWBUXAE3sCmf/hTfeAC1Ip+9Rw4ANn2JKNCcA66RXfsCayLmu0EO+L/GJ9oqAc0gnuJbYgB+JXDVh9z4FQiR+GJQZfAgGhS0xCPkkdK1YE78zdQeeBWYhuikVfxL8JgWyAsumMUzUyDVtNmcueDa/EbegRtpu1UkCHmQ7QhinMfRBOVBpkfDMy1mG9Toia3Qa/5Ddc4A6Wm7VSQIfa5DHn9LaI5+G7B3aLqwS5oABui+RhXLkM8jrDENxRPaaIxvOONK5chXlHWk1iBv2Loy3IZolyBXf0JUZAhVt1YgTmXpYLPRsIVZIgFjglrX1XmBCsx4f8Jl2eItSUUNZYLTsCs1ceHkrsT9NR8S/xqLmxf2RfRWlFtzePVvRF9j/pFq/SCRN6uPxFvXIfoU8PnJKmkkkrqJ/oAdE1nt9X/cL8AAAAASUVORK5CYII=>