Getting Started
Architecture
Commerce Chain architecture — Five Pillars, OSS/hosted boundary, and ecosystem integrations.
2 min read · Getting Started
Commerce Chain connects supply chain and demand chain loops through Loop Engine, shared contracts, and optional hosted services.
New to loop participation? After this overview, read the Loop Participation guide to see how modules declare which loops and events they handle, and the Runtime configuration guide for the adapter injection pattern (no global database import inside packages).
The CCO model
SCM and DCM are modeled as one operational system: loops share state through Loop Engine events instead of separate orchestration stacks.
OSS surface vs hosted platform
Domain types, loop definitions, guard contracts, and adapter interfaces are open and portable.
AI intelligence services, tenant isolation, hosted execution, billing, and enterprise compliance reporting are part of Better Data CCO.
Apache-2.0 is used for explicit patent grant support and enterprise legal adoption.
Technology stack
- Loop Engine runtime executes all SCM/DCM loops.
- Commerce Gateway provides LLM-ready commerce data access.
- Signal Tags emits product-authentication signals for compliance loops.
@commerce-chain/*packages provide framework contracts.
End-to-end procurement flow
- Signal Tags verification event marks a suspect lot (
SENSE). - AI actor retrieves supplier context through Commerce Gateway (
DECIDE). - Guard policy evaluates confidence and permission constraints (
GOVERN). - Human buyer approves procurement action (
EXECUTE). - Loop completion emits learning signals and outcome deltas (
IMPROVE).
Deployment options
- Self-hosted: run Loop Engine + Commerce Chain contracts in your infra.
- Hosted: Better Data operates multi-tenant CCO with managed integrations.