Pulse (PBCP Pulse)
App URL: https://pulse.pcampus.co
Context API: https://pbcp-api.pcampus.co/context
Overview
PBCP Pulse is the reference application of the Pcampus Business Context Platform (PBCP). It transforms Business Context into Business Stories that business owners can understand without needing to know the underlying infrastructure.
Every screen answers: What happened? · Why? · What next?
Pulse is not an ops dashboard — it is a Story Explorer that lets businesses see themselves through the lens of their data.
Who uses this
| Persona | What they do |
|---|---|
| Business owner / Stakeholder | View Business Stories — what customers are doing, how sales are trending, whether promotions are working |
| Product Manager | Verify the accuracy of Business Context |
| Platform Engineer | Use Developer Mode — Event Timeline, Pipeline, Health |
| Sales / Demo | Demonstrate PBCP value to prospective customers in 60 seconds |
Two modes
Story View — the default experience for business stakeholders: see each entity's story through a timeline
Developer Mode — secondary mode for engineers who need to inspect raw events and the pipeline
Story View — how it works
Story types
A Story is the evolution of a business entity reconstructed from Business Context — not a log of raw events.
| Story | Question it answers |
|---|---|
| Customer Story | Who is this customer, what have they done, what is their total value? |
| Order Story | How did this order travel through the system, where did it get stuck? |
| Product Story | How well does this product sell, who buys it, and when? |
| Campaign Story | Did this campaign work, who responded? |
| Promotion Story | Was this promotion worth it compared to the revenue it drove? |
One engine, many domains — a pharmacy uses Customer Story and Order Story out of the box; other domains (retail, school, factory) use the same engine.
Data flow
Story Timeline UX
Three-panel layout — select an entity → see its timeline → drill down into details + recommended actions
Pilot — Pharmacy
Pharmacy Platform is the first production implementation of PBCP.
The pharmacy sends Business Events via the Event SDK:
customer.visited— patient visits the pharmacyprescription.dispensed— medication dispensedproduct.sold— product soldpayment.completed— payment received
Pulse displays the Customer Story: how often this patient visits, what they purchase, whether they are on continuous medication — without ever opening the database directly.
Technical overview
| Area | Choice |
|---|---|
| Framework | Next.js, React, TypeScript |
| UI | Tailwind CSS, shadcn/ui |
| Animation | Motion (motion.dev) — timeline transitions |
| Charts | Apache ECharts — funnel, sankey, time series |
| Story Timeline | Custom StoryTimeline component (no chart library) |
| Context API | PBCP Context API v1 (required) |
| Intelligence | PBCP Intelligence API v1 (optional enrich) |
| Deployment | cockpit.pcampus.local · demo env: COCKPIT_DEMO_MODE |
Integration
Pulse reads data through the Context API only — it never queries the Event Store directly and never sends LINE messages, emails, or push notifications itself.
Context API overview
| Method | Endpoint | Description |
|---|---|---|
GET | /context/pulse | Today's business summary |
GET | /context/customers | List customers with context |
GET | /context/customers/:id | Full Customer Context + story |
GET | /context/orders | List orders with context |
GET | /context/orders/:id | Full Order Story |
GET | /context/products/:id | Product Story |
GET | /context/campaigns/:id | Campaign Story |
Full PBCP Core API reference → API Reference →