The CIRPASS-2 Validation Stack for Textile DPP
What makes a textile DPP verifiable rather than merely documented? The CIRPASS-2-compatible Reeco stack applies seven validation layers — schema, model, semantics, textile logic, mass-balance controls, conformity credentials and traceability events — so a claim is checked against production data before the passport is issued, not after.
Executive Summary
Textile DPP compliance fails when data is only collected and not verified.
The CIRPASS-2-compatible Reeco stack applies seven validation layers: SCH, MDL, SEM, TXT, RCO, DCC, DTE.
Why a Multi-Layer Stack Is Required
Most platforms stop at "document present". That does not prove product-level claim integrity.
A robust DPP workflow must validate structure, semantics, textile logic, and mass-balance coherence.
Layer Overview
| Layer | Scope | Typical Output |
|---|---|---|
| SCH | Schema conformance | Structural errors (for example SCH001) |
| MDL | Model integrity | Missing fields or malformed objects (MDL*) |
| SEM | Semantic consistency | Contradictory meanings (SEM*) |
| TXT | Textile logic | Textile-specific claim inconsistencies (TXT*) |
| RCO | Reeco control layer | Hard business controls (RCO003 mass balance) |
| DCC | Credentialization | TC exported as UNTP DCC 0.6.1 |
| DTE | Traceability events | Batch flow exported as TransformationEvent |
Validation Performance Posture
For deterministic checks on structured payloads, core validation can execute in milliseconds (reference benchmark: around 1.6 ms per request in lightweight runs).
This is operationally relevant: controls can run synchronously at submission time, before label emission.
What Competitors Usually Miss
| Capability | Typical DPP UI | Reeco Stack |
|---|---|---|
| File upload | Yes | Yes |
| Schema checks | Partial | Full SCH + MDL |
| Textile semantic rules | Rare | SEM + TXT |
| Hard mass-balance block | Rare | RCO hard block |
| UNTP DCC export | Rare | Native |
| UNTP DTE export | Rare | Native |
Implementation Notes
Endpoints
POST /api/v1/dpp/validatePOST /api/v1/dpp/export/dccPOST /api/v1/dpp/export/dcc/jwtPOST /api/v1/dpp/export/dte
Spec Versioning
- UNTP reference:
0.6.1 - Evidence model: W3C Verifiable Credentials
FAQ
Is schema validation enough for compliance?
No. Schema checks confirm shape, not truthfulness of sustainability claims.
What makes RCO different?
RCO adds hard operational controls such as mass-balance blocking when certified material is exhausted.
Why include DCC and DTE in the same stack?
Because validation without exportable evidence is not interoperable compliance.