What's here
Each business process has two documents:
| Type | Purpose | Changes when |
|---|---|---|
| SOP | How we run this process day-to-day (owner, steps, failure modes) | The process changes |
| Runbook | How to activate or debug a specific system right now | The system changes |
Process index
Demo Booking
Cal.com → webhook → pipeline → lifecycle emails → admin console.
Demo Booking Runbook
Switch on migrations 0162–0166, Cal triggers, env vars, smoke test.
Migration Apply
Drizzle migration workflow, drift guard, journal conventions.
Oman Payroll & WPS
Payroll run, PASI, separation-of-duties approval, WPS SIF (.xlsx) generation.
Partner Activation
Tokenised proposal → NDA e-sign → kanban → close → portal access.
Flow: Demo Booking Lifecycle
flowchart TD
A([Visitor books demo on Cal.com]) --> B[Cal webhook → POST /api/webhooks/cal]
B --> C[demo_bookings row created]
C --> D[Sales notification email sent]
C --> E{Lifecycle job runs every 30 min}
E --> F[Reminder + RSVP email sent]
F --> G{Attendee clicks RSVP link}
G -->|Yes| H[confirmed_at set]
G -->|No| I[Chaser sent up to DEMO_REMINDER_MAX]
H --> J[Cal MEETING_STARTED webhook]
J --> K[attended_at set]
K --> L[Recap email with recording link]
J -->|No-show| M[Reschedule email]
C -->|Cancelled| N[Reschedule / re-engage email]