🇩🇰 🇪🇺

Founder Onboarding Ritual

13 Notarized Digital Events — one founder's journey from invitation to genesis membership.
First 100 founders receive 2 Eldersafe email accounts as founding member reward.

Founding Member — #001–#100

🎗️ Genesis Cohort

You are one of 100. Your onboarding is not just a signup — it is the first proof that the Eldersafe–Ældre Sagen collaboration model works. Every step is a numbered, timestamped digital event. Every event is auditable.

Phase 1 — Email Infrastructure (Events #001–#004)

Before you touch Eldersafe, your digital identity must exist. You get two email addresses — one on eldersafe.dk (Simply.com) and one mirrored on eldersafe.cloud.

#001
🔑 System: Issue Founder Invitation
Timestamp: auto-generated · Authority: Eldersafe Registrar · On-chain: no

Each founder receives a unique invitation token. This token binds their membership number to the genesis cohort and authorizes email account creation.

Invitation issued to founder #NNN with membership number FDR-NNNNN
Invitation token: eldersafe-genesis-XXXX-XXXX-XXXX
Expires: 72 hours from issuance
#002
👤 Founder: Access Simply.com Control Panel
Actor: founder · Duration: ~2 minutes
  1. Navigate to https://www.simply.com/en/login/
  2. Log in with Eldersafe admin credentials (provided separately via secure channel)
  3. Navigate to Email → Email Accounts
  4. You are now in the email management panel for eldersafe.dk
🌐 URL: https://www.simply.com/en/login/
🔐 Auth: Eldersafe admin username + password
📍 Target: Email → Email Accounts → Create new
#003
📧 Founder: Create membershipnumber@eldersafe.dk
Actor: founder · Domain: eldersafe.dk · Host: Simply.com (mx.simply.com)
  1. Click "Create email account"
  2. Enter Username: FDR-NNNNN (your membership number)
  3. Enter Password: auto-generated (24 chars, saved to password manager)
  4. Set Mailbox quota: 50 MB (Eldersafe policy — text-only, no attachments)
  5. Click Create
  6. Verify: send test email to FDR-NNNNN@eldersafe.dk
📧 New email: FDR-NNNNN@eldersafe.dk
🔐 Password: [auto-generated · 24 chars]
📦 Quota: 50 MB
⚡ MX: mx.simply.com (DKIM: simplycom1._domainkey)
🔐 Security: This password is stored ONLY in the founder's personal password manager. Eldersafe never stores email passwords. This is your primary Eldersafe email.
#004
🔄 System: Mirror Email to eldersafe.cloud
Authority: Eldersafe Infra · Target: FDR-NNNNN@eldersafe.cloud

Simply.com supports automatic forwarding. The system configures a forward rule so all mail arriving at FDR-NNNNN@eldersafe.dk is also delivered to FDR-NNNNN@eldersafe.cloud — Eldersafe's internal mail system.

  1. In Simply.com Email panel, select the new account → Forwarding
  2. Add forward address: FDR-NNNNN@eldersafe.cloud
  3. Enable "Keep copy in mailbox" (important — both inboxes receive)
  4. Save. Verify by sending test email to eldersafe.dk address — should appear in both inboxes.
📤 Forward: FDR-NNNNN@eldersafe.dk → FDR-NNNNN@eldersafe.cloud
📥 Keep local: YES (dual delivery)
🏷️ Internal route: /var/mail/eldersafe/FDR-NNNNN/
Why mirroring? The eldersafe.dk address is the "public face" — the one Ældre Sagen sees. The eldersafe.cloud address is the internal, system-integrated inbox that Eldersafe's automation can read, parse, and respond from. Two addresses, one identity. This is the founding member flex.

Phase 2 — Eldersafe Signup (Events #005–#008)

Now your email exists. Time to claim your digital identity on Eldersafe.

#005
🔐 Founder: Sign Up on Eldersafe
Actor: founder · Target: https://eldersafe.cloud/login
  1. Open browser → https://eldersafe.cloud/login
  2. Enter Medlemsnummer: FDR-NNNNN
  3. Enter E-mail: FDR-NNNNN@eldersafe.dk
  4. Click "Send login-link"
  5. Check your eldersafe.dk inbox for the magic link
  6. Click the magic link → redirects to Eldersafe dashboard
🌐 URL: https://eldersafe.cloud/login
📝 Medlemsnummer: FDR-NNNNN
📧 Email: FDR-NNNNN@eldersafe.dk
🔗 Magic link expires: 10 minutes
#006
⚙️ System: Create Verification Request
Authority: Eldersafe · DB table: verification_requests · Status: pending

On first signup, Eldersafe automatically creates a membership verification request. This is the core of the pilot — no API, no MOU. Just an email.

INSERT INTO verification_requests (member_id, member_number, status, deadline_at)
VALUES (NNN, 'FDR-NNNNN', 'pending', '2026-06-13 00:00:00')

✅ Request #NNN created
📅 Deadline: 14 days from now
📨 Emails remaining: 3 of 3
⏰ First reminder: 72 hours
#007
📨 System: Send Verification Email to Ældre Sagen
From: login@eldersafe.dk · To: info@aeldresagen.dk · CC: FDR-NNNNN@eldersafe.dk

The system fires the verification email. This is the genesis moment — the first official contact between Eldersafe and Ældre Sagen for this member.

Subject: Medlemsbekræftelse — medlem FDR-NNNNN / Eldersafe
To: info@aeldresagen.dk
CC: FDR-NNNNN@eldersafe.dk
Reply-To: FDR-NNNNN@eldersafe.dk
Body:
Kære Ældre Sagen,

En person med medlemsnummer FDR-NNNNN har anmodet om
bekræftelse af gyldigt medlemskab i Ældre Sagen via Eldersafe.

Denne email er også sendt til FDR-NNNNN@eldersafe.dk.
Al yderligere korrespondance bedes rettet til denne adresse.

Svar venligst med én af følgende:
  "vi bekræfter" — medlemskabet er gyldigt
  "vi afviser at udtale os" — vi kan hverken be- eller afkræfte

Såfremt der ikke modtages svar inden 14 dage,
betragtes anmodningen som udløbet.

Med venlig hilsen
Eldersafe
#008
📬 Founder: Receive CC at eldersafe.dk + eldersafe.cloud
Actor: founder · Verification: dual inbox delivery

The founder receives the verification email in BOTH inboxes thanks to the mirroring set up in Event #004. This proves the email infrastructure works end-to-end.

  1. Check FDR-NNNNN@eldersafe.dk inbox — verification email received ✓
  2. Check FDR-NNNNN@eldersafe.cloud inbox — verification email received ✓
  3. This dual receipt is logged as proof of delivery
🔍 Why this matters: If Ældre Sagen replies, the reply goes to FDR-NNNNN@eldersafe.dk (the Reply-To header), which forwards to FDR-NNNNN@eldersafe.cloud where Eldersafe's automation can process it. The founder sees everything. Nothing is hidden. This is the transparency model.

Phase 3 — Verification Resolution (Events #009–#011)

Now we wait — with structured reminders. This is the part that demonstrates the collaboration model works (or doesn't). Either outcome is data.

#009
⏰ System: Reminder Schedule Begins
Authority: Eldersafe Cron · Max: 3 emails total · Anti-spam by design

The reminder engine runs every hour, checking all pending verification requests. For this founder:

Email # When Type Subject
1 Immediately (t=0) Initial request Medlemsbekræftelse — medlem FDR-NNNNN
2 +72 hours (t+3d) Påmindelse 1 Påmindelse 1 — Medlemsbekræftelse FDR-NNNNN
3 +168 hours (t+7d) Påmindelse 2 Påmindelse 2 — Medlemsbekræftelse FDR-NNNNN

After 3 emails: no more reminders. After 14 days: timeout. Clean, respectful, auditable.

#010
🏛️ External: Ældre Sagen Responds (or Doesn't)
Actor: Ældre Sagen · Channel: email reply-to FDR-NNNNN@eldersafe.dk

Three possible outcomes — all of which are data:

Response Status Meaning
✅ "vi bekræfter" verified Membership confirmed. Full activation. The model works.
❌ "vi afviser at udtale os" refused They won't confirm/deny. We have a response — engagement exists.
⏰ No response timeout 14 days pass. 3 emails sent. No reply. Documented silence.
📊 Pilot data: Across 100 founders, the distribution of verified/refused/timeout IS the pilot result. If 60% are verified, 20% refused, 20% timeout — that's the proof Ældre Sagen engages with the format. If 0% respond — that's proof too. Either way: we have data where before we had assumptions.
#011
✅ System: Verification Resolved → Founding Member Activated
Authority: Eldersafe · DB UPDATE: verification_requests.status = 'verified'

The verification request is resolved. The member's dashboard updates automatically. The audit trail is complete.

UPDATE verification_requests
SET status = 'verified', response = 'vi bekræfter', responded_at = '2026-06-XX'
WHERE member_number = 'FDR-NNNNN'

🎗️ Founding member #NNN activated
📊 Verification events: 11 notarized digital events
🔗 Audit trail: complete and immutable

Phase 4 — Founding Member Reward (Events #012–#013)

The flex. Only 100 people will ever have this.

#012
🎁 System: Issue Second Eldersafe Email (Founding Member Reward)
Authority: Eldersafe · Reward: 2nd email account · Cohort: Genesis #001–#100

As a founding member reward, you receive a SECOND Eldersafe email address. This one is a vanity alias — clean, personal, flexible. While your primary address is FDR-NNNNN@eldersafe.dk (the system-facing identity), your reward address is human-readable.

  1. System creates second email account on Simply.com
  2. Format: [founder-chosen-alias]@eldersafe.dk
  3. Same 50 MB quota, same mirroring to eldersafe.cloud
  4. Example: jens@eldersafe.dk (if founder is named Jens and chooses that alias)
  5. Both emails appear on the founder's Eldersafe dashboard
📧 Primary: FDR-NNNNN@eldersafe.dk (system identity)
🎁 Reward: [alias]@eldersafe.dk (founding member flex)
🔄 Both mirrored to: FDR-NNNNN@eldersafe.cloud
👥 Only 100 people will ever have two Eldersafe emails
Why a second email? The membership-number email is functional — it's how the system identifies you and how Ældre Sagen's reply is routed. The alias email is human — it's what you give to other members, what appears in the community, what feels personal. It's the difference between a database key and a name. Founding members get both.