Live demos
Five products. Five chains.
All signed. All real.
Each record is a complete schema.org JSON-LD provenance chain — machine-readable, AI-queryable, compliance-verified. The record is the demo. No mockups.
Heritage handwoven chain. Artisan-signed from herder to export. Demonstrates privacy-tier 2 (community visible) and GI tag support.
Berry Amendment demo chain. 100% domestic origin at every hop. DoD audit-ready export. The hardest compliance case — if Economy3 passes DoD audit, it passes everything.
Cotton commercial chain. Farm → gin → spinning mill → fabric. Demonstrates multi-jurisdiction compliance: ESPR + CA Scope 3 + worker disclosure at brand step.
Peruvian alpaca chain. Demonstrates naturally coloured fibre (no dye step), high-altitude origin, and ESPR animal welfare attestation.
EUDR (EU Deforestation Regulation) demo. GPS coordinates on file, satellite cross-referenced against Dec 2020 baseline. Abebe Girma, 0.8ha, Gedeo agroforestry. Same schema.org material-chain pattern as textiles — sector vocabulary in additionalProperty.
DoD audit demo. Every hop is domestic: TX cotton gin → NC spinning mill → SC fabric mill (NYCO ripstop weave) → VA cut & sew → DoD inspection. Signed at each custody transfer. Berry Amendment compliance computed at query time from the signed hop chain, not from a certificate.
How the schema works
One pattern. Every sector.
All five demos use the same schema.org material chain pattern — a Product nested inside a Product to represent custody stages. Coffee uses the same pattern as wool — washing station is the ginning equivalent, dry mill is the scour equivalent. Sector-specific vocabulary (cupping score, EUDR GPS, HS codes) goes in additionalProperty.
This is the design: one open schema handles any physical product, any supply chain, any jurisdiction. The compliance engine runs against machine-readable rules — not hardcoded logic — so new regulations are new rule files, not new code.