Local loops. Global economies.
A repaired component moving across town and a battery shipment crossing a border differ in scale, but both need identity, evidence and authority the receiving side can verify. Product Passports link a product to its history. Wallets identify who may act. Open protocols let independently operated systems exchange those records.
Share local knowledge with its context.
A successful repair, inspection or reuse can become a starting point elsewhere—with its source, assumptions and result intact. People in another place can adapt what fits to their own materials, rules and priorities, while preserving what differs.
- 01Local practiceA result in its real context
- 02Attributable modelSources and assumptions remain visible
- 03Open exchangeRecords and authority travel together
- 04Local adaptationAnother community decides what fits
Place is part of what a record means.
A receiving project can ask what is near, within or connected to its site without separating the answer from its source and local context. That helps people discover candidates and transfer useful knowledge from one place to another. The receiving place still decides what fits its materials, needs, rules and priorities.
Circularity is made of many small hand-offs.
A circular value chain includes observations, repairs, offers, permissions, transfers and new uses. Recording the source and result of each interaction helps receiving organisations inspect the product's history.
- ObserveWhat exists now?condition · place · source
- ImagineWhat could happen next?need · match · alternatives
- AuthoriseWho may decide or act?person · organisation · agent
- ContinueWhat became the next fact?event · evidence · receipt
Product Passports and asset records keep the thing visible. The Wallet keeps identity, context and authority visible. Agents can perform the repetitive coordination inside those boundaries. Open protocols support exchanges between these systems.
The instruments, by name
Each movement has a body of rules that decides what a receiving party is obliged to accept. Naming them is only useful if our own position against each one is stated in the same breath, so it is — with implementation status and limitations recorded on the facts page.
| Instrument | What it covers here |
|---|---|
| UN Transparency Protocol (UNTP) — verification | UNTP defines the credential families supply-chain parties exchange about a product: the Digital Product Passport, the Digital Conformity Credential a testing or certification body issues, and the Digital Traceability Event. POST /untp/verify selects the trust anchor from the credential's own issuer.id — a tenant key, an enrolled foreign issuer key, or a live did:web resolution — rather than from a list of accepted strings. |
| UN Transparency Protocol (UNTP) — issuance to a wallet | The same three credential types are issued as wallet-redeemable credentials in the pre-seeded test tenant, reachable from the sandbox with no account. That tenant's signing keys are regenerated on every server restart, so credentials issued there are for integration work and carry no legal or regulatory weight. |
| MLETR — the UNCITRAL Model Law on Electronic Transferable Records | MLETR is a model for national legislation, not a product approval. Recognition depends on applicable law and reliable methods for identification, control and integrity. Verifable does not offer a transferable-record registry or claim an exclusive-control mechanism here. |
| ESPR product groups, which bound every row above | A record moves in the shape its product group gives it. Verifable's common passport rails and custom templates cover batteries, textiles, electronics, construction products, detergents and other groups. The battery group under Regulation (EU) 2023/1542 has the wired public guided shape today; textiles and electronics have versioned readiness profiles, while construction and custom groups begin from the common record. A trade document or marketplace listing can link to those records without becoming evidence of product-specific legal conformance. |
Why the shared layer matters
- For the people receiving the record
- A repairer, buyer, marketplace, customs team or receiving project should be able to inspect a record it did not create, understand its source and decide what it can rely on.
- For the organisations supplying it
- One accountable record can serve many counterparties without turning every hand-off into a bespoke portal, spreadsheet or bilateral integration.
- For local knowledge
- A successful local repair, reuse or operating practice can travel as attributed evidence. Another place can adapt it instead of receiving a context-free prescription.
- For people and agents acting on it
- A Wallet can show the active identity and authority. An agent can prepare or carry out bounded work. The resulting event returns to the record with its source and consequence visible.
Choose a starting point
Run the Sandbox, create a guided battery record, browse the exact capability evidence, or read pricing. Corrections and interoperability partners are welcome: hello@lumoin.com.