Skip to content
Darwin Evolution

Glossary

Compliance and traceability accumulate acronyms fast. This page collects the ones that show up across the docs, ordered by frequency in our context.

Compliance frameworks

Section titled “Compliance frameworks”

FSMA 204: Food Safety Modernization Act, Section 204 (US FDA). Mandates traceability for designated foods. Effective for high-risk foods on 2028-07-20. Concrete obligations:

  • CTE (Critical Tracking Event): a recorded supply-chain event that the FDA considers material (receiving, transformation, shipping, etc.).
  • KDE (Key Data Element): the specific data fields the CTE must carry (date, location, quantity, lot code, etc.).
  • TLC (Traceability Lot Code): unique identifier for a batch that follows it across the chain.

EUDR: EU Deforestation Regulation. Mandates that 7 commodities entering the EU (cattle, cocoa, coffee, oil palm, rubber, soya, wood) prove deforestation-free origin via geolocation. Effective 2026-12.

  • DDS (Due Diligence Statement): the document the importer files declaring no-deforestation evidence per shipment.

USMCA: US-Mexico-Canada Agreement (NAFTA successor). Customs framework requiring proof of origin for goods crossing the border duty-free.

  • Certificate of Origin (USMCA): the BOM-by-origin document the producer / exporter self-certifies.

IATF 16949: Automotive quality management standard from the International Automotive Task Force. Mandatory for tier-1 / tier-2 suppliers to OEMs. Quality records:

  • PPAP (Production Part Approval Process)
  • FAI (First Article Inspection)
  • SPC (Statistical Process Control), with Cp / Cpk capability indices.

ESPR: Ecodesign for Sustainable Products Regulation (EU). Frames the Digital Product Passport (DPP) mandate that progressively rolls out from 2027 by category (textiles, batteries, electronics first).

EU 2023/1542: EU Battery Regulation. Mandates a battery passport for industrial / EV / LMT batteries from 2027-02.

Identity & data formats

Section titled “Identity & data formats”

DID: Decentralized Identifier. W3C spec for crypto-anchored identity. Each tenant + organization in Darwin has a DID. Events are signed against DIDs.

EPCIS 2.0: GS1’s standard for Electronic Product Code Information Services. Models supply-chain events as ObjectEvent / AggregationEvent / TransformationEvent. Darwin maps its internal event model to EPCIS 2.0 for interoperability with GS1-compliant systems.

GS1 Digital Link: URL syntax that encodes GTIN / lot / serial in a QR-friendly format (e.g. /01/<gtin>/10/<lot>/17/<expiry>). The Fidenta passport viewer renders this resolver pattern.

GTIN: Global Trade Item Number. The 8/12/13/14-digit barcode you scan at retail.

HMAC-SHA256: symmetric signature algorithm used for webhook payload integrity and per-tenant QR verification. Each tenant has a secret. Signatures are verifiable client-side without exposing the key.

Darwin product names

Section titled “Darwin product names”

Captia: the capture layer. Mobile PWA plus ERP, IoT, and CSV connectors. Digitizes the workshop, the field, and the smallholder where no existing system covers the first link of the chain.

Tracium: the traceability layer. Standardizes captured events, anchors them on-chain (Polygon PoS + OP Stack L2, 13 smart contracts), auto-generates regulatory bundles per framework.

Fidenta: the digital identity layer. Mints a per-product passport accessible via QR. Views per stakeholder: consumer (storytelling), retailer (compliance data), auditor (technical evidence), brand (analytics).

Operational terms

Section titled “Operational terms”

Sandbox: non-production tenant for development / evaluation. Free-tier, same APIs as production but synthetic data and no on-chain finality cost.

Whitelabel: every front-end (Captia, Tracium, Fidenta viewer and dashboard) applies tenant-specific branding at runtime: logo, colors, typography, copy, custom domain. New tenants pick their brand at provisioning, with no code changes required.

Multi-tenant: a single sandbox or production environment hosts multiple tenants. Tenant operational data is isolated per tenant at the database layer via tenantId scoping. The on-chain layer stores hashes and references, designed to be verifiable without exposing sensitive data, since the original payloads stay off-chain under tenant access control.

Idempotent UUID: a client-generated identifier sent with capture submissions. If the same UUID arrives twice (network retry, sync restart), the server returns the original result without creating a duplicate event.