How kingterentius/foodtribeos works
Food Tribe OS is an in-development platform for food-service organizations. Its documented target workflow is event-driven: an inventory donation can prompt a volunteer-shift suggestion in Events, with Dapr providing messaging, service invocation, and state-management building blocks. The README also names Identity, Inventory, and Events as core domains. The tree shows app and service areas, but the only indexed source is package metadata; this graph therefore reflects documented architecture, not verified runtime wiring.
Main entry points: services Inventory service · users Identity service
Components 11
Product apps
- Web app
food-tribe-os/apps/web - Discovery app
food-tribe-os/apps/discovery-app - App features
food-tribe-os/apps/features
Domain services
- Identity service
food-tribe-os/services/users - Inventory service
food-tribe-os/services - Events service
food-tribe-os/services - API service
food-tribe-os/services/api - Gamification service
food-tribe-os/services/gamification
Dapr building blocks
- Dapr runtime
- Abstract state store
Other components
- Food organizations
Connections 9
- Inventory service → Dapr runtime: publishes donation
- Dapr runtime → Events service: dispatches event
- Identity service → Dapr runtime: invokes services
- Inventory service → Dapr runtime: invokes services
- Events service → Dapr runtime: invokes services
- Identity service → Dapr runtime: manages state
- Inventory service → Dapr runtime: manages state
- Events service → Dapr runtime: manages state
- Dapr runtime → Abstract state store: stores state