An agent handling a shipment records the inputs it consulted: supplier attestations, audit reports, origin certificates, and the policy version in force at that moment.
Solutions · Supply Chains
Replaces · Siloed compliance databases · Vendor-controlled audit logs
Verifiable AI for supply chains.
Traceable handoffs from source to shelf.
Global supply chains span dozens of suppliers, auditors, and regulators, yet the reasoning behind each compliance decision is scattered across siloed databases and vendor audit logs. nOS captures every audit rationale, exception approval, and handoff as a signed decision trace, so the "why" behind a shipment travels with it from source to shelf. Trace Labs works with networks like SCAN (the Supplier Compliance Audit Network) to make multi-party compliance verifiable and portable.
Decision traces enshrinedAudit decision rationale Exception approvals across borders Customs and origin verifications Multi-tier supplier attestations
What gets captured
Most relevant memory layers
Shared & Verifiable
Working memory captures private agent reasoning. Shared memory is where multi-party context coordinates. Verifiable memory is where decisions are enshrined.
~40%
US imports audited via the protocol
Deployment & partners
SCAN, Supplier Compliance Audit Network
Real enterprise data, processed in production, with decision traces enshrined as Knowledge Assets in the OriginTrail DKG.
The problem
The case for verifiable decisions in supply chains.
Supply chain compliance is a multi-party problem solved with single-party tools. A retailer audits a tier-one supplier, that supplier attests for tier two, and a customs broker files on behalf of all of them. Each party keeps its own records, so when a regulator asks why a shipment was cleared, the answer has to be reassembled from email threads, PDF certificates, and a database nobody outside the company can inspect.
Regulations have made that reassembly expensive. UFLPA forced-labor rules, the EU Deforestation Regulation, CBAM carbon reporting, and FSMA 204 food traceability all require evidence that reaches past your direct suppliers. AI agents deployed on top of the existing silos inherit the same blind spots: they can tell you a shipment was approved, not what evidence made approval defensible.
How it works
How a decision becomes verifiable.
Context that other parties are entitled to see moves into shared memory, so the broker, the auditor, and the buyer work from the same facts instead of three reconciliations.
The agent applies policy and records the reasoning, including which exception was granted, who was entitled to grant it, and what precedent from earlier shipments it inherited.
The resulting decision trace is written to the OriginTrail DKG as a Knowledge Asset, so any counterparty or regulator can verify it later without access to your systems.
What changes
What this changes in practice.
The practical change is where evidence lives. Instead of a compliance team assembling a defense after a question is asked, the reasoning behind each clearance already exists in a form a customs authority or buyer can check. Determinations stop being assertions backed by filing cabinets and become records with lineage.
That also changes what an agent is worth. An agent that clears shipments without leaving a trace saves time and adds risk. An agent that clears shipments and enshrines why each clearance was permitted compounds: the hundredth decision inherits precedent from the previous ninety-nine, and the audit that follows is a query rather than a project.
FAQ
Questions about supply chains.
How is this different from supply chain traceability software?
Traceability software records where goods moved. A decision trace records why a compliance decision about those goods was allowed: the evidence consulted, the policy applied, the exception granted, and the precedent inherited. Movement data alone does not answer a regulator asking how a determination was reached.
Do our suppliers have to adopt nOS as well?
No. Suppliers can keep their existing systems. What matters is that attestations and audit evidence entering a decision are referenced and signed, so the resulting trace is verifiable even when the parties run different software.
Does this expose commercially sensitive supplier data?
No. Working memory and private context stay in your infrastructure. Only the commitments and metadata you choose to publish are recorded, which lets a counterparty verify that a decision followed policy without seeing your pricing or supplier list.
Which supply chain regulations does this help with?
Any regime that requires defensible evidence rather than a stored document: UFLPA and comparable forced-labor rules, the EU Deforestation Regulation, CBAM, and FSMA 204 traceability. nOS does not file for you; it makes the reasoning behind each determination auditable.
How long does it take to see value?
The first useful traces appear as soon as one decision type is instrumented, typically a single high-volume determination such as origin verification. Value comes from depth on one workflow rather than shallow coverage of many.
What happens to our existing audit records?
They remain valid and can be referenced as inputs. nOS does not require migrating history; it changes how decisions are recorded from the point of adoption forward.
Start free
Power up your business with the OriginTrail DKG.
Create Knowledge Assets, build shared context graphs, enshrine decision traces. Open-source infrastructure. Community support. Zero cost.
Go Pro
The full Network Operating System.
Custom agent frameworks (Hermes, OpenClaw, LangChain, Claude). Custom data pipelines. Custom integrations with your enterprise systems. Dedicated infrastructure and support.