Email AtlasAtlasIndexHomeOpen raw ↗
Candidate / member · Application journey

Application viewed

member transactional shadow 99/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
Triggerapplication_viewed

Source

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

Wiring

Trigger sourcelifecycle event → emitIntent
Dispatch actionsend-application-viewed
Channelemail
Brain policystandard · applications — capped + quiet-hours-eligible, bundle-eligible if marketing
Idempotencysha256(application_viewed · 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 99/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

No curated entries for this email yet. When you edit it, append a line to email-changelog.jsonl — see the changelog.

Feedback

Open GitHub issue ↗ Saved ✓
← Application receivedShortlisted →