Core Concepts
Identity Resolution
Cross-channel identity via ChannelIdentity, multi-tenancy, and how leads are resolved.
Architecture
Event-driven architecture, Lambdas, ingestion flow, and database strategy.
Events
Inbound contract from Webhook Domain, internal service signals, and event types.
Memory
Long-term memory system, derivation from events, and concrete examples.
Features
Computed numeric features for ML/MAB consumption.
Open Decisions
Architectural decisions still under discussion.
Key Patterns
- Signals, not raw data — stores what happened to the lead, not how it happened
- Event → Memory — enriched data derived from events, no per-source tables
- ChannelIdentity as sole source of identity resolution
- Global lead, org-scoped data — one person = one Lead, behavioral data via LeadOrganization
- Feature store designed for future ML/MAB consumption