Digital Product Passport Lineage

Note (dated 2026-08-04): a chain composes independent computations performed in an analytical order. No step's output is carried into the next step by the execution model; each step computes from its own declared inputs. This is true of every chain on this site, including chains whose per-step copy below reads as a data handoff.

Validate DPP data carrier against CIRPASS-2 Core Ontology (art-115) → build cradle-to-gate hash-only supplier lineage with carbon aggregation (art-116) → verify consumer/resale authenticity + ownership continuity (art-117). EU Central DPP Registry live 19 Jul 2026.

OpenChainGraph · 3 Steps compliance mandate EU ESPR · DPP Registry 19 Jul 2026 CIRPASS-2 Core Ontology Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII

Chain Stages · 3 Steps

1ROOT · D0node

EU ESPR Digital Product Passport Data Carrier Validator art-115

CIRPASS-2 conformance result feeds lineage building

MCP Call · validate_dpp_data_carrier

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "validate_dpp_data_carrier",
    "arguments": {
      "carrier_type": "qr_gs1_digital_link",
      "product_id": "https://id.gs1.org/01/09506000134352",
      "dpp_data": {
        "durability_score": 8,
        "reparability_score": 7,
        "recyclability_pct": 72,
        "carbon_footprint_kg_co2e": 12.4,
        "substances_of_concern": [],
        "manufacturer_id": "GL-MFG-001",
        "product_category": "electronics"
      }
    }
  },
  "id": 1
}

↓

2D1node

Digital Product Passport Cradle-to-Gate Lineage Builder art-116

Anchored supplier lineage feeds authenticity verification

MCP Call · build_product_lineage

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "build_product_lineage",
    "arguments": {
      "product_id": "GL-PROD-2026-001",
      "stages": [
        {"stage":"raw_materials","supplier_hash":"sha256:aaaa0001...","certification":"ISO-14001:2015","dataVersion":"2026-Q1","carbon_value":4.2},
        {"stage":"manufacturing","supplier_hash":"sha256:bbbb0002...","certification":"ISO-9001:2015","dataVersion":"2026-Q1","carbon_value":7.8}
      ]
    }
  },
  "id": 2
}

↓

3TERMINAL · D2node

Luxury Goods Product Authenticity Verifier art-117

Exports authenticity artifact with execution_hash — final stage

MCP Call · verify_product_authenticity

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "verify_product_authenticity",
    "arguments": {
      "claimed_root_hash": "sha256:aaaa0001...",
      "presented_lineage_hashes": ["sha256:aaaa0001...", "sha256:bbbb0002..."],
      "ownership_transfers": [
        {"from":"MFG","to":"DIST","date":"2026-01-10"},
        {"from":"DIST","to":"RETAIL","date":"2026-03-05"}
      ]
    }
  },
  "id": 3
}

Question: A buyer wants assurance this resale unit was not diverted mid-chain. Does every ownership transfer on the passport hand off to the party the previous one named? Run the AINumbers MCP tool `run_chain` with {"chain":"digital-product-passport-lineage"} and read `art-117-product-authenticity-verifier.ownership_continuous`. Re-run with `inputs` for `art-117-product-authenticity-verifier`, reusing the values that result echoed, with `ownership_transfers` changed so the second transfer starts from an address no earlier transfer reached. Compare the same field. Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`. Ledger, for a human re-check: https://ledger.ainumbers.co/ PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads. Chain page: https://ainumbers.co/chaingraph/chains/digital-product-passport-lineage.html

Digital Product Passport Lineage

Ask your agent