Journal
Understanding check-ins and message release
Start with the message and its person
A switch holds your written messages, email recipients, and a schedule. Drafts give you room to prepare. Before arming a switch, read the message, check the address, and make sure the plan reflects what you intend.
A check-in needs confirmation
Open the app, sign in, and tap the check-in button. Wait for confirmation from the service. Opening an email is not enough, and an offline or failed request does not reset the schedule.
A missed check-in is the beginning of reminders
The reminder sequence advances one stage at a time, followed by the configured grace period. A service interruption should not cause missed stages to be skipped. A failed reminder holds progression for review.
Act before release
A successful check-in before release resets the process. Pausing a switch stops its active schedule. Once release has happened, a later check-in cannot recall what was already shared.
Make room for the limits
Requiem is in development and live delivery is not ready to rely on. Keep your own copies, maintain current contact information, and do not treat an unconfigured development build as a dependable way to send critical information.