Regulatory Alignment

localLOOP is still lab-demo infrastructure, but the protocol now documents how it can evolve toward DPP, battery, packaging, waste-traceability, and German circular-economy data expectations building on the v0.2.0 DPP-compatible baseline. The new ProductDNA schema provides product-level DPP alignment (ESPR Art. 9-10).

Review the spec

What changed

Data minimization
Minimal interop payloads now explicitly reject personal contact fields.
Forward compatibility
Receivers can accept additive `0.1.x` payloads and preserve unknown fields.
DPP-ready hooks
`passport`, `classification`, and `traceability` blocks create a non-breaking upgrade path.
ProductDNA
Product-level DPP entity with ESPR-aligned passport fields, referencing MaterialDNA composition.

What this is not

This roadmap does not claim legal compliance, certification, or product-group coverage for delegated acts that are still emerging.

Regulatory Alignment Roadmap

localLOOP remains a lab-demo project with no public pilots or production deployments. This roadmap is a compatibility plan, not a certification claim and not legal advice.

Why this roadmap exists

LOOP now needs to stay additive and interoperable as EU product, packaging, battery, and waste-traceability rules become more digital. The immediate goal is to make v0.1.1 payloads easier to extend without breaking existing lab integrations.

Current baseline

  • v0.2.0 is the current baseline with comprehensive DPP extension fields (ESPR, UNTP, PPWR, Battery Passport, NKWS-aligned). v0.1.1 payloads remain valid.
  • Receivers should accept additive 0.1.x patch releases when they can preserve or safely ignore unknown fields.
  • Minimal interop payloads must stay free of personal contact data.
  • Passport, classification, and traceability blocks are optional extension points, not required fields.

Regulatory signals to track

EU ESPR and Digital Product Passport

  • Regulation (EU) 2024/1781 entered into force on July 18, 2024.
  • The regulation establishes the Digital Product Passport framework and requires delegated acts to define product-specific rules.
  • The first ESPR Working Plan for 2025-2030 prioritizes product groups including textiles, furniture, tyres, mattresses, iron and steel, and aluminium.
  • Implication for localLOOP: use additive passport identifiers, access-scope metadata, classification hints, and stable traceability references without hard-coding product-specific delegated-act fields too early.

EU Batteries Regulation

  • Regulation (EU) 2023/1542 entered into force on August 17, 2023.
  • Digital battery passport obligations start applying from February 18, 2027 for light means of transport, industrial batteries above 2 kWh, and electric-vehicle batteries.
  • Implication for localLOOP: support passport IDs, battery category hints, due-diligence references, retention metadata, and role-based access boundaries.

EU Packaging and Packaging Waste Regulation

  • Regulation (EU) 2025/40 entered into force on February 11, 2025 and applies from August 12, 2026, with later phased obligations.
  • Reusable transport packaging and grouped packaging will increasingly rely on harmonized identification and data-carrier requirements.
  • Implication for localLOOP: preserve packaging identifiers, reusable-loop references, and document links without assuming a single passport format yet.

EU Waste Shipment and Traceability

  • Regulation (EU) 2024/1157 entered into force on May 20, 2024.
  • The move toward electronic documentation and stricter cross-border controls makes evidence references and retention windows more important.
  • The Digital Waste Shipment System (DIWASS) applies from May 21, 2026, mandating electronic processing of waste shipment notifications and documents.
  • Implication for localLOOP: keep document references, facility IDs, operator IDs, and retention dates attachable to material records and transfer events. Support waste shipment document references in transfer payloads.

Germany National Circular Economy Strategy

  • Germany adopted the National Circular Economy Strategy in December 2024.
  • The strategy emphasizes digital product information, reuse, repair, municipal circularity, and better data availability across value chains.
  • Implication for localLOOP: keep municipal-node interoperability, reusable material identity, and digital passport alignment as first-class design goals.

GDPR and green claims governance

  • GDPR Article 5 requires personal data to be adequate, relevant, and limited to what is necessary.
  • Directive (EU) 2024/825 on empowering consumers for the green transition tightens how sustainability claims can be presented.
  • The separate Green Claims Directive proposal (COM(2023)166) was withdrawn by the European Commission in June 2025 after the EPP and Italy withdrew support. Directive (EU) 2024/825 on empowering consumers for the green transition remains the operative instrument, with Member State transposition due by March 27, 2026, and rules binding from September 27, 2026.
  • Implication for localLOOP: do not present protocol metadata as proof of compliance or environmental performance unless the required evidence and verification model exists.

City action timeline

The table below maps key regulation milestones to concrete planning checkpoints for city infrastructure owners. Dates are operative dates, not political agreement dates. This is informational only — not legal advice.

RegulationWhat appliesOperative dateCity planning action
DIWASS (WSR 2024/1157 Art. 26)Electronic processing of cross-border waste shipment documentsMay 2026 (now active)Confirm waste operators can submit and retrieve electronic shipment documents; verify document-reference fields are available in material-transfer records
PPWR (EU) 2025/40Reusable transport and grouped packaging identificationAugust 2026Identify packaging categories in city procurement scope; ensure packaging identifiers can attach to material-transfer records
Green claims (Dir. EU 2024/825)Sustainability claims presented to consumersSeptember 2026Review city-published material-flow or circularity statistics against tightened substantiation rules
ESPR DPP — textiles, furnitureDigital Product Passports for textiles and furniture (first delegated acts)2026–2027Assess procurement volumes for these categories; ProductDNA schema is DPP-aligned and ready for extension
Battery Passport (EU) 2023/1542Digital passports for EV, light means of transport, and industrial batteries > 2 kWhFebruary 2027Audit city fleet and depots for in-scope battery categories; ensure asset management systems can store battery passport IDs

Delivery plan

Horizon 1: now to 90 days

  • Accept application/ld+json end-to-end in the backend.
  • Remove PII-bearing fields from minimal interop payloads.
  • Publish canonical versioned schema paths in the site mirror.
  • Expand the JSON-LD context so additive fields expand predictably.
  • Add sync and validation checks so protocol, backend copies, and site mirrors cannot silently drift.

Horizon 2: 3 to 12 months

  • Introduce profile-based extension guidance for battery, packaging, and waste-shipment use cases (v0.2.0 provides UNTP DPP-aligned optional fields as a starting point).
  • Model access scopes for public, operator, and regulator-visible passport data.
  • Add retention-policy and evidence-reference guidance for transfer and status events.
  • Map current LOOP categories to product and waste classifications without freezing product-specific delegated-act structures too early.

Horizon 3: 12 to 24 months

  • Add conformance tests for additive patch releases and profile-specific extensions.
  • Prototype adapter layers for battery passport and DPP service-provider integrations once implementing acts mature.
  • Add reusable packaging and municipal reuse scenarios to lab flows.

Horizon 4: 24 months and beyond

  • Track product-specific delegated acts and standards as they are adopted.
  • Promote stable extension profiles into normative schema modules only when rules are sufficiently concrete.
  • Add machine-readable evidence and verification models before making any compliance-facing product claims.

Design guardrails

  • Preserve backward compatibility by keeping the v0.1.1 baseline payloads valid.
  • Preserve forward compatibility by allowing additive patch-line versions and unknown extension fields.
  • Keep regulated or sensitive attributes optional until a delegated act or standard makes them precise enough to model safely.
  • Avoid embedding personal data in shared protocol payloads.
  • Separate interoperability readiness from legal compliance claims in every public-facing document.

Official sources