1. Create
Write and encrypt
Draft messages and recipients first. Message content is stored encrypted at rest and decrypted only for authenticated reads or controlled delivery processing.
How it works
The system nudges first, then releases only when the threshold is crossed.
No Longer Here is built around a staged execution model: write and encrypt the message, verify the recipient, watch for missed check-ins, send reminders first, then release through a queued delivery flow only when the configured threshold is crossed.
2. Verify
Invite the recipient
Recipients confirm identity in advance. They can accept the role early, but they still cannot read the message before release conditions are met.
3. Protect
Heartbeat and release
Check-ins and grace windows are measured against your heartbeat settings. Messages are only eligible for release once the threshold is crossed.
Reminder phase
Before the final threshold is reached, the system sends owner reminders. This exists to reduce accidental delivery caused by a single missed check-in or a short interruption.
Reminder evaluation and reminder processing are separate queued operations. That keeps them reliable, auditable, and safe to run on infrastructure that later moves from shared hosting to dedicated workers.
Release phase
Once the threshold is crossed, armed messages move into a release queue. Delivery attempts are claimed, processed, retried if necessary, and recorded so the operational path can be inspected later.
This release path is intentionally separate from ordinary page requests. It is designed to be worker-safe, reclaim stale jobs, and avoid tying message delivery to a user pressing a button in the dashboard.