Something interesting is happening in supply chain compliance conversations right now. Large buyers — electronics manufacturers, automotive OEMs, major brands — are starting to ask for verified facility data from suppliers who aren't members of any formal certification body. No audit on file. No network membership. Just: we need to know who you are and where you operate, in a format we can actually verify.
A lot of this sprint was invisible to end users but will matter to everyone who's looked at a credential render and thought "this is a lot to scan." Today's post covers a full redesign of how Digital Product Passports display, two AI misbehavior problems (and how we fixed them), and one deliberate decision to leave something that looks like a bug alone.
When you open a Digital Product Passport for the first time, one of the first things you'll encounter is a product identifier — a structured string of numbers that tells verifying systems exactly what product this credential describes and at what level of granularity. Those identifiers are built on GS1 Application Identifiers (AIs). This post breaks down the three AI codes you'll encounter most in a DPP, what each one means, and why the distinction between model, batch, and serial level matters more than it might initially seem.
Intro Guide and Video to getting started with DPP Kit
Milestone 1 is complete: all five UNTP credential types are live in DPP Kit, with AI-assisted credential creation for Digital Product Passports and Digital Facility Records. Here's what shipped, the bugs that taught me things, and what's coming next — including selective disclosure by April.
The core flow — upload documents, let the AI agent extract claims, review and edit, issue a credential — was working. But there were enough rough edges in how state moved between the editor, the AI agent, and Directus that real usage was exposing real problems.
Sprint Update: Days 8-9 — AI Credentials, Stateless Verification, and a Launch-Blocking Bug We Almost Missed We're nine days into what I've been calling the epic sprint, and the last two days were a mix of genuinely exciting new capability and the kind of architectural reckoning that makes you grateful you caught it before launch. Here's what happened.
This post documents Day 7 of building DPP Kit in public, covering the development of an AI-assisted credential editor that lets users generate and refine UNTP-compliant credentials through a split-panel chat interface with per-field accept/reject controls. It also captures key architectural decisions — like shared context builders, prompt caching, and Tier 2 validation integration — that make the system efficient to scale across credential types.
Day 5 of building a UNTP compliant W3C Verifiable Credential Issuing and Management System. Today we tackled integrated Tier 2 testing into it's own module and also inline during credential editing and issuing.
Tales of Day 4, going from local development to a publicly accessible multi-tenant UNTP credential issuing platform
Building in public road map for a multi-tenant W3C Verifiable Credentials management platform to support UNTP practitioners. From empty directory to published to dppkit.io with build in Tier 2 testing in just a week.
Building production-ready UNTP infrastructure in 4 weeks - and doing it in public. Follow along as DPP Kit goes from beta launch to AI-assisted credential creation to full production, helping supply chain organizations meet EU ESPR compliance deadlines.
Supply chain transparency is no longer optional. Regulators worldwide are demanding proof of sustainability claims. Consumers want to know the real story behind products. And businesses need verifiable credentials that can't be greenwashed away.