Email AtlasAtlasIndexHomeOpen raw ↗
Candidate / member · Application journey

References request

member transactional shadow 98/100

In plain English — what this does

The moment this happens in ClubOS, the system automatically emails the member. They can turn this off in Settings, 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).

Delivery

Audiencemember · Candidate / member
Mail-classtransactional
Statusshadow
Fromnotifications@thequantumclub.nl
Reply-Toconcierge@thequantumclub.nl
Recipientscandidate
Triggerreferences_request

Source

Builder filecandidate-application-bodies.ts ↗
Renderaudit-artifacts/cand-references.html

Wiring

Trigger sourcelifecycle event → emitIntent
Dispatch actionengine-dispatch
Channelemail
Brain policystandard · applications — capped + quiet-hours-eligible, bundle-eligible if marketing
Idempotencysha256(references_request · entity · candidate · window)
Engine stateshadow (engine dormant until ramp)

Wiring is auto-derived from RECIPIENT_MAP + the notification registry — it cannot drift from the real engine wiring.

Audit

Lens-minimum 98/100 — scored on six lenses: component fit · copy & register · completeness · CTA integrity · purpose / managed-service · intelligence. ≥98 = converged.

Versions

Builder source history on GitHub →

History

  • newclaude-aa2026-06-17
    Built 4 net-new Tier-1 emails: references-request, candidate weekly + re-engagement digests, partner onboarding nudge, admin weekly exec summary
    Owner-approved net-new round; widens coverage across all three audiences
Full changelog →

Feedback

Open GitHub issue ↗ Saved ✓
← Role closedInterview scheduled →