Passport Lite

Use cases

When you need to show where every value came from.

Document preparation without promising registration, certification or automatic compliance.

Prepare a product publication

Collect scattered information and generate a reviewable static page before hosting it under a controlled domain.

Request supplier data

Expose materials, origin, tests, repair and end-of-life data that still lack a documentary reference or date.

Hand a dossier between teams

Package documents, a manifest and hashes so another person can verify which files formed the delivery.

Create a starting point for a DPP

Organise a general profile before adapting it to verified rules for the relevant product group.

It does not replace

It does not replace registration, certification, a PLM system or legal and sector review.

Prepare a dossier

Tool · Use cases
EspañolEnglishFrançaisDeutschItalianoPortuguêsCatalàEuskaraGalegoPolski中文日本語اردوالعربيةहिन्दीРусскийΕλληνικάTürkçeNederlands한국어Boarisch

Sierra 750: from data to package

Fictional bottle example: names, documents and tests are demonstrations, with data dated 15 July 2026. Load Sierra 750 or import the downloadable draft to reproduce it. The sample data are in Spanish.

Checks

Compare three versions of the same draft: A, original; B, the steel percentage reference left blank; C, steel changed to 80%, totalling 98%. B and C need review but do not block the ZIP. An individual value of 101% does block it. Obtain real documents and resolve warnings before publication.

A / B / CCompleteReviewMissingZIP
A3100✓
B3010✓
C3110✓

QR · HTTPS

The example ZIP contains 10 files and no attachments. Extract index.html to view it, but its QR still points to the fictional example.com URL. For a real product, host the files at your HTTPS address, confirm that address and test the QR from another device. Downloading or checking the QR inside the app does not publish the page.

https://example.com/products/sierra-750/passport

ZIP · 10
  • index.html
  • ficha.html
  • data/passport.json
  • data/product.jsonld
  • schema/passport-lite.schema.json
  • assets/qr.svg
  • assets/qr.png
  • README.txt
  • manifest.json
  • checksums.txt

SHA-256

SHA-256 hashes detect byte changes. Editing a file after export makes its hash differ. They are not a digital signature, product certificate or proof that the QR destination exists.

manifest.json · checksums.txt

01e20257c59e94cd610a9050abe39c3891d25e9c5f17f4b7c9466eeee231616f