# Moved to seven, with nothing to send it · Tara · continue, chapter 3 · verification receipt · 11 September 2026

Scope: the third chapter of the _Tara · continue_ track. Fifteen inherited
slides became twenty: a cover, three section dividers, fifteen content slides
and a close, in three sections of five. Nothing was merged. The
[brief](../../authoring/tara-scheduling-chapter.md) records what the chapter is
for and why each treatment was chosen; [state.json](state.json) holds the exact
counts, tool results and findings.

## What was checked

- **Build freshness.** `build-eve-oshun.py --check` passes on the delivered
  tree: 1,517 slides and 664 sources. The chapter is 20 slides running 26.5
  minutes, with one table and three diagrams, and no capture.
- **Executed evidence.** The inherited characterization harness,
  `pinned-tara-scheduling.test.mjs`, passes all 16 tests on this host, with
  the clocks and randomness pinned. Every stated value was re-executed through
  the same loader: the evening plan and its two reminders, the equality,
  resume, recent-completion and disabled-reminder cases, the four wall clocks,
  the Monday-only nights, and the store and query sequence. The inherited guide
  recorded Node 24.13.1 with time-zone data 2025c; this host runs Node 22.23.1,
  ICU 78.2 and time-zone data 2026a, and every value reproduced.
- **An adversarial source check.** An independent reviewer checked every claim
  in the draft against the scheduler, the operations module, the trigger model
  and the contract, and found eleven that were wrong or overstated. Each was
  verified and fixed before the first build: the builder is not pure; saving
  the same identifier replaces a stored plan; a due reminder's stored status
  still reads scheduled; the upcoming query returns nothing at 07:05; the
  equality case holds only with quiet hours off; and a trigger engine in Tara's
  features package is a fourth place scheduling rules are written, unconnected
  to this builder.
- **Bindings.** No assignment or teaching file binds a `tara-schedule-*` slide,
  and `check-center-coverage.py --check` reports no stale bindings.
- **Browser rendering.** `eve-edition-review.mjs --guide tara-scheduling` sweeps
  all 20 slides at 1440×900, 1280×720 with audio chrome, 390×844 and in print —
  80 measurements, no findings, no page errors. The first run found the storage
  slide's class-name title running 113px past a phone screen; it is now plain
  words, with the class name in the notes.
- **Narration.** Twenty tracks rendered on this host's CPU and verified with
  `--check --ids`, and the library-wide check verifies every track.
- **PDF.** 20 pages, exact authored visual text on every one, in order, and
  `check-pdf.py` passes, including its table-header floor on the one table.
- **Suites and lint.** Python 479 passed, 0 failed. Node 489 of 489. `ruff
  check` on the touched tests and Prettier on every touched file are clean.

## What was not checked

- **No capture.** The ritual scheduler has no application caller and no
  surface; the member's notifications page belongs to a separate preference
  system. The chapter's treatments item stays open for Phase E's "Tara:
  scheduling and reminders".
- **No sender.** No dispatcher, notification channel, durable store or delivery
  record exists for these plans in the pinned source.
- **No policy admission.** Recurrence, calendar conflicts, minimum spacing and
  trigger admission are declared elsewhere and read by nothing here.
