# Offline reading, updates and queued work · Meet Lilith chapter 3 · verification receipt · 10 September 2026

Scope: the third and last chapter of the _Meet Lilith_ track. Twenty inherited
slides became twenty-six: a cover, four section dividers, twenty content slides
and a close, in four sections of five. This chapter closes the track. Amended on
the same day with the chapter's capture, which the first pass left open. The
[brief](../../authoring/offline-continuity-chapter.md) records what the chapter
is for and why each treatment was chosen; the track brief is
[meet-lilith-track.md](../../authoring/meet-lilith-track.md);
[state.json](state.json) holds the exact counts, durations and tool results.

## What was checked

- **Build freshness.** `build-eve-oshun.py --check` passes on the delivered
  tree. The chapter is 26 slides in four sections of five, running 38.0 minutes,
  with no table in it.
- **Four pinned units re-read, not re-pointed.**
  `assignments/v1-offline-continuity.json` binds four units across the feature
  and architecture surface pages to twenty-four pieces of slide evidence. Each
  was read at its pinned revision before its fingerprint moved, and each note
  records the correction the slide makes to its unit.
- **The retry sequence was derived from the policy, not copied.**
  `libs/oshun/offline/src/retry.ts` declares four attempts, a one-second initial
  delay, a factor of two and a thirty-second cap; `queue.ts` increments the
  attempt count, dead-letters at the ceiling, and otherwise schedules
  `initial × factor^(attempts−1)`. So the delays are one, two and four seconds,
  the fourth failure exhausts the budget rather than scheduling an eight-second
  retry, and the cap never applies by default. That is exactly what the timeline
  draws, and it is why the fourth point carries the emphasis.
- **The fallback chain and its status were read from the worker.** `sw.js`
  matches the exact request with `ignoreVary`, then substitutes cached home HTML
  through the marker helper, then returns a minimal document with status 200.
  The state machine's three terminal states are those three, and the emphasis is
  on the one that returns success while proving nothing was found.
- **The freshness rule was tightened after reading the guard.** A missing date
  header skips the age check because the guard requires it to be present; an
  unparseable one enters the guard and loses the comparison. Both now stated
  separately, in the chapter whose subject is being exact about mechanisms.
- **Narration.** All 26 tracks rendered on this host's CPU and verified with
  `--check --ids`; the whole-library check reports no orphan manifest entries.
- **Browser rendering.**
  `eve-edition-review.mjs --guide member-offline-continuity` sweeps all 26
  slides at 1440×900, 1280×720 with audio chrome, 390×844 and in print — 104
  measurements, no spill, no document overflow, no findings. Swept again after
  the warming slide became a capture, with the same result.
- **The chapter's capture.** `assets/offline-continuity/offline-card.png` is
  the shipped `PwaOfflineFallback` card, rendered from its pinned component over
  browser storage seeded with the declared fixture. Forty-four repository files
  — the component, the recent-content helper, the Nisaba offline store, the
  route tables and the design tokens they reach — were read from the pin and
  hashed into `provenance.json`. The shipped readers, not the harness, decided
  what the card lists: the run asserts on what `readNisabaRecentPassages` and
  `buildPwaRecentContentFallback` return, so a wrong storage key or a rejected
  record fails the capture rather than quietly producing an empty card. The four
  callout coordinates are measured from the rendered geometry. Later the same
  day the harness was re-pointed onto the shared pinned bundler, which resolves
  TypeScript path aliases out of the app's own tsconfig chain; the image bytes
  are unchanged.
- **PDF.** 26 pages, exact authored visual text on every one, in order. The
  downloadable `decks/member-offline-continuity.pdf` was still the twenty-page
  pre-rewrite export and is now the delivered one.
- **Suites and lint.** Python 458 passed, 0 failed. Node 444 of 446 — the two
  failures are pre-existing `Cannot find module 'zod'`. Ruff, ESLint and
  Prettier clean.

## What this chapter has to keep correcting

Both pinned units describe a single offline substrate that the web and mobile
surfaces ride on, with retry and sync behaving consistently across both. The
code does not: the service worker implements its own store and fetch loop, and
neither it nor its helper instantiates the reusable queue class. Explaining that
gap is the reason the assignment exists, so every rebinding note says so
explicitly rather than repeating the prose. The manifest carries the same shape
of correction — the pinned unit still names OSHUN and six domain shortcuts
against a current manifest naming Lilith and four.

## What this chapter found

- **A three-row state machine grid needed a corridor.** The fallback chain's
  three terminal states around one initial state put both elbows of two diagonal
  transitions through occupied cells. Rearranged so each diagonal has one clear
  corridor — the fourth time a state-machine grid has needed that in this plan.
- **Two tables were two different shapes.** The cache policy stayed a
  comparison, because six request classes in the order the worker tries them is
  exactly that and the order is the teaching. The retry table became a timeline,
  because "four attempts, three delays" is a sequence with a clock.
- **Both gates had a third outcome**, as in chapter two: a cached response
  served with no provable age, and a reload armed by a sibling tab that saved no
  scroll snapshot in this one.
- **The card's four buttons and the four always-warmed routes are two lists in
  two files, and nothing in the app makes them agree.** The slide tells a reader
  they are the same four, so `test_offline_capture.py` now reads both out of the
  pin and fails if they ever diverge.

## What was not checked

- No human reader session and no listening review at normal speed.
- The narration was rendered on this host's CPU rather than the Apple GPU the
  rest of the library used; only the MP3 bytes differ.
- **The capture is a rendered card, not a device session.** No service worker
  ran in the capture browser, no route was warmed and no cache was inspected;
  the index it lists was seeded, and what the card does with it is the shipped
  code's answer. It was taken under Chromium 148 — the build Playwright pins in
  this repository and the one the browser sweep uses — where the library's
  earlier assets were captured under 152.
- The chapter reads two implementations and neither runs here. No device
  session, no worker lifecycle and no queue drain was executed; every claim is
  read from pinned source.
