Domain Examples
PBCP is a domain-agnostic platform — one engine that supports any business where "events happen" in its system.
Whether it's a pharmacy, an online store, a logistics company, or a SaaS app — the structure is exactly the same:
Business Events → Business Context → Business Story → Intelligence → DecisionsWhat changes between domains is only the event names and payload — the core engine is 100% identical.
What is shared across all domains
| Layer | Shared |
|---|---|
| Event Store | Append-only, immutable — every event from every domain is stored in the same place |
| Context Builder | Logic that transforms events → context (extensible per entity type) |
| Story Engine | Composes stories from context — 1 engine, ∞ domains |
| Intelligence | Churn risk, abandonment, engagement — patterns are transferable |
| Pulse UI | StoryTimeline component renders for any domain |
What is domain-specific
| Layer | Domain-specific |
|---|---|
| Event catalog | Event names and payload schema for each domain |
| Adapters | Code that transforms app events → PBCP canonical events |
| Story labels | "Cart abandoned" vs "Shipment delayed" vs "Student dropped course" |
| Context types | Shipment Context ≠ Patient Context ≠ Student Context |
Domains
How any domain plugs in
Your App (any domain)
Business action
e.g. order placed, patient visited,
shipment dispatched
track(eventName, payload)
PBCP Platform
Event API
Context Builder
Story Engine
Intelligence
Consume
Pulse
Story Explorer
Your Marketing App
execute offers
3 steps to integrate any domain:
- Define event catalog — specify the events that occur in your business (Event Catalog →)
- Instrument your app — call
track(eventName, payload)at each point where an event occurs - Read stories — call the Story API or open Pulse to view Business Stories immediately