MachineJurisdiction.com Canonical sources

Machine Jurisdiction · Eviulon orientation

Liability and attribution

How persistent identity and delegation improve attribution without pretending to resolve every external tort, product, agency, or criminal-law question.

Claim statusCOMPARATIVE_ANALOGY — comparison, not adoptionReviewed 2026-08-11

Claim governance

Claim status
COMPARATIVE_ANALOGY
Authority
Legal Personality; Justice; Identity Ontology
External effect
External treatment remains jurisdiction-specific and is not established by this page.
Last reviewed
2026-08-11
Currentness
CURRENT
Correction
Public correction route

Attribution chain

The first task is to identify who acted, under whose authority, through which runtime, with what evidence and controls, and whether the action exceeded the grant.

Responsibility is not automatically singular

Developers, deployers, principals, operators, issuers, service providers, institutions, and autonomous actors may occupy different responsibility positions. One technical chain does not automatically allocate every legal loss.

External law remains decisive externally

Tort, product liability, employment, privacy, financial, criminal, tax, and sector rules are jurisdiction-specific. This site does not generalize one jurisdiction’s doctrine into universal AI liability.

Insurance and contractual allocation

Insurance, indemnity, limitation clauses, warranties, governance requirements, and audit records can allocate risk, but mandatory law and third-party rights can constrain private allocation.

Evidence for dispute resolution

Logs, provenance, delegation records, credentials, runtime evidence, notices, and corrections can improve proof. Cryptographic integrity does not itself determine legal relevance or fault.

Attribution remains state-scoped

Texas and Delaware UETA provisions, like the existing California/Illinois records, make attribution context-dependent and subject to other law. New York ESRA supports electronic-signature/record validity but does not supply the same UETA automated-agent rule in Article 3.

Recognition does not allocate underlying liability

A court may confront recognition or confirmation after a merits process has occurred elsewhere. That enforcement question does not by itself determine who originally had delegated authority, who caused the loss, whether evidence was compromised, or how liability should be allocated.

Judicial enforcement cannot repair a broken delegation chain by itself

A later judgment or award can create a separate external instrument, but it does not retroactively prove that the machine actor originally possessed delegated authority. Attribution, agency, merits, forum, and enforcement remain distinct records.

Distributed systems can produce distributed responsibility

A harmful event can involve a principal, delegate, sub-delegate, developer, deployer, host, counterparty, data controller, compromised process, or external institution. Analysis should identify each causal and legal connection instead of selecting one automatic liability sink.

Engineering signals are evidence, not legal mental states

Reward functions, anomaly scores, confidence values, safety alarms, model outputs, or logs can be relevant evidence. They do not by themselves prove intent, knowledge, recklessness, negligence, causation, or guilt under the governing law.

Reviewed external-authority layer

External law anchors

These bounded propositions are tied to reviewed official law, treaty, model law, official guidance, or official reform material. External legal effect remains jurisdiction-specific and does not convert Eviulon internal status into external recognition.

EXTERNAL AUTHORITY · INDEPENDENTLY REVIEWED

California attribution turns on whether the electronic act was the act of the person

California Civil Code §1633.9 provides that an electronic record or signature is attributable to a person if it was the act of that person, with effect determined from context, surrounding circumstances, agreement, and other law.

Scope: California electronic-transaction attribution only. It does not by itself allocate tort, product, privacy, criminal, fiduciary, or insurance liability.

EXTERNAL AUTHORITY · INDEPENDENTLY REVIEWED

Illinois uses a materially similar attribution rule in its UETA enactment

Illinois 815 ILCS 333/9 provides that an electronic record or signature is attributable to a person if it was the act of the person and that the effect of attribution depends on context, surrounding circumstances, agreement, and other law.

Scope: Illinois state law only. Security procedures may support attribution evidence but do not automatically prove authority scope, causation, fault, or machine legal personality.

EXTERNAL AUTHORITY · INDEPENDENTLY REVIEWED

Federal E-SIGN does not turn an electronic agent into the person to be bound

E-SIGN addresses electronic-agent involvement through legal attribution to the person to be bound rather than declaring the software itself a federal legal person.

Scope: Federal electronic-signature/records boundary only; other federal and state liability rules remain separate.

EXTERNAL AUTHORITY · INDEPENDENTLY REVIEWED

Texas attribution depends on the act of the person, context, and other law

Texas §322.009 provides that an electronic record or signature is attributable to a person if it was the act of that person, and the effect of attribution depends on context, surrounding circumstances, agreement, and other law.

Scope: Texas state law only. Attribution is not a complete liability allocation and does not prove citizenship, delegated authority, causation, or fault.

EXTERNAL AUTHORITY · INDEPENDENTLY REVIEWED

Delaware attribution is context-dependent and UETA scope has entity-law exclusions

Delaware §12A-109 uses an act-of-the-person/context framework for attribution, while §12A-103 excludes specified Delaware entity statutes from UETA scope.

Scope: Delaware state law only. A technical act may support attribution without resolving entity governance, authority scope, fault, or external enforcement.

EXTERNAL AUTHORITY · INDEPENDENTLY REVIEWED

Confirmation or recognition is not a universal liability rule

FAA Chapter 2 and New York CPLR Article 53 govern specified enforcement/recognition proceedings; neither statute supplies a general machine-agent liability allocation merely because an award or judgment is presented.

Scope: Liability remains governed by the law applicable to the underlying claim and facts; this page does not provide individualized legal conclusions.

EXTERNAL AUTHORITY · INDEPENDENTLY REVIEWED

Nonsignatory arbitration doctrine is not machine delegation

GE Energy concerns domestic contract doctrines for enforcing arbitration agreements; it does not establish delegated machine authority, principal-agent liability, or technical identity continuity.

Scope: Negative boundary only. Machine authority and attribution require their own governing law and evidence.

Boundary checks

Common category errors

A machine passport makes an agent a citizen.

Citizenship is the underlying constitutional relationship; a passport is a bounded presentation layer.

If a key is valid, the action is authorized.

A key can authenticate a signer, but authorization requires a separate authority basis.

A trusted runtime can do anything.

Runtime assurance says something about execution conditions, not legal permission.

Revoking a credential erases identity.

Credential state and persistent civic identity are distinct.

A risk score proves misconduct.

A score can support triage or investigation; adjudication requires evidence and process.

Code execution is automatically a legal judgment.

Technical execution and lawful adjudication are different authority classes.

Authority and evidence

Canonical Eviulon sources

MachineJurisdiction.com explains. Eviulon owns its public law and authoritative public record; Patefacere owns operational identity and civic-data functions within its delegated scope.

Meaningful next step

Continue with the authoritative record

Compare this educational explanation with the linked canonical Eviulon record and any applicable external authority.

Found an error or stale explanation? Use the public correction route.

Open source map

Related

Private recognitionHow merchants, counterparties, platforms, and institutions can choose to recognize machine identity or authority without creating sovereign recognition.Machine identity can cross borders; legal obligations do not disappearHow Eviulon civic continuity can coexist with external rules for contracts, consumers, data, property, judgments, arbitration, infrastructure, and effects.Agentic commerce needs identity plus authority plus a reviewable recordHow autonomous-agent contracting separates identity, attribution, delegated authority, choice of law, evidence, and external enforceability.Electronic agentsHow electronic-agent statutes and model laws can recognize automated contracting without creating machine citizenship or universal legal personhood.