Digital Product Passports · Wallet · accountable agents

Make our world flourish.

Give the things around us a living record—one that grows through the people who make, use, maintain, repair and transform them. Issue product passports, keep lifecycle knowledge, and discover what becomes possible next.

Start with a Product Passport See how it works

Product Passport creator

Work from a complete example, a governed profile, or data you already have.

Select a product. The same workspace changes in place: fields, source mapping, evidence, identity level and carrier. The default garment is ready for the repair journey below.

Complete example

Immediate result Editable item record · sources mapped · carrier ready

Continue in the creator

This example changes locally in your browser. Continue when you want the full creator, mappings and validation views.

Recipient views

Give each recipient the detail and actions their role requires.

Access and precision are separate decisions. A field can be shared as an exact value, range, threshold, proof, reference or protected fact while its canonical source remains intact.

Selected fieldFibre composition

source retained

62% organic cotton · 31% recycled nylon · 7% elastane

Recipient: Tailor
Access: View item measurements · append repair event
Precision: Exact item measurements and composition
Protected: Dye formula · supplier prices

Meaning and evidence remain attached supplier declaration → canonical material composition → recipient projection Continue with this view

Wallet

See the request, authority and expected result before you decide.

The Wallet places the active person, represented organisation, counterparty, requested information, permitted action, constraints and returning receipt in one decision.

See the Wallet request model Open the Wallet Playground

VVerifable WalletPersonal context · illustrative request

Ready to review

Alter one garment

Allow an independent tailor to repair item 0438.

Requested by the garment owner · counterparty qualification verified for this example

Acting as: Garment owner · personal Wallet
Counterparty: Independent tailor · cross-border service
Share: Item measurements · composition · repair instructions
May do: Read selected fields · append one repair event
Terms: One item · seven days · agreed price
Expected return: Signed repair event · receipt · updated care note

Local decision preview · signing happens in the Wallet

Accountable agents

Let an agent prepare the work within explicit authority.

OAuth/CIMD/ID-JAG is the enterprise-managed authority rail. KYA-OS is the named DID/VC-native route for an independent specialist. Verifable is composing both around the same policy, optional human checkpoint and attributable receipt.

Authority arrives

Established service partner

Principal: Manufacturer service organisation
Proof: Enterprise identity chain · destination policy
Scope: Repair partner role · this product family · active contract
Expires: When the service relationship ends

Common bounded operation

View repair measurements
Propose alteration
Append accepted repair event

The operation carries repair measurements and the approved update field; design and commercial facts keep their governed views.

Policy and result

Authority input modelled
Policy request shaped
Checkpoint determined by policy
Receipt fields assembled

Choose a route, then preview the same operation model.

Inspect the operation envelope

{
  "principal": "did:web:service.example",
  "agent": "urn:agent:service-repair-assistant",
  "resource": "urn:product:item:work-jacket:0438",
  "action": "appendRepairEvent",
  "limits": { "item": "0438", "expiresIn": "7d" },
  "policy": "destination-decision",
  "result": "attributableRepairReceipt"
}

Explore accountable agents Open the Wallet Playground

On 10 August 2026, Lumoin committed Verifable to the OpenID Foundation AIIM OAuth/CIMD/ID-JAG MCP Security Interoperability Event. The full operation and authority contract is implemented, and the hosted OAuth-protected MCP reference is now integration-tested in Verifable.Server. Its named public origin is not activated here, and partner-result evidence remains to be recorded. KYA-OS is the named portable DID/VC authority route beside it. The public Sandbox and Wallet Playground make Wallet ceremonies and their protocol outcomes inspectable; the MCP and ID-JAG proving loop belongs to the separate agentic interop case.

The same operation in different work

Use identity, recipient views, authority and receipts across fields.

Select a field below. The task changes while the accountable structure stays legible.

IdentityGarment item
Recipient viewMeasurements · instructions
AuthorityQualified tailor
WorkAlter · repair
ReceiptRepair event

A tailor receives the exact item information and one bounded update right.

Open this setup

Read the complete application matrix

Field	Identity	Recipient view	Authority and work	Receipt
Garment	Item	Measurements and instructions	Tailor repairs	Repair event
Equipment	Existing asset ID	Model, warranty and fault	Technician services	Maintenance event
Battery and electronics	Batch or item	Condition and handling	Collector or repairer assesses	Intake or second-life event
Packaging	Batch or pool	Material and reuse rules	Logistics actor returns or washes	Batch event
Metals	Material lot	Exact value, range, threshold or proof	Buyer or recycler processes	Material event
Construction and 3D	IFC entity, design or printed instance	Media and installation data	Qualified installer fits, repairs or reuses	Component event

Agent operation model

Inspect the exchange, handoff by handoff.

Begin with the tailor operation. Read the human result first, then reveal the trace, JSON-LD or governed MCP operation shape. This synthetic view explains the contract; it is not deployment evidence.

See the accountable operation Open the Lab contract

tailor-repair / operation model synthetic view · adapter not invoked

Result

One repair request is ready for a Wallet decision.

The proposed view carries the required measurements and append right. Governed views continue to hold design and commercial facts.

Authority: Independent tailor · portable delegation
Checkpoint: Owner approval
Expected return: Repair event and signed receipt

{
  "@id": "urn:product:item:work-jacket:0438",
  "type": "ProductPassport",
  "requestedAction": "appendRepairEvent",
  "recipient": "qualifiedTailor"
}

{"operation":"appendRepairEvent","transport":"MCP Streamable HTTP — target governed operation binding","authority":"enterprise-managed | portable-delegation","result":"attributableReceipt"}

One complete journey

A garment repair across organisations.

Follow one existing passport through a repair request, two ways authority can arrive, a precise decision and a returning receipt.

01 / 05 Existing passport record

Existing passport

The garment already carries identity, material facts and care information.

Existing product data and retained evidence already give this item a useful record.

Wallet request

Its owner asks for a repair and sees the expected result.

The request names the item, required fields, price, time window and the receipt that should return.

Two ways authority arrives

An established partner and an independent tailor converge on the same bounded task.

OAuth/CIMD/ID-JAG serves enterprise trust. KYA-OS is the named DID/VC-native target beyond a shared directory.

Exact decision

The Wallet reveals the necessary measurements and repair right.

The approved view carries the measurements and repair right; design and commercial facts continue in their governed views.

Returning evidence

An accepted repair would return as an event and receipt.

The product record, warranty, contract and permitted reporting views can continue from the attributable result.

Explore the accountable operation

Many hands make light work

Choose the result you want to complete.

The record carries meaning forward. The Wallet carries authority. People and agents complete the next task and return its evidence.

Create or import a product record Explore the Wallet Connect software or an agent Plan an organisational deployment