# Chapter 5 · One note, and who actually reads it · brief · 12 September 2026

The fifth and last chapter of the _Tara · continue_ track, rewritten in the Eve
edition on 12 September 2026, and the merge the track brief planned from the
start: `tara-reflection` keeps the chapter and the twenty-eight slides of
`tara-companions` fold into it. 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 four asked what comes back with a member. This one asks what they leave
behind, and what is offered next. On the Oshun mobile Tara route a finished
practice can open a reflection card — a prompt, three authored starters, a box,
Save and Skip — and beneath it six companion offers: a Nisaba passage, an Arete
next step, a Nyx perspective, a Veritas and Sophia explanation, an Assistant
follow-up and a Metis study path.

The chapter teaches where the note actually lives, what ends the offer to write
one, and what chooses the six offers. The answer to the last is the session's
own words: a fixed classifier over the session id, title, summary, route and
tags. Five of the six offers are handed the member's note and two of them read
it; the one whose helper could turn a note into a study path never receives it.

**Running example.** An evening body scan, ten minutes long, of which the player
measured eight minutes of listening. Executed from the pinned model: the card
reads _10 min listened · Fresh start · Fresh completion_, the prompt is the body
family's _What shifted in your body?_, and the member types one line. Saving it
writes a trimmed, stamped record in the screen's own state and takes the session
off the Continue rail. The same title classifies as a **sleep descent** for the
companions — the words _body scan_ — so the four destination offers are a daily
passage, an Arete balance check, Nyx nightly highlights and a Metis course path
on a calculus seed.

## Three learning promises (the cover)

1. **A note on one screen** — React state keyed by session; no write leaves it.
2. **Twelve hours, then gone** — saving a note takes the session off the rail.
3. **Offers built from words** — the session's text, not the member's note.

## Three things to remember (the close)

1. **Name the holder.** A saved note lives in one screen's state.
2. **Twelve hours, inclusive.** Writing the note ends the offer to write it.
3. **Words choose the offer.** The session's text, not the member's note.

**Bridge.** The next track leaves the room for Tara's native and offline
surfaces.

## Sections

Six sections of seven to nine.

| Section                       | Slides                                                                                       |
| ----------------------------- | -------------------------------------------------------------------------------------------- |
| Getting to the note           | the running example, the gate, three ways in, three records, a course route, chips, families |
| The prompt, and writing it    | five families, four states, the append helper, the limit, Save, Done, where it lives         |
| What the note changes         | the completion effect, two clocks, the window, the rail, the action, identity, one card      |
| Six offers, one session       | the six models, two gates, identity, two classifiers, the six families, attribution, a seam  |
| Where each offer goes         | the destination map, the study branch, the topics, scoring, the digest, context, candidates  |
| The handoff, and what carries | ranking, the link, the prompt, the payload, the guard, access, navigation, the inspection    |

## Merge decisions

Nine inherited slides merged into a neighbour, and each id is registered in
`MERGED_AWAY_SLIDES` with the slide that absorbed it:

- the second prompt slide into the **five-family registry**, and the second text
  slide into the **six-family registry**, so each catalog is read in one place;
- the second topic slide into the **topic registry**;
- Arete, Nyx and the Metis moment map into one **destination table**: six
  moments across four rooms, executed from the pinned relationships, so a reader
  sees the whole handoff map at once instead of three quarters of it;
- Skip and Edit into the **capture state machine**, where they are transitions;
- the Assistant's invocation guard into the **Assistant sequence**, where it is
  the first message;
- the reflection guide's inspection case into the **chapter's closing trace**,
  because a chapter ends once.

`tara-companions` leaves the catalog, and its manuscript, deck, PDF and coverage
file retire with it.

## Treatment decisions

- **Five registries, because five catalogs exist.** The prompt families and
  their fifteen starters, the six text families and their vocabularies, the five
  study topics and their course seeds, the six evidence notes, and the
  destination map: each is a table the reader can check a claim against. Three
  of them replace pairs of instalment slides; the destination table replaces
  four separate maps. Where a column samples a longer list, its heading says so.
- **The capture states became a state machine**, which is what they are: an
  available note that Save and Skip move out of, Edit and Write reflection move
  back, and Done leaves from.
- **Gates became decision trees** where the source asks one or two questions:
  the reflection entry gate, the twelve-hour window, the Continue action, the
  build-and-display gates, the resolver seam, the study branch and the Metis
  entitlement check.
- **Two sequences, for the two paths that really send messages**: Save, from the
  button to the note record and the continuation summary; and the Assistant
  follow-up, from the tap through the invocation guard to the sheet that sends
  the composed prompt as a turn.
- **The prompt priority is a stack, not a tree**, because five ordered checks do
  not fit a two-question flowchart: course context, then three title substrings,
  then the general fallback.
- **An independent source check** of the draft found sixteen wrong or overstated
  claims, each verified at the pin and fixed before the first build. The
  largest: five of the six companion memos are handed the member's note and two
  of them read it — the draft said two were given it; only the Nisaba and Metis
  relationships have a resolver seam at all; the Assistant offer neither builds
  a domain stack nor changes route; its card shows a handoff count, not the
  titles; the pending-reflection flag matters to the continuation branch, not
  the live one; the structured classifier checks a sleep subtype before any
  transition trigger; four of the six text vocabularies were missing a word
  each, and one omission (`reflection` beside `reflect`) was load-bearing.
- **One slide lost a beat to fit.** The closing trace was four boundaries and
  overflowed a 1280×720 screen with audio chrome by six pixels; it is three now,
  with the note and its clock read together.

## What this chapter does not establish

No durable storage, no destination write, and no arrival. The note is real,
trimmed and stamped, and its reach ends at the screen's own state. The six
offers build links with context attached; nothing here shows a passage opened, a
habit created, an Iris memory written, an evidence pack resolved or a Metis
course entered. Mood labels on these cards are classifications of words, not
measurements. Nothing was run on a device.
