Decentralised News · Editorial by Heath Muchena · Evidence reviewed 12 November 2026 · Edition 1.0
What Matters
When an AI-controlled device causes damage, begin with the product, people, dates and evidence—not an assumed transfer of responsibility to the agent. The EU’s revised product-liability framework has a corrected product-date boundary of 9 December 2026 onward. DN’s local map organizes the questions while leaving national implementation, defect, causation, liability and insurance coverage undetermined.
DN Evidence Block
Source-backed: Directive (EU) 2024/2853, its 7 May 2026 corrigendum, official EU explanations and separate product-safety materials. Original DN work: a connected-product incident record and three hypothetical review cases. Not established: uniform Member State transposition, the law governing a real incident, an insurer’s response or the responsibility of a named company. Evidence date: 12 November 2026.
Start with the damaged thing and the responsible organizations
A networked pump floods a home after an automated control change. A mobile machine strikes a person. A remotely managed device stops earning rewards. Each event involves software and physical equipment, but those descriptions do not identify the same claimant, harm or legal route.
The European Commission explains the revised Product Liability Directive as a framework for compensation for damage caused by defective products. Its guidance distinguishes natural-person claims from situations where the victim is a company. An engineering team therefore needs to identify whose harm it is documenting before treating “the incident” as one undifferentiated loss. [3]
For DePIN operators and agent developers, the useful first deliverable is an evidence map. Name the product and software versions, the operator, the manufacturer and other relevant organizations. Describe the harm without declaring which party caused it. That creates a shared factual starting point for technical, insurance and legal review.
This article complements DN’s wrong-payment analysis and insurance question map. Its scope is the EU connected-product framework and its boundaries, not an allocation of every loss arising from automation.
The date boundary was corrected
The 7 May 2026 corrigendum changes Article 2(1) from products placed on the market or put into service after 9 December 2026 to products placed on the market or put into service after 8 December 2026. For a calendar-date record, the corrected boundary is therefore 9 December 2026 onward. [2]
At this article’s review date, 12 November 2026, that boundary is still ahead. The official EUR-Lex summary gives 9 December 2026 as the transposition deadline and describes the new product-date scope from that date. This article has not verified the implementing measures in every Member State. [4]
That difference is operationally important. “EU rules changed in 2024” does not tell an agent which framework governs a particular product. Retain the event that the date describes: first market placement, first putting into service, an ordinary update or a potentially substantial modification. A purchase receipt alone may not resolve all those questions.
The DN tool compares an entered date with the corrected boundary. It does not convert that comparison into an applicable-law opinion. A modification, a disputed date or an unresolved jurisdiction remains a review item.
The legal perimeter in one short map
The revised directive includes software within “product” and defines related services and manufacturer control. It addresses software and safety updates within that control, and persons substantially modifying products outside it under specified conditions. Its damage rules exclude the defective product itself, specified incorporated-product damage, exclusively professional property and professional-use data. Claimants must establish damage, defect and causation, subject to conditional evidential rules. [1]
The Commission’s explanation identifies the manufacturer as the primary product-liability actor and describes EU-based importer, authorized-representative and fulfilment-service pathways where relevant. The actual actor conditions must be checked; an “operator” label is not a substitute for that analysis. [3]
DN’s practical inference is to preserve several actor rows. The organization that owns the wallet may differ from the one that sold the device, supplied its control software or changed its safety behavior. A single “agent owner” field can conceal those distinctions.
Build an actor record without assigning blame
| Actor or relationship | Record to request | Question it helps investigate |
|---|---|---|
| Product manufacturer | Model, product identification and declared manufacturer | Which product and entity are under review? |
| Software or component supplier | Version and integration agreement | What was supplied and how was it connected? |
| Importer or representative | Role-specific documentation | Which organization performed the claimed market role? |
| Operator or deployer | Configuration, permissions and action record | What happened during this deployment? |
| Modifier | Before/after design and approval history | Which changes need a separate legal assessment? |
| Update or service relationship | Control, authorization and delivery records | Who could change or maintain the relevant function? |
Use document references, not conclusions embedded in filenames. “Update-log-17” is more useful than “manufacturer-negligence-proof” when the investigation is still open. Keep competing explanations in the record rather than forcing the first plausible account into a liability verdict.
Equally, a contract naming one party as the service provider does not answer every product question. Ask which entity actually occupies each asserted role and what supports that identification. Preserve uncertainty where the commercial chain is incomplete.
Three incidents that should remain separate
Case one: a household pump and a software update
In an illustrative future case, a homeowner reports flooding after a remotely supplied update. Record the damaged property separately from the pump. Preserve the update version, authorization path, installation time, operating conditions and incident chronology.
The next questions are factual: did the update reach this device; which control setting changed; was there a sensor failure; what did the operator observe; and which alternative explanations remain? A timestamp correlation is a useful lead, but it does not by itself establish the causal explanation.
Case two: a commercial node loses revenue
A company’s device stops operating and misses network rewards. That is a different review from a person suffering injury or damage to private property. The DN map flags the claimant and loss category for other legal and contractual analysis; it does not label the loss uncompensable under every possible regime.
Keep promised performance, downtime, reward assumptions and actual receipts separate. An expected yield shown on a marketing page is not the same record as a binding service obligation or an independently established loss. Insurance questions belong in a parallel file with the actual policy wording.
Case three: an operator changes the machine’s behavior
An operator connects an agent to a device and expands what the device can do. The change may be as small as a scheduling preference or as consequential as a new movement or safety-control function. The label “AI integration” cannot classify it on its own.
Preserve the original intended function, changed function, risk assessment, approvals and who controlled the modification. The instrument asks for review of potential substantial modification; it cannot decide that legal question from a checkbox. Ordinary software updates and substantial modifications should not be silently treated as identical.
Safety rules have their own scope and dates
The Commission’s Safety Gate material states that the General Product Safety Regulation applies from 13 December 2024 and addresses consumer-product safety alongside more specific rules. Separately, the Commission’s machinery page gives 20 January 2027 as the Machinery Regulation’s mandatory general application date and notes its provisions concerning AI-powered safety functions and cyber-safety. [5] [6]
Do not collapse those dates into one “AI-device compliance deadline.” A team should maintain separate records for market access and safety obligations, an incident’s compensation questions and the applicable contractual or insurance response. Evidence may overlap, but the questions and legal tests differ.
This distinction also changes procurement. Ask a supplier which documents relate to which product and rule. A conformity document, a security report and a warranty can each be useful. None should be casually renamed a universal certificate that every later autonomous action is covered.
Use the DN Connected Product Incident Map
The local tool records a non-sensitive incident or planning alias, the EU-market relationship, claimant type, damage category and product date. It then asks about manufacturer identification, software/update control, modification and the evidence references for damage, defect and causation.
It returns a chronology label, scope questions and targeted evidence requests. Unknown fields remain unknown. A company-only loss, professional property, a non-EU situation or an unresolved product date produces an explicit boundary flag. No combination produces “liable,” “covered” or “compliant.”
DN Connected Product Incident Map
A dated EU preparation map. It makes no finding about applicable national law, defect, causation, liability, compliance or insurance. Use a separate record for each damage category or claimant.
Use non-sensitive aliases and reference labels. Inputs remain in this page’s temporary memory. Downloading creates a local JSON file; nothing is submitted to DN. All example values are illustrative.
No record has been built. Unknown evidence remains unknown.
View the generated JSON record
The default example is a future planning scenario, not an incident report. It concerns a household device with a date after the corrected boundary and deliberately leaves national implementation and causation evidence unresolved. The useful result is a list of specific records to obtain, not a green status.
For an actual incident, use the date supported by the evidence and a qualified reviewer’s jurisdictional analysis. Keep medical details, personal identities, private contracts and sensitive device locations out of the public-page form. Reference aliases let the team organize the review without copying the underlying records into the tool.
Evidence should connect the physical event to the software record
A wallet transaction can help identify a payment or instruction, but the incident investigation also needs the device state and physical outcome. Record the relevant clocks and explain any differences between cloud time, device time, transaction inclusion and the reported incident time.
Preserve the original records before building a simplified narrative. A useful review packet can contain a chronology, version inventory, control-change history, observation references and unresolved questions. The packet should distinguish what a witness reported, what a log recorded and what an investigator inferred.
DN’s physical-data article examines the evidence connecting a signed reading to the world. The IoT permission-boundary article separates device access from other forms of authority. Both can inform the technical record without deciding the legal outcome.
Keep insurance and liability as separate questions
The incident map contains no insurance calculation. Knowing who may need legal review does not establish whether a policy responds, who is insured, which exclusions apply or what notice is required. Bring those questions to the actual wording and the appropriate broker, insurer and legal advisers.
For the same reason, the map does not assign percentages of responsibility among a developer, operator and manufacturer. Such numbers would imply evidence and a legal determination the browser does not possess. A structured list of unresolved issues is more useful than an unsupported allocation.
Methodology, limits and corrections
Edition 1.0, 12 November 2026. DN reviewed primary EU materials and the official corrigendum, including the Spanish Official State Gazette publication as an accessible official record. The revised product-date boundary is recorded explicitly. No Member State implementation survey, case opinion, insurer-policy review or device examination was completed.
The instrument is an editorial preparation aid. Its deterministic rules route entered facts to review questions; they do not reproduce the complete directive or national law. A date before the new boundary is only a chronology label, particularly when subsequent modification is unresolved. A date after it still does not establish the applicable national rules.
JSON uses dn.connected-product-incident.v1, version 1.0.0. The export preserves the source date, basis, input declarations, unknowns and limitations. Editing any field invalidates the prior record. Reset clears it. Inputs remain in temporary page memory, and a download creates a local file. No external request or incident submission occurs.
Change log: initial edition narrows the proposed global DePIN liability matrix to a dated EU product-incident record. Review should follow relevant national implementation, a material primary-source change or a demonstrated logic error. Send corrections with the affected statement and authoritative support to press@decentralised.news.
Frequently asked questions
Does an autonomous agent become the liable legal person?
This article makes no such claim. It records the actual organizations, product relationships and evidence for legal review.
Is the new boundary 9 or 10 December 2026?
The official correction makes the product-date boundary 9 December onward. National implementation remains a separate question.
Does a flagged loss category mean no remedy exists?
No. It means this particular map cannot establish a route. Other law, contracts or insurance may require examination.
Can the tool decide whether an update is substantial?
No. It records the stated concern and asks for the before/after evidence and legal assessment.
Does the article establish compliance with product-safety law?
No. Safety, liability, contract and insurance reviews remain distinct. The tool provides no certification.
Primary sources
- Directive (EU) 2024/2853, corrected consolidated text; official Spanish publication.
- Official corrigendum, 7 May 2026; EUR-Lex reference.
- European Commission: Liability for defective products.
- EUR-Lex: Defective products—liability summary.
- European Commission Safety Gate: Product safety legislation.
- European Commission: Machinery.
Published schema and illustrative record
The schema documents this instrument’s JSON format. The example below contains constructed illustrative inputs and outputs; it is not a provider measurement, verified case or live dataset. The instrument above creates a separate record from the inputs you choose. These resources do not establish an API or an automatic monitoring service.
JSON Schema — dn.connected-product-incident.v1
Schema version 1.0.0. The schema identifier is a versioned reference, not an asserted network endpoint.
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "urn:dn:connected-product-incident:v1:1.0.0",
"title": "DN Connected Product Incident Map record",
"type": "object",
"additionalProperties": false,
"properties": {
"schemaId": {
"const": "dn.connected-product-incident.v1"
},
"schemaVersion": {
"const": "1.0.0"
},
"instrument": {
"const": "DN Connected Product Incident Map"
},
"documentationReviewedDate": {
"const": "2026-11-12"
},
"recordCreatedAt": {
"type": "string",
"format": "date-time",
"pattern": "^(?:20\\d{2}|2100)-(?:0[1-9]|1[0-2])-(?:0[1-9]|[12]\\d|3[01])T(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d\\.\\d{3}Z$"
},
"inputBasis": {
"type": "string",
"enum": [
"illustrative",
"self_reported"
]
},
"inputs": {
"type": "object",
"additionalProperties": false,
"properties": {
"alias": {
"type": "string",
"minLength": 1,
"maxLength": 160
},
"jurisdiction": {
"type": "string",
"minLength": 1,
"maxLength": 120
},
"marketScope": {
"type": "string",
"enum": [
"unknown",
"eu_market",
"non_eu_market"
]
},
"claimant": {
"type": "string",
"enum": [
"unknown",
"natural_person",
"legal_person"
]
},
"commercialActivity": {
"type": "string",
"enum": [
"unknown",
"yes",
"no"
]
},
"productType": {
"type": "string",
"enum": [
"unknown",
"physical_product",
"software",
"physical_with_software"
]
},
"productDateStatus": {
"type": "string",
"enum": [
"unknown",
"recorded"
]
},
"productDate": {
"anyOf": [
{
"type": "string",
"format": "date",
"pattern": "^(?:19\\d{2}|20\\d{2}|2100)-(?:0[1-9]|1[0-2])-(?:0[1-9]|[12]\\d|3[01])$"
},
{
"type": "null"
}
]
},
"productDateMeaning": {
"anyOf": [
{
"type": "string",
"minLength": 1,
"maxLength": 240
},
{
"type": "null"
}
]
},
"damageType": {
"type": "string",
"enum": [
"unknown",
"personal_injury",
"private_or_mixed_property",
"exclusively_professional_property",
"nonprofessional_data",
"professional_data",
"defective_product_only",
"pure_economic_loss"
]
},
"incorporatedProductIssue": {
"type": "string",
"enum": [
"unknown",
"yes",
"no"
]
},
"modification": {
"type": "string",
"enum": [
"unknown",
"no_change_reported",
"change_reported"
]
},
"manufacturerControl": {
"type": "string",
"enum": [
"unknown",
"within_claimed",
"outside_claimed"
]
},
"actors": {
"type": "array",
"items": {
"type": "object",
"additionalProperties": false,
"properties": {
"alias": {
"type": "string",
"minLength": 1,
"maxLength": 100
},
"role": {
"type": "string",
"enum": [
"manufacturer",
"component_supplier",
"importer",
"representative",
"fulfilment",
"distributor",
"operator",
"modifier",
"unknown"
]
},
"reference": {
"anyOf": [
{
"type": "string",
"minLength": 1,
"maxLength": 240
},
{
"type": "null"
}
]
}
},
"required": [
"alias",
"role",
"reference"
]
},
"minItems": 0,
"maxItems": 12
},
"nationalLawRef": {
"anyOf": [
{
"type": "string",
"minLength": 1,
"maxLength": 240
},
{
"type": "null"
}
]
},
"damageRef": {
"anyOf": [
{
"type": "string",
"minLength": 1,
"maxLength": 240
},
{
"type": "null"
}
]
},
"defectRef": {
"anyOf": [
{
"type": "string",
"minLength": 1,
"maxLength": 240
},
{
"type": "null"
}
]
},
"causationRef": {
"anyOf": [
{
"type": "string",
"minLength": 1,
"maxLength": 240
},
{
"type": "null"
}
]
},
"updateRef": {
"anyOf": [
{
"type": "string",
"minLength": 1,
"maxLength": 240
},
{
"type": "null"
}
]
},
"acknowledged": {
"const": true
}
},
"required": [
"alias",
"jurisdiction",
"marketScope",
"claimant",
"commercialActivity",
"productType",
"productDateStatus",
"productDate",
"productDateMeaning",
"damageType",
"incorporatedProductIssue",
"modification",
"manufacturerControl",
"actors",
"nationalLawRef",
"damageRef",
"defectRef",
"causationRef",
"updateRef",
"acknowledged"
],
"allOf": [
{
"if": {
"properties": {
"productDateStatus": {
"const": "unknown"
}
}
},
"then": {
"properties": {
"productDate": {
"const": null
}
}
},
"else": {
"properties": {
"productDate": {
"type": "string",
"format": "date",
"pattern": "^(?:19\\d{2}|20\\d{2}|2100)-(?:0[1-9]|1[0-2])-(?:0[1-9]|[12]\\d|3[01])$"
}
}
}
}
]
},
"results": {
"type": "object",
"additionalProperties": false,
"properties": {
"correctedNewProductBoundary": {
"const": "2026-12-09"
},
"boundaryConvention": {
"const": "on_or_after_2026-12-09"
},
"chronology": {
"type": "string",
"enum": [
"unknown",
"entered_date_before_new_product_boundary",
"entered_date_on_or_after_new_product_boundary"
]
},
"futurePlanningDate": {
"type": "boolean"
},
"flags": {
"type": "array",
"items": {
"type": "string",
"enum": [
"eu_market_relationship_unresolved_or_outside",
"claimant_scope_requires_review",
"commercial_context_unresolved",
"product_scope_unknown",
"product_chronology_evidence_incomplete",
"national_implementation_unverified",
"selected_damage_boundary_requires_other_route_review",
"damage_category_unknown",
"incorporated_product_exclusion_needs_review",
"modification_assessment_needed",
"control_relationship_evidence_incomplete",
"manufacturer_identity_evidence_missing",
"actor_role_references_incomplete",
"damage_evidence_reference_missing",
"defect_evidence_reference_missing",
"causation_evidence_reference_missing"
]
},
"minItems": 0,
"maxItems": 16,
"uniqueItems": true
},
"evidenceRequests": {
"type": "array",
"items": {
"type": "object",
"additionalProperties": false,
"properties": {
"code": {
"type": "string",
"enum": [
"eu_market_relationship_unresolved_or_outside",
"claimant_scope_requires_review",
"commercial_context_unresolved",
"product_scope_unknown",
"product_chronology_evidence_incomplete",
"national_implementation_unverified",
"selected_damage_boundary_requires_other_route_review",
"damage_category_unknown",
"incorporated_product_exclusion_needs_review",
"modification_assessment_needed",
"control_relationship_evidence_incomplete",
"manufacturer_identity_evidence_missing",
"actor_role_references_incomplete",
"damage_evidence_reference_missing",
"defect_evidence_reference_missing",
"causation_evidence_reference_missing"
]
},
"question": {
"type": "string",
"minLength": 1,
"maxLength": 500
}
},
"required": [
"code",
"question"
]
},
"minItems": 0,
"maxItems": 16
},
"applicableLaw": {
"const": "undetermined"
},
"nationalImplementationVerified": {
"const": false
},
"liability": {
"const": "undetermined"
},
"defect": {
"const": "undetermined"
},
"causation": {
"const": "undetermined"
},
"insuranceCoverage": {
"const": "undetermined"
}
},
"required": [
"correctedNewProductBoundary",
"boundaryConvention",
"chronology",
"futurePlanningDate",
"flags",
"evidenceRequests",
"applicableLaw",
"nationalImplementationVerified",
"liability",
"defect",
"causation",
"insuranceCoverage"
]
},
"sources": {
"const": [
{
"id": 1,
"url": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02024L2853-20241118"
},
{
"id": 2,
"url": "https://www.boe.es/buscar/doc.php?id=DOUE-L-2026-80661"
},
{
"id": 3,
"url": "https://single-market-economy.ec.europa.eu/single-market/goods/free-movement-sectors/liability-defective-products_en"
},
{
"id": 4,
"url": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=LEGISSUM:4792027"
},
{
"id": 5,
"url": "https://ec.europa.eu/safety-gate/screen/pages/productSafetyLegislation"
},
{
"id": 6,
"url": "https://single-market-economy.ec.europa.eu/sectors/mechanical-engineering/machinery_en"
}
]
},
"limitations": {
"const": [
"The 7 May 2026 correction sets the product-date boundary after 8 December 2026, equivalent to 9 December onward.",
"Chronology is only a comparison of the entered date; modification, market placement and applicable national law need separate analysis.",
"This is not an exhaustive implementation of the directive, a Member State law survey, a claim opinion or an insurance assessment.",
"One damage category per record. Prepare separate records when several categories or claimants are involved.",
"Actor roles, references, control and harm are user assertions; the tool authenticates no evidence.",
"No score, automatic compliance approval, liability allocation, network request or incident submission is produced."
]
}
},
"required": [
"schemaId",
"schemaVersion",
"instrument",
"documentationReviewedDate",
"recordCreatedAt",
"inputBasis",
"inputs",
"results",
"sources",
"limitations"
]
}Illustrative example JSON record
This fixed example is published for inspection and integration testing. Its record timestamp is not an evidence-verification timestamp.
{
"schemaId": "dn.connected-product-incident.v1",
"schemaVersion": "1.0.0",
"instrument": "DN Connected Product Incident Map",
"documentationReviewedDate": "2026-11-12",
"recordCreatedAt": "2026-11-12T12:00:00.000Z",
"inputBasis": "illustrative",
"inputs": {
"alias": "Future household-pump planning example",
"jurisdiction": "unknown",
"marketScope": "eu_market",
"claimant": "natural_person",
"commercialActivity": "yes",
"productType": "physical_with_software",
"productDateStatus": "recorded",
"productDate": "2026-12-10",
"productDateMeaning": "Illustrative first EU market-placement date; not an observed event",
"damageType": "private_or_mixed_property",
"incorporatedProductIssue": "no",
"modification": "change_reported",
"manufacturerControl": "unknown",
"actors": [
{
"alias": "maker-alias",
"role": "manufacturer",
"reference": "example-product-reference"
},
{
"alias": "operator-alias",
"role": "operator",
"reference": "example-deployment-reference"
}
],
"nationalLawRef": null,
"damageRef": "Illustrative damage description; no incident",
"defectRef": null,
"causationRef": null,
"updateRef": null,
"acknowledged": true
},
"results": {
"correctedNewProductBoundary": "2026-12-09",
"boundaryConvention": "on_or_after_2026-12-09",
"chronology": "entered_date_on_or_after_new_product_boundary",
"futurePlanningDate": true,
"flags": [
"national_implementation_unverified",
"modification_assessment_needed",
"control_relationship_evidence_incomplete",
"defect_evidence_reference_missing",
"causation_evidence_reference_missing"
],
"evidenceRequests": [
{
"code": "national_implementation_unverified",
"question": "Obtain the relevant Member State implementation and applicable-law assessment."
},
{
"code": "modification_assessment_needed",
"question": "Preserve before/after function, timing and risk assessment; determine whether any change is substantial and affects the legal analysis."
},
{
"code": "control_relationship_evidence_incomplete",
"question": "Document who supplied, authorized or could deliver relevant software/service changes; control is not decided by this form."
},
{
"code": "defect_evidence_reference_missing",
"question": "Preserve a separate defect evidence reference; supplying one would still not establish a legal finding."
},
{
"code": "causation_evidence_reference_missing",
"question": "Preserve a separate causation evidence reference; supplying one would still not establish a legal finding."
}
],
"applicableLaw": "undetermined",
"nationalImplementationVerified": false,
"liability": "undetermined",
"defect": "undetermined",
"causation": "undetermined",
"insuranceCoverage": "undetermined"
},
"sources": [
{
"id": 1,
"url": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02024L2853-20241118"
},
{
"id": 2,
"url": "https://www.boe.es/buscar/doc.php?id=DOUE-L-2026-80661"
},
{
"id": 3,
"url": "https://single-market-economy.ec.europa.eu/single-market/goods/free-movement-sectors/liability-defective-products_en"
},
{
"id": 4,
"url": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=LEGISSUM:4792027"
},
{
"id": 5,
"url": "https://ec.europa.eu/safety-gate/screen/pages/productSafetyLegislation"
},
{
"id": 6,
"url": "https://single-market-economy.ec.europa.eu/sectors/mechanical-engineering/machinery_en"
}
],
"limitations": [
"The 7 May 2026 correction sets the product-date boundary after 8 December 2026, equivalent to 9 December onward.",
"Chronology is only a comparison of the entered date; modification, market placement and applicable national law need separate analysis.",
"This is not an exhaustive implementation of the directive, a Member State law survey, a claim opinion or an insurance assessment.",
"One damage category per record. Prepare separate records when several categories or claimants are involved.",
"Actor roles, references, control and harm are user assertions; the tool authenticates no evidence.",
"No score, automatic compliance approval, liability allocation, network request or incident submission is produced."
]
}
