# Textile DPP Compliance Checklist

## Executive Summary

This checklist is designed for textile brands, manufacturers, and certification-driven supply chains preparing for ESPR-era Digital Product Passport obligations.

## 1) Data Foundation

### Required Controls

| Check | Status Criteria |
|---|---|
| Product IDs are stable and unique | No duplicate IDs across batches |
| BOM data is structured | No free-text-only material declarations |
| Certification references are normalized | TC identifiers are machine-parsable |

## 2) Validation Controls

| Check | Status Criteria |
|---|---|
| Schema checks (`SCH`) active | Invalid payloads blocked |
| Model checks (`MDL`) active | Missing mandatory objects blocked |
| Semantic checks (`SEM`) active | Contradictions flagged |
| Textile checks (`TXT`) active | Textile claim logic enforced |
| Reeco controls (`RCO`) active | Mass-balance hard block (`RCO003`) enabled |

## 3) Claim Integrity

| Check | Status Criteria |
|---|---|
| GRS-to-product conversion logic defined | `GSM x CW x YY` documented |
| Consumption trace per batch | Auditable at SKU or lot level |
| Exhaustion control | Label issuance blocked when balance is zero |

## 4) Interoperable Evidence

| Check | Status Criteria |
|---|---|
| DCC export available | `POST /api/v1/dpp/export/dcc` |
| DTE export available | `POST /api/v1/dpp/export/dte` |
| Credential signing available | `did:web` + Ed25519 |
| Public verifier key endpoint | `/.well-known/did.json` live |

## 5) Governance and Audit Readiness

| Check | Status Criteria |
|---|---|
| Rule versions tracked | Change history available |
| Evidence retrieval per product | Audit package generated on demand |
| Exception workflow defined | Warnings vs hard blocks clearly separated |

## FAQ

### Is this checklist only for large enterprises?

No. SMEs can adopt the same logic with narrower scope and phased rollout.

### What is the most critical technical control?

Hard mass-balance enforcement tied to certified input availability.

### What should be implemented first?

Structured data + validation layers, then credential exports.