Service Diagram · Boundaries & Contracts

16 services · 5 layers · event-bus only · no direct calls

Bounded contexts · event-bus communication

Each service owns its data and exposes a versioned data contract. Services never share a database and never call each other directly — they communicate only by publishing and subscribing to events on the bus. A service's contract is its public boundary; everything else is internal.

Service map by layer

Core CommerceInventory truth · freshness · pricing · marketplace · subscriptions · checkout
IntelligenceBehavior AI · meal planning · routing & delivery optimization
Financial LifecycleAtomic ledger · community credits · settlement
IntegrationSupplier hub · external systems
SurfacesWorker OS · Employer OS · Partner OS · Consumer app

Event-bus data flows

13 contracts on the bus
Inventory Telemetry Service
inventory.updatedInventorySnapshot
FreshScore Engine
FreshScore Engine
freshscore.updatedFreshScoreSnapshot
Pricing Orchestrator Service
FreshScore Engine
freshscore.updatedFreshScoreSnapshot
Zero-Waste Marketplace Service
FreshScore Engine
freshscore.updatedFreshScoreSnapshot
Behavior AI Service
Pricing Orchestrator Service
price.adjustedPriceAdjustment
Worker OS
Zero-Waste Marketplace Service
waste.item_flaggedWasteListing
Community Credit Engine
Behavior AI Service
recommendation.generatedRecommendation
Checkout Service
Checkout Service
order.createdOrder
Routing & Delivery Engine
Checkout Service
order.createdOrder
Ledger Service
Routing & Delivery Engine
order.fulfilledDeliveryAssignment
Ledger Service
Routing & Delivery Engine
order.fulfilledDeliveryAssignment
Community Credit Engine
Subscription Engine
subscription.renewedSubscriptionEvent
Ledger Service
Community Credit Engine
credit.earnedCreditEntry
Worker OS

All services