In plain English — what this does
The moment this happens in ClubOS, the system automatically emails the member within seconds. Because it's time-sensitive, it always sends right away — and it's never sent twice for the same event.
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 | built |
| From | notifications@thequantumclub.nl |
| Reply-To | concierge@thequantumclub.nl |
| Recipients | candidate |
| Trigger | account_deletion_requested |
| Builder file | account-security-bodies.ts ↗ |
|---|---|
| Render | audit-artifacts/ac-deletion-requested.html |
| Trigger source | lifecycle event → emitIntent |
|---|---|
| Dispatch action | engine-dispatch |
| Channel | email |
| Brain policy | express · system — uncapped, bypasses quiet-hours/frequency-cap |
| Idempotency | sha256(account_deletion_requested · 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.
No curated entries for this email yet. When you edit it, append a line to email-changelog.jsonl — see the changelog.