# The Product Passport Becomes the House Record

Read on the gallery: https://institutions-of-one-fashion.vercel.app/packages/co10

All dossiers: https://institutions-of-one-fashion.vercel.app/dossiers

Source page: https://rn-selected-work.vercel.app/sources/ioo-fashion/co10

Version: 1.0 · Complete editable editorial edition

## Canonical thesis
A product passport can become part of a house archive when verified compliance data is joined to provenance, care, repair, change, authorship, and stewardship without confusing mandatory fields with complete history.

## Complete editorial sequence
The EU Ecodesign for Sustainable Products Regulation establishes a framework that includes digital product passports, with details dependent on delegated acts and implementation. That current legal source should not be reduced to a trend prediction or represented as a complete rule for every garment today. It does, however, make product-level information infrastructure central to a changing European regulatory landscape.

A house can treat the resulting data as more than a compliance endpoint. Stable identifiers, material and supply-chain evidence, care, repair, alteration, ownership or custody events where appropriate, rights, contributor records, and archival relationships can make an object more intelligible over time. The danger is equally institutional: false precision, unverifiable supplier claims, inaccessible interfaces, surveillance, proprietary lock-in, and data that disappears when a vendor closes.

### 01 · REQUIRE — What is legally required now?
Identify product scope, applicable delegated acts, actor, territory, date, required fields, carrier, access rules, and official legal source. Mark future implementation unresolved until adopted.

Evidence: VERIFIED · S38

### 02 · VERIFY — Who supports each field?
Bind claim, data source, responsible party, verification method, date, confidence, correction, and evidence file. Do not transform a supplier assertion into an audited fact.

Evidence: PROPOSAL · S34, S38

### 03 · EXTEND — What history may responsibly be added?
Connect design development, maker and repair records, care, alterations, provenance, archive deposit, rights, and permitted owner narration while minimizing personal data.

Evidence: INFERENCE · S08, S39, S42

### 04 · PRESERVE — Will the record survive the vendor?
Require export, open formats, persistent identifiers, versioning, backups, access governance, migration tests, and a non-digital fallback for essential care information.

Evidence: PROPOSAL · S39, S66

## Counterargument
More product data does not automatically create accountability. A passport can amplify unverified claims, expose workers or consumers, shift burdens onto suppliers, and become inaccessible after sale. Evidence quality and governance matter more than interface polish.

## Reader fieldwork
1. Determine the product, territory, date, and authoritative requirements with counsel.
2. Trace every proposed field to its source and verifier.
3. Separate public, restricted, personal, confidential, and archival layers.
4. Export and restore one record without the current software vendor.

## External production dependencies
Recorded performance, bespoke RN photography, participant releases, and counsel or specialist review are separate human-led productions. The editorial edition does not present them as finished recordings, permissions, or professional opinions.