# Chapter 1 · The sitting, and what it leaves behind · brief · 11 September 2026

The first chapter of the _Tara · practise_ 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-practise-track.md](tara-practise-track.md). The receipt is
under `verification/`.

## The job

The previous track ended on a candidate form and a teacher. This one opens the
sitting. One page mounts a player over a chosen row; the player owns a local
clock, a local finish and a local reflection draft, and nothing else; and around
it sit two writes and three reads that do not agree with each other as neatly as
the screen suggests.

The chapter exists because the player's screen is the most persuasive surface in
the product and the least load-bearing. It reports completed at eighty per cent
of a position the member can drag. It shows Saved after a three-hundred-
millisecond timer and no request at all. Its completion effect posts and never
inspects `response.ok`. And a later room read can mark the sitting done from a
source row whose duration was zero.

**Running example.** Row two of the twelve-row course — _The breath, observed_,
five minutes — opened, scrubbed to 239 seconds and ended. The player says
partially-completed. The chapter follows that one number until it can say
exactly what was written, what a later read will show, and which of the two is
answering the member's question.

## Three learning promises (the cover)

1. **The clock is editable state**, not measured listening.
2. **Two inserts run in sequence with no transaction**, and the second can fail
   after the first has landed.
3. **A later read answers a different question** from the screen that produced
   it.

## Three things to remember (the close)

1. **A label is not a receipt.** Saved, completed and done each come from a
   different owner, and only one of them involves a request.
2. **Check the response before believing a post.** One of these two helpers
   reads `response.ok` and one does not.
3. **Name the projection.** The room's done set, the canonical completion event
   and the streak are three different reads of the same table.

**Bridge.** Chapter two — Tara ritual sessions and recovery: the contract behind
the words this chapter borrows.

## Sections

Four sections of six, five, five and five.

| Section                              | Slides                                                                                  |
| ------------------------------------ | --------------------------------------------------------------------------------------- |
| Choosing the sitting                 | the case, the course rows, the overlay, two indexes, three feeds, the route             |
| Inside the player                    | the transport, the idle clock, the threshold, two text sources, two audio paths         |
| What starting and finishing write    | the start receipt, three request results, two inserts, the projection, two readbacks    |
| Reflection, return and the next room | the saved label, the offline branch, a fresh mount, two kinds of link, the closing case |

## Treatment decisions

- **Four captures**, all from `assets/tara-web-practice/`, pinned at
  `1ceae52c7896a59ac74a4429d410f3218f0b91c6`: the course rows, the player, the
  authored transcript, and the reflection surface whose Saved label is the
  chapter's sharpest claim. Two of the four — the transcript and the player —
  were taken for the original delivery in September and never used, and the
  `product-view` slides they replace cited smaller crops of the same run.
- **`tara-web-text-access` became a capture rather than a card grid.** The
  contrast it teaches is between an authored six-line script and five fixed
  caption lines, and the script is the half that can be shown.
- **`tara-web-local-transitions` becomes the track's first state machine.** It
  was a recovery map, and it is five states with named transitions between them
  — the only slide in the chapter where the order of the checks inside one tick
  is the whole point. Its labels are the source's own transition names, kept to
  one or two words so five arrows can share one grid without colliding; the
  sentence each one stands for is in the notes.
- **Two ownership handoffs become sequence lanes**, unchanged in substance: the
  start request across component, route and repository, and the two inserts
  inside one repository method.
- **`tara-web-readback-streak` becomes a compare panel**, not a card grid. Its
  rows already asked one question twice, of two reads over the same table.
- **No table.** Nothing in this chapter is a catalog; the numbers that matter
  are boundaries and they belong in the branch that tests them.

## What this chapter does not establish

No live member persistence. The repositories are read and characterised and the
database they would write to is not exercised. No deployed route behaviour: the
page and route wrappers are read in source. No normal-speed listening and no
independent reader acceptance. The shared audio-session manager and the
canonical checkpoint model are named where the web player does not use them, and
native device work belongs to the V1.1 surface.
