19 / 25
Investor discussion draftTechnology and data architecture
Core modules, data loops, privacy boundaries, reliability, and security.
Customer channelsWeb/PWAWellnessKioskExternal embedStatus/tracking
↕Shared business coreAccountsMenuOrdersPricingRewardsProgramsAttribution
↕Control and executionOperationsPaymentsKitchenDriversNotificationsAnalytics
↕Restricted providersTL-AI modelGoogle MapsSMS/Web PushPayment chains/providers
Data domains
| Identity | Account, contact, consent, saved delivery details |
|---|---|
| Wellness | Goal, calorie target, diet, allergens; account-scoped |
| Food truth | Ingredient, portion, nutrition, allergens, images, price |
| Commerce | Cart, order, discounts, payment state, refund |
| Operations | Availability, slots, timestamps, status, kitchen audit |
| Network | Location, partner, affiliate, commission, payout |
Reliability controls
- Server-side validation for prices, categories, calories, permissions, and rewards
- Nonces, signatures, rate limiting, secure cookies, origin/domain allowlists
- Order deduplication and idempotent payment handling
- UTC timestamps with browser-local presentation
- AI caching, retry, refund, and deterministic fallback
- Private payment keys and mnemonic outside WordPress
- Audit records for status, commission, payout, and settings changes
- Backup, restore, monitoring, and incident runbooks required operationally
Data flywheel
Meal offeredmenu truth
→Meal accepted/editedpreference signal
→Order fulfilledoperational signal
→Repeat/rewardretention signal
→Menu + model improvecontrolled learning
