Immediate need
Product requirements
See what applies to this product, what is already present and which source or supplier evidence is still needed.
Review the selected field setDigital Product Passports
Prepare product data for market—and beyond.
Choose the product or packaging record. See what applies, what is missing and who is responsible. Review the approved result for passports, sales channels, lifecycle work and reporting without entering the same facts again.
Browser-local workspace · download anytime
Start with the product
What are you preparing?
Browser-local draft
Battery passportLoading the source-bound field catalogue
Regulation (EU) 2023/1542 + Commission-published, non-binding guidance
Guidance Document: Digital Batteries Passport — data points by category
The 71 Commission guidance points are shown separately from their legal basis. Six recorded divergences remain visible; no industry profile is treated as EU authority.
- Source catalogue
- 71 points
- Editor coverage
- 71 of 71 represented
- Selected scope
- 50 guidance-mandatory
Level of detail
71 Commission data points
Field values and evidence remain in this browser.
ModelShared design or product typeA battery model, textile style, construction product type or 3D model.
BatchProduction run, lot or managed poolFacts shared by the units made, assembled or handled together.
ItemOne physical unitAn individual battery, used building component, garment or printed part.
Installation, service and repair remain linked events. They do not silently change the identity or legal granularity of the record.
Current recordBattery passportVerified field catalogue
Working goalPrepare and maintain this recordChange the goal without changing the source facts
Current recipientPublicAccess and disclosure stay separate
Next decisionAdd the first expected itemNo combined compliance score
One record · several accountable results
See what this record can support.
Begin with the result you need. Each view uses the same product facts, evidence and access decisions; opening a view changes this workspace in place.
Controlled use
People and access
Compare what a customer, owner, service provider, recycler or authority receives, including reduced-precision answers.
Public view selectedMarket work
Prepare for market
Bring role, destination, sales route, conformity evidence, carrier and submission work into one reviewable market case.
Separate product, packaging and destination dutiesValue-chain exchange
EU DPP ↔ UNTP 0.7
Compare the EU product record with a wider value-chain representation and inspect every mapping, transformation or omission.
Same facts · separately governed projectionsContinuing record
Lifecycle and logbooks
Keep installation, inspection, maintenance, repair, reuse and replacement events connected to the product and building context.
Product record + attributable eventsTrade and reporting
Reuse approved facts
Trace product facts into shipment records, CBAM evidence, warehouse and custody records, and reporting outputs without conflating them.
Each output keeps its own rules and receiptIntegration
Systems and agents
Use the same reviewed operation through the human workspace, HTTP API or MCP, with an attributable result on every route.
One operation contract · three interfacesSource-bound fields
Battery passport
Edit the Commission’s 71-point battery catalogue while inspecting the cited Batteries Regulation basis and category-specific applicability.
Component structure and provenance
Keep every component’s facts together.
Each component instance has its own stable identity. Its fields retain the source assertion, input binding, semantic mapping and disclosure policy used to form the record.
This release exposes the migration-derived catalogue and its source and provenance references. The tested record contract keeps repeated instances, evidence, actor and time separate without mixing one component’s facts with another. It is not connected to value entry on this page, and spare-parts and adjacent resource references remain unshaped.
Loading fields
Applicability and authority
Source catalogue
The 71-point catalogue published by the Commission is shown with its cited legal basis and category-specific guidance claim. “BR” means Regulation (EU) 2023/1542. The guidance is non-binding; the Regulation remains the legal source.
Six recorded differences between the guidance and the Regulation
- Marking references: the Annex and guidance point to different Article 13 paragraphs.
- Instructions for use: the guidance cites Annex XIII 1(t), which does not exist in the current Regulation text; the field is deferred.
- Rated capacity: the Regulation lists it as public information while the guidance suppresses the duplicate row.
- Recycled content: the guidance marks the shares mandatory earlier than the Regulation's source-document timetable.
- Material composition: the guidance row leaves its legal-source cell blank.
- Category label: the guidance repeatedly prints “LMV” where the defined category is LMT.
These are evidence-review findings, not silent corrections. The editor keeps the cited text and the recorded discrepancy inspectable.
Source to editor field
Traceability map
Each row connects a source point and cited basis to the editor field that represents it, its value structure, update mode and access scope.
From approved information to a market result
Prepare the case before the product is offered or placed.
Select the responsible role, destination, date and route. Verifable then keeps product requirements, conformity evidence, passport work, packaging, sales-channel checks and the resulting acknowledgements distinguishable.
An organisation market case can retain these choices, approvals and external responses. This browser draft does not submit anything.
Applicable requirements, dates and source evidence remain inspectable in Record & sources.
Do not treat schema validation, a draft or a data carrier as evidence that the product conforms.
Identity, granularity, backup copy, Registry work and the physical carrier stay separately reviewable.
One carrier may serve several records, while packaging evidence, EPR and marketplace duties retain their own basis.
Goods codes, quantities, origin and emissions evidence can feed a separate customs or CBAM case with reverse lineage.
The resulting record distinguishes internal approval, external submission and destination acknowledgement.
Source-linked cross-product market check
See what a retained assessment will ask.
Some market duties apply because of an incorporated component or a particular use—not because the information belongs in this passport. Verifable keeps the future assessment connected to the product without turning its questions into invented passport fields.
The rule pack keeps its questions, evidence and legal status outside the passport draft. Unknown information stays Needs review; it never becomes a guessed answer or a conformity claim.
External issue, registration, marketplace and reporting actions require a retained organisation case, accountable authority and a named destination. The controls remain unavailable in this browser-only draft.
Access and disclosure
Access views
Access determines who may receive a field. Disclosure precision determines whether they receive its exact value, a range, threshold or presence-only answer. Evidence quality states how the value was obtained. These remain draft projections until an issued record and authorization policy enforce them.
0 fieldsin this view
Resulting view
Public
Live JSON-LD
Same draft, structured.
Every value remains attached to its editor-field identity, source basis, selected-scope applicability and recipient policy.
The structured view and editable draft are generated from the same browser-local record.
Veritas · browser-local
Check this draft before export.
Read the current source-bound record, check its released data shape and list expected information that is still missing. The engine works only on the documents passed to it and fetches nothing.
- Profile
- Waiting for verified profile
- Revision
- Waiting for verified revision
- Draft schema
- Waiting for verified schema
The browser-local semantic runtime loads only when a check is requested.
Uses the current editor scope and applicability. It is not a legal-conformity verdict.
What this establishes: local syntax, released-schema and source-coverage results for this draft. It does not issue, sign, register or publish a passport; verify issuer or status; establish legal conformity; or prove acceptance by an authority or counterparty.
Inspect the proposed machine-operation shape
This portable request uses the same full operation contract as the human, HTTP and MCP bindings. This browser deployment previews it without invoking a retained service binding or changing the local draft.
One reviewed operation · several interfaces
Connect the systems that already hold and use the data.
The human workspace, HTTP API and MCP use the same input, validation, permission, result and operation record. Integrations do not get a second, weaker route around review.
Prepare the record, inspect every source, choose a recipient and download the current structured draft.
Connect PIM, PLM, ERP, ecommerce, Registry, printing, overlabelling or other production routes through versioned operations.
Let an authorised agent explain a source, patch a draft, validate a result or prepare a carrier through the same operation contract.
The machine-readable profile and proposed operation are inspectable now. This browser-local draft has no retained service selected, so execution controls stay disabled here. Production integrations wire the same implemented business operations, authority, policy decision, trace and operation record to HTTP or MCP.
EU product record + wider value chain
Compare the EU DPP with UNTP 0.7.
The EU record answers the applicable product rules. UNTP carries approved product, conformity, facility and event information across organisations and into trade. They share facts without becoming the same instrument.
- Profile
- UNTP 0.7 · DPP exchange profile
- Schema
- Digest-pinned exchange assets
- Source record
- Selected Product Passport
Applicable product rules
EU DPP
- Product-specific legal scope and dates
- Required identity, evidence and access groups
- Data carrier, backup copy and Registry work where applicable
- Updates allowed by the applicable product act
Cross-organisation exchange
UNTP 0.7
- DPP for the shared product representation
- DCC for linked conformity evidence
- DTE for make, move and modify events
- DIA and DFR for identity and facility records
Inspectable transformation
Source field → UNTP path
Selected record granularityModel · batch · item
credentialSubject.granularityLevelExactThe editor and the pinned UNTP profile use the same three granularity values.
Product identityBattery point 7
product.registeredId | batchNumber | serialNumberTransformThe selected granularity determines which identity path receives the value.
ManufacturerBattery point 3
product.producedByPartyNeeds structureA name alone does not create the URI-based party object required by the exchange profile.
Manufacturing placeBattery point 8
product.producedAtFacilityPolicy-boundOnly a resolvable facility identity permitted for the recipient may be projected.
Keep the record alive
Connect product facts to lifecycle and logbooks.
A product passport is not the whole history. Events connect the product to where it was installed, what work was performed and which evidence changed.
Each event names the subject, actor, effective time, evidence, access and the record it corrects or supersedes.
Keep the construction product record linked to installation, renovation and building context without turning the logbook into the product passport.
Use the product record and attributable events to support maintenance, warranty, second life and end-of-life decisions.
The event preview, commit and receipt contracts are implemented once. This browser page invokes the human workspace binding; retained HTTP and MCP bindings use the same operation contract and are activated per deployment.
Reuse approved facts · keep every outcome distinct
Follow the same evidence into trade and reporting.
Local and global value chains meet here. The product record supplies governed facts; each trade document, custody record, calculation or report applies its own rules and returns its own result.
Shipment and conformity records
Reuse approved product, party, facility and evidence references in separately issued trade documents and UNTP traceability events.
- Input
- Product identity, parties, goods, evidence
- Result
- Document, signature, status and relationships
Supplier evidence to reported result
Carry goods codes, quantity, origin, installation, production route, emissions method and verification evidence into a separate CBAM case.
- Input
- Approved operational and supplier facts
- Result
- Calculation lineage and Registry output
Goods identity is not the financial instrument
Link the described goods to warehouse, quantity, custody and control evidence while keeping the receipt, pledge and surrender state separate.
- Input
- Batch, quantity, grade, location, evidence
- Result
- Custody and control record with conflict checks
CBAM and XBRL are separate projections
Trace each reported fact back through calculation, aggregation, mapping and source evidence, including the exact ruleset or taxonomy version.
- Input
- Governed facts and calculation lineage
- Result
- CBAM output or XBRL/OIM reporting package
Ask bounded questions of the evidence graph
Start with a table and relationship graph: origin, facility, route, evidence freshness, CBAM exposure, custody quantity and conflicting claims—with provenance, time, access and uncertainty preserved.
- Views
- Table · relationship graph
- Later
- Vector map when the shared renderer is wired
These operations require their reviewed domain packs, accountable authority and retained result contracts. This page does not simulate a successful document, filing, query or financial claim.
Data carrier
Prepare a local handoff.
Choose a carrier preview, then explicitly prepare a handoff containing only entered fields in the Public view.
No value is placed in a carrier until you prepare it. The local handoff is not issued, signed, durably hosted or resolver-bound.
Review this disclosed view in WalletPrepare a public-view handoff to create a QR.
Local draft and retained service
Download the draft or discuss the accountable next step.
The JSON-LD contains every entered value with its field identity, source, applicability and recipient policy. Where the selected route calls for an issued or retained record, the next service can add the appropriate persistent identifier, accountable issuer, signatures, status and continued access.