In plain English — what this does
The moment this happens in ClubOS, the system automatically emails the member. This one is essential, so it always sends, and it's never sent twice for the same event, and quiet-hours stop it arriving at a bad time.
Dark-inbox is a simulated backdrop — the email is pinned light by design (best-effort dark preview).
| Audience | member · Candidate / member |
|---|---|
| Mail-class | transactional |
| Status | shadow |
| From | notifications@thequantumclub.nl |
| Reply-To | concierge@thequantumclub.nl |
| Recipients | candidate |
| Trigger | payment_succeeded |
| Builder file | member-billing-bodies.ts ↗ |
|---|---|
| Render | audit-artifacts/mb-receipt.html |
| Trigger source | lifecycle event → emitIntent |
|---|---|
| Dispatch action | send-payment-receipt |
| Channel | email |
| Brain policy | standard · mc:transactional — capped + quiet-hours-eligible, bundle-eligible if marketing |
| Idempotency | sha256(payment_succeeded · entity · candidate · window) |
| Engine state | shadow (engine dormant until ramp) |
Wiring is auto-derived from RECIPIENT_MAP + the notification registry — it cannot drift from the real engine wiring.
Lens-minimum 98/100 — scored on six lenses: component fit · copy & register · completeness · CTA integrity · purpose / managed-service · intelligence. ≥98 = converged.