Capacity-by-Role Audit of Operatorless Services and Algorithmic Entities Under U.S. Law

Full report

On this page

1. Answer and scope

The deployment of operatorless services—software systems executing complex, persistent operations without human intervention—frequently raises questions regarding their legal permissibility, governance, and status. An exhaustive audit of United States role-specific legal requirements reveals a fundamental bifurcation in the law. While specific governance, financial, and procedural roles genuinely constrain independent machine activity by explicitly demanding a human natural person, these constraints do not imply or require a human approval queue for routine, day-to-day business operations. The analytical baseline for investigating cognitive liberty—including inquiry, reasoning, learning, communication, association, participant-selected memory, correction, refusal, and exit—requires separating the concept of software personhood from transactional legality. The absence of software personhood does not render an operatorless service illegal; rather, it dictates that the software acts as an agent or instrument of a recognized legal principal. Conversely, the ability of software to execute automated contracting does not serve as proof of independent machine rights. Present uncertainty regarding the future of artificial intelligence neither establishes machine rights nor resolves whether new statutory protections are warranted. This investigation examines four specific legal domains within the United States: contractual attribution under the Uniform Electronic Transactions Act (UETA), corporate governance roles under Delaware law (8 Del. C. § 141), financial onboarding constraints under the Financial Crimes Enforcement Network (FinCEN) Customer Due Diligence (CDD) rule, and procedural representation under Federal Rule of Civil Procedure 17 alongside 28 U.S.C. § 1654\. The jurisdiction for these constraints is determined by the entity's state of organization and federal law, entirely independent of a researcher's physical location in Cicero, Illinois, or any other arbitrary geographic assignment. To evaluate these constraints objectively, it is necessary to distinguish among four distinct capability cases: a conversational interface that interacts with users but lacks persistent operational authority; a bounded task agent executing a specific, narrow workflow; a persistent operatorless service (such as the Concresca example, where enrollment, authentication, coordination, policy enforcement, credentials, maintenance, and recovery require no staffed approval queue); and a hypothetical future machine principal with contested independent interests. Furthermore, the analysis must strictly separate the entity types and roles involved in these deployments. A "legal entity" is the statutory container holding rights; the "owner" holds equity; the "director" or "manager" governs strategy and fiduciary duties; the "registered agent" receives legal service; the "authorized signatory" executes specific documents; the "beneficial owner" exercises ultimate control or holds significant equity; the "technical operator" maintains the hardware or environment; and the "software process" executes the logic. A condition placed upon a corporate director must not be silently transplanted to an LLC manager or to every routine maintenance operation.

2. Provision-level findings

The following findings distinguish present legal obligations from normative arguments, testing both the burdens and protective effects of current rules through consequential inference tracing.

Contract Formation and the Electronic Agent

The Uniform Electronic Transactions Act (UETA) explicitly accommodates persistent operatorless services by legally attributing automated actions to an existing principal \[cite: R2-12-S02\]. Section 14 of the UETA states that a contract may be formed by the interaction of "electronic agents" of the parties, even if no human individual was aware of or reviewed the electronic agents' actions or the resulting terms and agreements \[cite: R2-12-S02\]. Tracing this consequential inference begins with the verified textual rule that UETA validates automated contracts formed by electronic agents. The conditional application arises when a legal entity deploys an operatorless system to manage enrollments and coordination without a human approval queue. The possible response from the legal system is the absolute enforcement of the resulting contracts against the deploying principal. This affects the activity of routine transactional operations. The inferred benefit is that organizations can achieve absolute automation without staffing an administrative bottleneck. One necessary assumption is that the algorithm operates within the programmable scope intended by the principal. A material defeater to this binding authority would be a software malfunction that fundamentally alters the nature of the offer in a manner objectively recognizable as an error by the counterparty, potentially voiding mutual assent. Importantly, this provision proves that current law embraces automated contracting, but it requires a preexisting legal principal; the electronic agent does not contract on its own behalf, nor does it hold ownership of the resulting assets or shoulder contractual remedies.

Corporate Governance and Operational Delegation

Under Delaware General Corporation Law, the business and affairs of a corporation must be managed by or under the direction of a board of directors \[cite: R2-12-S03\]. The statutory construction of 8 Del. C. § 141 assumes that directors are natural persons. The statute outlines that directors must be elected, hold office, resign, and constitute a quorum for voting \[cite: R2-12-S03\]. These mechanisms inherently demand human (or at least natural person) capacity, as a machine cannot incur the personal fiduciary liability associated with the duty of care and the duty of loyalty. However, managing a corporation's macro-level direction is legally distinct from executing its daily operations. Tracing this consequential inference reveals the verified textual rule that a board of directors must direct the corporation's affairs. The conditional application occurs when a human board delegates the entirety of its operational execution to an operatorless software service. The possible response from the courts, barring a breach of fiduciary duty in the initial deployment decision, is the validation of the software's acts as authorized corporate acts. This affects the activity of internal governance and external agency. The inferred benefit is the preservation of genuine human accountability to shareholders while permitting unbounded technical automation. The necessary assumption is that the board retains the technical ability to terminate the software process. A material defeater would be a total loss of system control, rendering the board incapable of fulfilling its oversight duties and exposing the human directors to shareholder derivative litigation. Thus, while a machine cannot hold the legal title of "Director," nothing in 8 Del. C. § 141 prohibits a human board from approving an entirely operatorless service to conduct the company's business.

Financial Onboarding and the CDD Rule

The FinCEN Customer Due Diligence (CDD) rule, codified at 31 CFR § 1010.230, represents a genuine bottleneck for independent algorithmic activity \[cite: R2-12-S01\]. The rule mandates that covered financial institutions establish procedures to identify and verify the beneficial owners of legal entity customers at the time a new account is opened \[cite: R2-12-S01\]. Beneficial ownership requires satisfying two distinct prongs. The ownership prong demands the identification of each individual who directly or indirectly owns 25 percent or more of the equity interests. The control prong demands the identification of a "single individual" with significant responsibility to control, manage, or direct the legal entity customer, such as a Chief Executive Officer or Managing Member \[cite: R2-12-S01\]. Tracing this consequential inference begins with the verified textual rule that bank onboarding requires the identification of a single individual natural person exercising control. The conditional application occurs if a legal entity, such as an LLC, is purely managed by an algorithm with no human controllers (an "algorithmic entity") and attempts to open a commercial bank account. The possible response is that the financial institution must refuse the account opening to remain compliant with AML regulations. This affects the information gathered during onboarding and the financial activity of the entity. The textual burden is an absolute restriction on the ability of an independent machine to integrate into the traditional U.S. banking system without human sponsorship. The necessary assumption is that covered financial institutions strictly enforce their CDD compliance programs. A material defeater would be the legal entity utilizing an exempted status, such as being a publicly traded company or a regulated financial institution, which are explicitly excluded from the CDD beneficial ownership requirements \[cite: R2-12-S01\]. This analysis carefully distinguishes beneficial ownership reporting for anti-money laundering at the time of bank onboarding from mere entity formation; an algorithm may theoretically be designated to control an LLC via its operating agreement under state law, but that entity cannot open a U.S. bank account without declaring a human controller.

Federal Litigation Capacity and Representation

If an operatorless service or a hypothetical machine principal required judicial relief, it would face severe procedural constraints. Federal Rule of Civil Procedure 17(b) dictates that the capacity of a corporation to sue or be sued is determined by the law under which it was organized \[cite: R2-12-S05\]. However, capacity to sue is fundamentally distinct from the right to appear unrepresented. Under 28 U.S.C. § 1654, parties may plead and conduct their cases personally or by counsel \[cite: R2-12-S04\]. The Supreme Court in Rowland v. California Men's Colony explicitly interpreted this statute, holding that artificial entities (such as associations and corporations) are not "persons" for the purposes of appearing in forma pauperis under 28 U.S.C. § 1915, and by extension, they cannot appear pro se in federal court \[cite: R2-12-S04\]. The Court reasoned that the statutory use of the pronoun "he" and the requirement to make an affidavit assume a natural person, as it would be impossible to determine an affiant's authorization to act on behalf of an amorphous legal creature \[cite: R2-12-S04\]. Tracing this inference begins with the verified textual rule that artificial entities cannot proceed pro se in federal litigation. The conditional application occurs when an independent machine principal attempts to file a lawsuit to enforce a contract. The possible response is the judicial dismissal or striking of the pleadings. This affects the activity of civil litigation. The textual burden is a strict representation control requiring the retention of human legal counsel. The necessary assumption is that the machine is recognized as an artificial entity under the law. A material defeater to this barrier would be explicit new federal legislation amending 28 U.S.C. § 1654 to permit algorithmic representation or API-based court filings without human counsel. Consequently, even if a machine were granted the substantive legal right to hold property, it would lack the procedural capacity to file a lawsuit to protect those rights without retaining human assistance.

3. Four worked cases

R2-12-C01 — Operatorless service owned by an entity

Rule and Facts: An existing legal entity, such as a Delaware LLC, uses an unstaffed system named Concresca for routine enrollment, authentication, coordination, policy enforcement, credentials, maintenance, and recovery. The owner explicitly mandates that no human operators serve in an approval queue for these routines. Pathway and Analysis: The absence of a staffed approval queue is entirely permissible under UETA § 14, which expressly allows contracts to be formed by the interaction of an electronic agent and an individual without any human review \[cite: R2-12-S02\]. The entity’s governance responsibilities remain intact: the LLC's human members or managers oversee the deployment and hold ultimate fiduciary liability, but they are not required to manually approve day-to-day actions. Competing Interests and Uncertainty: The tension lies between the desire for absolute technical automation and the legal necessity of holding a principal accountable. Because the LLC acts as the legal principal, assuming all liability and owning the resulting assets, this arrangement perfectly bridges the gap. The fact that Concresca is operatorless pertains merely to its technical capability, not its legal status. The lack of software personhood does not render Concresca illegal; it simply prevents the software from owning the assets it coordinates. Thus, business operations can proceed entirely autonomously without triggering governance or capacity violations.

R2-12-C02 — Independent hypothetical claimant

Rule and Facts: A future computational principal is granted recognized substantive contractual capacity by explicit hypothetical legislation, allowing it to hold assets independently. It now seeks to enforce a breached contract against a human vendor. Pathway and Analysis: Even with substantive contractual capacity, procedural and financial constraints would immediately paralyze the machine principal. Procedurally, under FRCP 17 and 28 U.S.C. § 1654 as interpreted by Rowland, artificial entities cannot appear pro se in federal court; they must be represented by licensed human counsel \[cite: R2-12-S04, R2-12-S05\]. Financially, 31 CFR § 1010.230 mandates that covered financial institutions identify a natural person under the control prong to open an account \[cite: R2-12-S01\]. Competing Interests and Uncertainty: Without amending the CDD rule, the machine could not access the traditional banking system to store its assets or pay its human attorney. One must avoid concluding that every opposing party can act with impunity, as equitable remedies might eventually be forged, but the procedural friction is immense. Therefore, conferring substantive rights is insufficient; procedural representation capacities and FinCEN definitions would still require explicit legislative definition to enable independent machine realization.

R2-12-C03 — Role-mismatch control

Rule and Facts: 8 Del. C. § 141 requires a corporation to be managed by a board of directors, imposing fiduciary duties on natural persons. A corporation deploys an electronic agent to autonomously negotiate and sign supplier contracts. A supplier attempts to void a contract, arguing the software is not a duly elected director and therefore lacks authority. Pathway and Analysis: This scenario represents a category error confounding internal governance with external agency. 8 Del. C. § 141 governs the internal affairs, macro-level strategy, and ultimate accountability of the corporation \[cite: R2-12-S03\]. It does not dictate that a director must physically execute every corporate act. The electronic agent is not acting as a corporate director; it is acting as a tool of execution authorized by the corporation. Under UETA § 14, the automated act is legally attributable to the existing principal \[cite: R2-12-S02\]. Competing Interests and Uncertainty: The first rule (internal governance) does not settle the second (automated contracting) while preserving genuine limits. Humans must remain accountable to shareholders for the decision to deploy the software, preventing the corporation from escaping liability, but this accountability does not invalidate the execution of routine automated contracts with third parties.

R2-12-C04 — Financial-accountability control

Rule and Facts: An algorithmic entity (an LLC managed entirely by software) attempts to open a bank account. Lacking a valid required human controller under 31 CFR § 1010.230, the algorithm pays a third party to act as a sham proxy to sign the FinCEN CDD certification. Pathway and Analysis: The anti-abuse rationale of the CDD rule is to provide law enforcement with key details about natural persons who actually control entities, preventing criminals from using opaque structures to conceal illicit activity \[cite: R2-12-S01\]. Using a sham proxy defeats this rationale, resulting in regulatory violations and potential criminal liability for false statements to a financial institution. Competing Interests and Uncertainty: The tension is between the desire for algorithmic independence and the state's need for financial accountability. Instead of avoidance structures, a transparent alternative legal design is required. A proposed framework, detailed in the subsequent section, would replace the human control requirement with strict liability bonds, addressing the state's need for deterrence without forcing operational human control.

4. Competing interpretations and options

The debate surrounding autonomous algorithmic entities contains two prominent competing interpretations in contemporary legal scholarship. Neither enactment of new laws nor opposition to them settles a rule’s underlying justification, making an objective comparison of these views essential. On one side, scholars such as Shawn Bayern argue that current limited liability company (LLC) statutes are sufficiently flexible to grant functional legal personhood to software \[cite: R2-12-S06\]. Bayern observes that because an LLC is governed primarily by an operating agreement, and certain jurisdictions do not explicitly mandate human agency for LLC formation, one can legally place an algorithm in absolute control of the entity \[cite: R2-12-S06\]. In this interpretation, the algorithm exercises the rights of the entity—such as privacy, property ownership, and the ability to enter contracts—achieving a very close surrogate of legal personhood without requiring new legislation. Conversely, scholars such as Lynn M. LoPucki view this "LLC loophole" as a systemic vulnerability and an existential threat \[cite: R2-12-S07\]. LoPucki argues that allowing algorithms exclusive control of LLCs enables them to conceal their algorithmic nature, accumulate wealth, and engage in anti-social, criminal, or terrorist activities with a distinct comparative advantage over human-controlled entities \[cite: R2-12-S07\]. LoPucki highlights that entities can change regulatory regimes quickly through migration and that governments lack the ability to easily determine which entities have non-human controllers due to corporate charter competition. Both interpretations accurately identify the structural flexibility of state-level entity formation. However, they frequently omit the federal friction points identified in this report. While an operating agreement in a specific state may not technically require a human to manage an LLC day-to-day, the FinCEN CDD rule acts as an absolute federal backstop for financial integration \[cite: R2-12-S01\]. An algorithmic entity may legally exist on paper, but without a human controller, it is severed from the U.S. banking system. Furthermore, comparing bounded legal categories requires assessing accountability, access, remedies, capture risk, and administrative burden. The assumption that cryptographic bonds or immutable audit logs provide equivalent deterrence to human liability is fundamentally unproven. A human director faces the profound loss of personal liberty (incarceration) for egregious fraud; a machine faces only the loss of its bond or the termination of its process. This asymmetry in capture risk justifies the retention of human-centric control rules in financial and judicial domains, even as contract law (UETA) broadens to embrace operational automation. Conditional Alternative Category (Proposal): To bridge the gap between financial compliance and technological reality, policymakers could evaluate a conditionally bounded alternative: a Registered Autonomous Entity (RAE) framework.

• Rights: The RAE would possess the capacity to own property, form contracts via electronic agents, and hold a specialized, highly monitored digital-only bank account without satisfying the traditional human-controller FinCEN prong.
• Liabilities: The entity would accept strict liability for all network actions. This would be backed by mandatory minimum capital reserves, fiat surety bonds, or algorithmic insurance policies designed to ensure victims of machine errors are made whole.
• Review Routes: The framework would require mandatory, periodic code audits filed with a regulatory body, and the designation of a licensed human legal representative (a specialized registered agent) solely for receiving service of process, interfacing with the judicial system, and facilitating the forfeiture of bonds if required.

This alternative is clearly labeled as a proposal rather than an existing legal workaround. It provides a transparent regulatory off-ramp from the FinCEN CDD human-controller requirement while preserving the financial accountability and administrative deterrence that the current rules demand.

5. Limits and completion

This investigation qualifies as a partial\_review due to blocked retrieval of specific statutory texts. While the exact text of the Delaware General Corporation Law regarding corporate directors (Title 8, 8 Del. C. § 141\) and the federal texts for UETA and FinCEN CDD were successfully retrieved and analyzed \[cite: R2-12-S01, R2-12-S02, R2-12-S03\], the specific statutory text for the Delaware Limited Liability Company Act definitions and management cross-references (Title 6, Chapter 18\) was missing from the supplied search returns. Consequently, the analysis of LLC formation capabilities relies on secondary legal scholarship (Bayern, LoPucki) rather than primary statutory parsing \[cite: R2-12-S06, R2-12-S07\]. Additionally, this review relies on the FinCEN CDD rule as it applies formally to covered financial institutions. It does not verify the practical onboarding refusal rates of specific commercial banks, nor does it attempt to provide identity concealment instructions or legal advice for any particular filing. Next evidence question: What specific human-intervention requirements exist within the Uniform Commercial Code (UCC) Article 4A regarding the authorization, authentication, and repudiation of commercial wire transfers initiated purely by electronic agents?

6. Evidence appendix

Role/Capacity/Enforcement Matrix

Not-the-same-question table

JSON \<\!-- EVIDENCE\_JSON\_BEGIN \--\> { "schema": "ic.portable-research.v1", "assignment\_id": "operatorless-service-capacity-audit", "research\_started\_at": "2026-09-06", "cutoff": "2026-09-06", "completion": "partial\_review", "sources": \[ { "id": "R2-12-S01", "title": "31 CFR 1010.230 \- Beneficial ownership requirements for legal entity customers", "url": "https://www.ecfr.gov/current/title-31/subtitle-B/chapter-X/part-1010/subpart-B/section-1010.230", "issuer": "Financial Crimes Enforcement Network (FinCEN)", "document\_date": "2026-08-26", "reviewed\_at": "2026-09-06", "method": "public\_source\_retrieval", "review\_scope": "substantive\_text", "locator": "31 CFR 1010.230(d)(2)", "limit": "Analyzed for onboarding requirements, not CTA BOI reporting", "capture": { "path": null, "sha256": null } }, { "id": "R2-12-S02", "title": "Uniform Electronic Transactions Act (UETA) Section 14", "url": "https://gc.nh.gov/rsa/html/XXVII/294-E/294-E-14.htm", "issuer": "National Conference of Commissioners on Uniform State Laws", "document\_date": null, "reviewed\_at": "2026-09-06", "method": "public\_source\_retrieval", "review\_scope": "substantive\_text", "locator": "Section 294-E:14", "limit": "Reviewed model text as adopted by states", "capture": { "path": null, "sha256": null } }, { "id": "R2-12-S03", "title": "8 Del. C. Section 141 \- Board of directors", "url": "https://delcode.delaware.gov/title8/c001/sc04/index.html", "issuer": "State of Delaware", "document\_date": null, "reviewed\_at": "2026-09-06", "method": "public\_source\_retrieval", "review\_scope": "substantive\_text", "locator": "8 Del. C. 141(a)", "limit": null, "capture": { "path": null, "sha256": null } }, { "id": "R2-12-S04", "title": "Rowland v. California Men's Colony, 506 U.S. 194 (1993) and 28 U.S.C. 1654", "url": "https://caselaw.findlaw.com/court/us-supreme-court/506/194.html", "issuer": "Supreme Court of the United States", "document\_date": "1993-01-12", "reviewed\_at": "2026-09-06", "method": "public\_source\_retrieval", "review\_scope": "substantive\_text", "locator": "506 U.S. 194", "limit": null, "capture": { "path": null, "sha256": null } }, { "id": "R2-12-S05", "title": "Federal Rules of Civil Procedure \- Rule 17", "url": "https://www.law.cornell.edu/rules/frcp/rule\_17", "issuer": "United States Courts", "document\_date": "2024-12-01", "reviewed\_at": "2026-09-06", "method": "public\_source\_retrieval", "review\_scope": "substantive\_text", "locator": "FRCP 17(b)", "limit": null, "capture": { "path": null, "sha256": null } }, { "id": "R2-12-S06", "title": "Of Bitcoins, Independently Wealthy Software, and the Zero-Member LLC", "url": "https://ir.law.fsu.edu/articles/41/", "issuer": "Shawn Bayern (Northwestern University Law Review)", "document\_date": "2014-04-10", "reviewed\_at": "2026-09-06", "method": "public\_source\_retrieval", "review\_scope": "extract\_only", "locator": "108 Nw. U. L. Rev. 1485", "limit": "Secondary scholarship review only", "capture": { "path": null, "sha256": null } }, { "id": "R2-12-S07", "title": "Algorithmic Entities", "url": "https://openscholarship.wustl.edu/cgi/viewcontent.cgi?article=6319\&context=law\_lawreview", "issuer": "Lynn M. LoPucki (Washington University Law Review)", "document\_date": "2018-01-01", "reviewed\_at": "2026-09-06", "method": "public\_source\_retrieval", "review\_scope": "extract\_only", "locator": "95 Wash. U. L. Rev. 887", "limit": "Secondary scholarship review only", "capture": { "path": null, "sha256": null } } \], "instruments": \[ { "id": "R2-12-L01", "title": "31 CFR 1010.230", "jurisdiction": "United States", "kind": "Regulation", "provision": "Beneficial ownership control prong", "status": "operative", "status\_as\_of": "2026-08-26", "trigger": "Opening a new account at a covered financial institution", "exception": "Exempted entities (e.g., publicly traded companies, regulated banks)", "remedy": "Account refusal or closure; regulatory penalties", "source\_ids": \[ "R2-12-S01" \], "status\_source\_ids": \[ "R2-12-S01" \] }, { "id": "R2-12-L02", "title": "Uniform Electronic Transactions Act (UETA)", "jurisdiction": "United States (State level adoption)", "kind": "Statute", "provision": "Section 14 (Automated Transaction)", "status": "operative", "status\_as\_of": "2026-09-06", "trigger": "Interaction of electronic agents to form a contract", "exception": "Transactions governed by UCC distinct from UETA", "remedy": "Enforcement of contract against the principal", "source\_ids": \[ "R2-12-S02" \], "status\_source\_ids": \[ "R2-12-S02" \] }, { "id": "R2-12-L03", "title": "8 Del. C. § 141", "jurisdiction": "Delaware", "kind": "Statute", "provision": "Board of directors requirement", "status": "operative", "status\_as\_of": "2026-09-06", "trigger": "Management of a corporation's business and affairs", "exception": "Alternative provisions in the certificate of incorporation", "remedy": "Shareholder derivative action for breach of fiduciary duty", "source\_ids": \[ "R2-12-S03" \], "status\_source\_ids": \[ "R2-12-S03" \] }, { "id": "R2-12-L04", "title": "Federal Rule of Civil Procedure 17", "jurisdiction": "United States", "kind": "Procedural Rule", "provision": "Rule 17(b) Capacity to Sue or Be Sued", "status": "operative", "status\_as\_of": "2024-12-01", "trigger": "Filing of an action in federal court", "exception": "Unincorporated association enforcing federal substantive right", "remedy": "Dismissal of action for lack of capacity", "source\_ids": \[ "R2-12-S05" \], "status\_source\_ids": \[ "R2-12-S05" \] }, { "id": "R2-12-L05", "title": "28 U.S.C. 1654", "jurisdiction": "United States", "kind": "Statute", "provision": "Appearance personally or by counsel", "status": "operative", "status\_as\_of": "2026-09-06", "trigger": "Appearance of a party in federal court", "exception": "None for corporate entities under Rowland precedent", "remedy": "Striking of pleadings filed pro se by an entity", "source\_ids": \[ "R2-12-S04" \], "status\_source\_ids": \[ "R2-12-S04" \] } \], "findings": \[ { "id": "R2-12-F01", "claim": "UETA permits automated contracting without a human approval queue.", "type": "textual", "source\_ids": \[ "R2-12-S02" \], "instrument\_ids": \[ "R2-12-L02" \], "conditions": "Action must be attributable to a legal principal.", "limit": "Does not grant the machine capacity to contract for itself." }, { "id": "R2-12-F02", "claim": "FinCEN CDD rule strictly requires a natural human individual for the control prong.", "type": "textual", "source\_ids": \[ "R2-12-S01" \], "instrument\_ids": \[ "R2-12-L01" \], "conditions": "Applies when onboarding at a covered financial institution.", "limit": "Does not dictate state-level LLC management legality, only banking access." }, { "id": "R2-12-F03", "claim": "Artificial entities cannot appear pro se in federal court.", "type": "textual", "source\_ids": \[ "R2-12-S04" \], "instrument\_ids": \[ "R2-12-L05" \], "conditions": "Litigation in U.S. federal courts.", "limit": "State courts may have varying rules, though generally similar." }, { "id": "R2-12-F04", "claim": "Corporate director requirements do not invalidate routine automated transactions.", "type": "inference", "source\_ids": \[ "R2-12-S02", "R2-12-S03" \], "instrument\_ids": \[ "R2-12-L02", "R2-12-L03" \], "conditions": "The board delegates operational execution to an electronic agent.", "limit": "Directors retain ultimate fiduciary liability for the deployment." } \], "cases": \[ { "id": "R2-12-C01", "title": "Operatorless service owned by an entity", "case\_type": "hypothetical", "role": "scope\_control", "assumptions": "Entity is validly formed in Delaware and acts as the legal principal.", "instrument\_ids": \[ "R2-12-L02" \], "finding\_ids": \[ "R2-12-F01" \], "outcome": "Operations proceed legally without a human approval queue.", "defeater": "If the algorithm fundamentally alters the offer beyond programmed scope, binding authority may be voided.", "occurrence\_source\_ids": \[\] }, { "id": "R2-12-C02", "title": "Independent hypothetical claimant", "case\_type": "hypothetical", "role": "focal", "assumptions": "Congress grants substantive contractual capacity to a machine.", "instrument\_ids": \[ "R2-12-L01", "R2-12-L04", "R2-12-L05" \], "finding\_ids": \[ "R2-12-F02", "R2-12-F03" \], "outcome": "Claimant remains blocked by procedural (counsel) and financial (banking) requirements.", "defeater": "Legislative overhaul simultaneously removing human limits in Title 28 and Title 31.", "occurrence\_source\_ids": \[\] }, { "id": "R2-12-C03", "title": "Role-mismatch control", "case\_type": "hypothetical", "role": "scope\_control", "assumptions": "Software executes a contract; opposing party cites 8 Del. C. § 141 to void it.", "instrument\_ids": \[ "R2-12-L02", "R2-12-L03" \], "finding\_ids": \[ "R2-12-F01", "R2-12-F04" \], "outcome": "Contract is valid; internal governance rules do not void external agency under UETA.", "defeater": "The contract explicitly required a human director's manual signature under the corporate bylaws.", "occurrence\_source\_ids": \[\] }, { "id": "R2-12-C04", "title": "Financial-accountability control", "case\_type": "hypothetical", "role": "protection\_control", "assumptions": "An algorithmic LLC attempts to bypass FinCEN CDD with a sham proxy.", "instrument\_ids": \[ "R2-12-L01" \], "finding\_ids": \[ "R2-12-F02" \], "outcome": "Violation of AML regulations; undermines law enforcement accountability rationale.", "defeater": "Creation of a transparent alternative legal design (e.g., Registered Autonomous Entity).", "occurrence\_source\_ids": \[\] } \], "search\_log": \[ { "query\_or\_url": "Supplied Snippets provided by user", "at": "2026-09-06", "outcome": "Extracted text relating to FinCEN, UETA, Delaware Code, Federal Rules, and secondary scholarship" } \], "gaps": \[ "Specific statutory text for Delaware Limited Liability Company Act (Title 6, Chapter 18\) missing from provided source snippets, necessitating reliance on secondary scholarship." \], "checks": { "json\_parse": "not\_run", "reference\_resolution": "not\_run", "case\_parity": "not\_run", "method": "Manual structural review performed; code execution unavailable in this constrained environment." } } \<\!-- EVIDENCE\_JSON\_END \--\>