# Chapter 4 · Kept in pieces, by different owners · brief · 11 September 2026

The fourth 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](tara-continue-track.md). The receipt is
under `verification/`.

## The job

Chapter three asked when a member is invited back. This one asks what comes back
with them. Tara has five surfaces a member can practise on — the consumer room
and its sitting player, a generic domain route with a second player, the Oshun
mobile app's Tara route, and standalone Tara web and mobile apps — and around
them sit checkpoints, completion records, saved items, downloads, shares,
reflections and haptic breath pacing. Each is kept by a different owner.

The chapter teaches who keeps each part of one interrupted sitting, how far each
claim about it reaches, and which four connections would make the pieces one
thread. It credits what is built — quick reset and sleep really do reach the
audio, and service favourites really are authenticated — and names the missing
seam beside every piece.

**Running example.** A member stops a five-minute sitting at two minutes and
twenty seconds — 140 of 300 seconds — by choosing End sitting. The canonical web
player calls it partially completed. Its completion post carries the duration,
an empty reflection and that state; the route passes on the duration and the
empty reflection, not the state, and the repository writes a receipt and a
canonical row that says completed. The continuation model, executed from the
pinned source, says _47% complete · resume from 2:20_ for an in-progress record
and _Ended early · restart from the beginning_ for the same record marked
abandoned. A standalone Tara app would keep the exact position — in one browser.

## Three learning promises (the cover)

1. **Five surfaces, many owners** — the same sitting is recorded by systems that
   never meet.
2. **Checkpoints that stay home** — an exact resume point survives a reload, in
   one browser.
3. **Saved means different things** — a label, a local store, a file or a
   service row.

## Three things to remember (the close)

1. **Name the owner.** Every retained state needs the record that holds it.
2. **Local is not synced.** A checkpoint in one browser does not reach the next
   device.
3. **Saved needs a readback.** A label is not a record until a later read finds
   it.

**Bridge.** The next chapter carries one observation out of a practice, and
follows the offers from the other rooms that come after it.

## Sections

Six sections of five to seven.

| Section                       | Slides                                                                                                        |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------- |
| Five surfaces, one sitting    | the stop at 2:20, five evidence levels, five surfaces, the room, two web players, the sitting controls        |
| Clock, speed, completion      | three records of time, one speed policy, three thresholds, the completion write, the decision order, a sample |
| Resume, reset, sleep          | a local checkpoint, the phone-to-web test, quick reset, sleep, accessibility, transcripts                     |
| Haptics and saving            | the haptic route, the phone link, six kinds of saved, favourites, the library's seeds, local actions          |
| Files, shares and a note      | a download, shares and journals, the Saved label, failures, Living Scenes                                     |
| What connects, and what would | library families, related guides, where each piece stops, four connections, the trace told truthfully         |

## Treatment decisions

- **Three captures, reused from the practise track's pinned bundle**: the room's
  course rows, the sitting controls and the reflection surface, each with three
  numbered callouts. The component render is identical at the pin, with declared
  sample data.
- **Paths and relationships became diagrams.** The completion write, the
  phone-to-web test, sleep downshift and the favourites split are sequence lanes
  that draw only messages the pinned source sends; the surface map, the library
  families, Living Scenes and the related guides are graph diagrams with the
  subject in focus.
- **Gates became decision trees** where the source asks two questions: quick
  reset's countdown, the haptic route's admission, the unified library's Tara
  batch and the standalone permission check.
- **Where the plan asked for a flow and the source has none, cards.** The three
  records of time never exchange a message, the haptic chain's pieces are
  separate until something calls the phone link, and the failures are separate
  places, so each is a card grid rather than lanes or a state machine that would
  draw transitions nobody makes.
- **The continuation rules are a stack, not a state machine.** The model is a
  function of one record, checked in a fixed order, so the five checks are bands
  and each boundary is what falls through to the next.
- **One registry table** — where each of eight pieces stops, what it reaches and
  its missing seam — read side by side.
- **An independent source check** of the draft found nineteen wrong or
  overstated claims, and each was verified against the pin and fixed before the
  first build: the completion post never carries a reflection (the note box
  appears after it); captions are five generic lines, not the authored script;
  the favourites view on the same route does read service favourites; the haptic
  compiler has a caller and only the phone push does not; the standalone apps
  have their own device vibration pacing; the Oshun mobile route is a fifth
  surface; a below-floor record says _Just started_; the plan fixture is
  labelled a sample for demos; the standalone player also saves on pause, seek
  and close; and the library imports, the journal limit, the premium rule, the
  sleep state's owner, the second browser test and the handbook's wording were
  each corrected.

## What this chapter does not establish

No deployed, cross-device, native-device or human acceptance. The captures are
renderings of pinned components, not a live member's session; the continuation
model was executed from the pinned source, and the haptic route's limits were
read from it, not exercised by a product flow. Nothing here shows a checkpoint
crossing a device, a favourite added from a web button, a reflection read back
after the Saved label, or a pulse on a watch.
