CUSTODYLINE
The Problem
Live Proof
The Vision
Contact Us
Past Tier 1, custody is tracked in email threads and PDFs that different organizations keep separately and rarely fully agree on. Recalls expose that gap the most painfully, but it's the same gap behind warranty disputes, vendor SLA claims nobody can verify, and shipments nobody can explain the timing on.
Component manufacturer in one country. Sub-assembly built in a second. Final assembly in a third. Three tiers, three jurisdictions, before the part ever reaches a customer.
Every organization keeps its own records. When a recall, a warranty claim, or a vendor dispute needs a real answer, everyone is reconciling spreadsheets and hoping much nothing was missed.
Blanket recalls because nobody can pinpoint the actual affected units. Warranty disputes with no shared evidence. Vendor SLAs nobody can independently check.
What follows is that scenario, built and running. Not a mockup.
Click any node. The hub can look into any one supplier on demand, or see everything it's received; suppliers can never see each other's. Illustrative of the access model the real network enforces via Fabric private data collections.
A unit's full build only opens once it clears warranty registration. Try the unregistered one.
Recall impact is one use of this trace. The same data backs warranty validation, vendor SLA checks, and route timing analysis.
Reads the same custody history as the recall trace, pointed at a different question: is this unit actually covered.
Computed from real Shipped → Received timestamps already in the ledger, no extra data needed.
Natural-language part lookup and anomaly flagging across the full ledger. On the roadmap, not in this build.
Point the camera at any part's QR code in the Bill of Materials above, or a printed/etched code on a real part carrying the same ID.