Eve library

Chapter 3 · Moved to seven, with nothing to send it · brief · 11 September 2026

Guide

Revision 1

On this page

The third chapter of the Tara · continue track, rewritten in the Eve edition on 11 September 2026. It follows the plan in EVE-V1-REDESIGN-TODOS.md and the track brief in tara-continue-track.md. The receipt is under verification/.

The job#

Chapter two asked what should shape a practice. This one asks when a member is invited back. Tara's ritual scheduler builds a plan from a template, the member's scheduling preferences and a supplied continuity state: an invitation time, a primary reminder and sometimes a follow-up. It saves the plan in an in-memory store and can list what is upcoming and what is due.

The chapter teaches where an invitation lands and why — a clock rule, a continuity rule, then quiet hours — why each reminder lands where it does, and what happens to the records afterwards. No application code calls the scheduler, and no code was found that sends a due reminder.

Running example. Monday 7 September, 21:50 UTC, a recovery window, a preferred time of 22:15 and quiet hours from 22:00 to 07:00 every day. Executed with pinned clocks: the invitation moves to Tuesday 07:00, the primary reminder is computed at 06:45 and moved to 07:00 with its quiet-hours flag set, and the follow-up lands at 08:30. The reasoning line still says "same-day recovery". Saved in memory, a due query at 07:05 on Tuesday returns the primary — its status still reading scheduled — and returns it again on a second call.

Three learning promises (the cover)#

  1. The invitation moves — preferred time, continuity, then quiet hours, in that order.
  2. Reminders shift too — each gets its own quiet-hours pass; a flag records the move.
  3. Records, not messages — saved in memory, returned by a query, sent by no caller found.

Three things to remember (the close)#

  1. Read the final time. The reasoning says same day; the timestamp says tomorrow at seven.
  2. A flag is not a removal. A moved reminder stays in the list, marked, and the due query returns it.
  3. Due is not sent. The due query returns records; nothing marks, sends or cancels them.

Bridge. The next chapter follows one interrupted five-minute sitting across four continuity systems, and what is true of it at two minutes and twenty seconds.

Sections#

Three sections of five.

Section Slides
Where the invitation lands the evening, the plan, where the rules are written, the clock rule, continuity
Zones, quiet hours, reminders three wall clocks, the quiet window, Monday-only nights, the second shift, off
Records nobody sends two clocks, the memory store, two queries, a reschedule, the due record

Treatment decisions#

  • Two gated flows became decision trees with two questions each: the clock rule (a preferred time, then the first declared daypart) and the quiet-hours step, whose moved branch is a "try again" outcome, because a quiet time is postponed to the window's end rather than refused.
  • Five comparisons became cards and panels: three executed wall clocks, three overnight weekday cases and three reminder branches as card grids; the two status clocks and the two read queries as compare panels.
  • The continuity table stays a table: four states, four candidate rules, read side by side.
  • The close of the chapter became sequence lanes: the evening case run end to end through the scheduler and its store, six executed messages ending on the same due record returned twice.
  • An independent source check of the draft found eleven wrong or overstated claims — among them that the builder is pure, that a reminder "comes back due" when its stored status still reads scheduled, and that scheduling policy lives in exactly three places — and each was fixed before the first build.
  • No capture. The scheduler has no caller and no surface; the member's notifications page belongs to a separate preference system with its own reminder lane. The chapter's treatments item stays open until the Phase E screenshot programme can show a surface honestly.

What this chapter does not establish#

No application caller, durable store, dispatcher, notification channel or delivery record. No calendar-conflict, recurrence, minimum-spacing or trigger admission — the builder reads none of them. Time-zone results hold for this host's data (ICU 78.2, tzdata 2026a) and should be rechecked when it changes.