# Chapter 5 · Named and scored, not yet drawn · brief · 11 September 2026

The fifth and last 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

Chapter four ended on records nothing converts between. Mentor Presence has the
same shape at a larger scale. A synthetic mentor is registered in detail — a
lineage, a voice profile, an avatar pack, permitted settings, arrivals and
postures — a score describes the sit she joins, and pure decision modules say
how she arrives, settles, breathes, rests and parts.

What reaches a member is narrower. The web player's default-off toggle requests
a short looping image; the renderer draws a gradient with a moving luminous band
and a watermark, and the caption beneath it names a seated guide. The release
report lists seventeen blockers for every mentor, and the render goes ahead,
because the players read `authoredPerformances.configured` and never
`releaseGate.ready`. The reducer, the breath driver, the rate helper, the scene
emitter and the disclosure helper have no application caller.

**Running example.** Sela Stillwater at misty lakeside: the web player asks for
a guided walk-in with session, cadence, context and mood all null, sent as a
four-second, forty-eight-frame envelope, and gets back a tonal loop under a
caption naming her — while her default release report says not ready, with
seventeen blockers.

## Three learning promises (the cover)

1. **Registered in detail** — lineage, voice, avatar and permitted choices, all
   drafted.
2. **Decided in pure functions** — arrival, choreography, breath and motion,
   mostly uncalled by a player.
3. **Drawn as a tonal field** — a band of light with a watermark, and a caption
   describing more.

## Three things to remember (the close)

1. **Ask what reaches the pixels.** The caption and registry describe a guide
   the renderer does not draw.
2. **A report is not a gate.** Seventeen blockers per mentor, and the render
   still runs.
3. **A decision needs a caller.** The reducer, breath clock, emitter and helper
   have none yet.

**Bridge.** The next track, _Tara · continue_, opens with the handoff from Tara
to Lilith's crisis policy — whether a sit may start at all.

## Sections

Six sections of seven.

| Section                        | Slides                                                                                          |
| ------------------------------ | ----------------------------------------------------------------------------------------------- |
| What a member is shown         | the sit, the capture, three controls, four layers, three stages, the cast, Sela's entry         |
| The score and its rules        | the web score, one voice, eight settings, four arrivals, the resolver, parse first, posture     |
| Decisions no player makes      | cadence, the phases, behaviour, crisis, the breath clock, playback rate, motion                 |
| Released or not, it renders    | seventeen blockers, two floors, the capability field, five gates, the envelope, inputs, the key |
| What the media carries         | provenance, reduced motion, private media, storage, durability, the ladder, the fallback        |
| Gaps, signals and the boundary | the late opt-out, the native seam, disclosure, two event systems, analytics, direction, the sit |

## Treatment decisions

- **The two setting tables became one registry**, `tara-mentor-settings`, eight
  rows at registry density; `tara-mentor-night-settings` is registered as merged
  away into it and its narration track is pruned. The two halves of one catalog
  were split only because a table used to hold four rows.
- **The three product views became capture callouts** on the existing captures,
  with pins placed in empty space next to what they name. The captures were
  taken at `b418a8d`; the component and the renderer are byte-identical at
  `1ceae52`, which the slides declare.
- **Two state machines**: the choreography phases on explicit completion events,
  and the crisis path from any phase to collapsed to resting.
- **Three layer stacks for three precedence orders**: the arrival resolver's
  reasons, the render function's gates, and the fallback ladder's rungs.
- **Four tables**: the cast, the settings registry, the arrivals and the
  behaviour catalog, each a set of exact values compared across rows.
- **Six sections need a tighter divider.** The divider validator admits six
  sections, but at the four-section rhythm six rows ran 80px past the narration
  chrome at 1440×900 and 47px at 1280×720. `deck.css` now tightens the rows the
  reader is not standing in for six-section dividers at both desktop sizes; no
  other chapter has six.

## Corrections to the inherited guide

- The running example's web request is a **walk-in**, not already-present: the
  recorded request from the component capture shows `arrivalId: "walk-in"`, and
  already-present is what the component asks for only under reduced motion. The
  score slide now shows the request the player sends, which parses, and the
  notes add that the same request with a grieving mood fails validation.
- The motion-review claim that "a high mean does not override a failed axis" is
  stated as the rule it is — `passesThreshold` requires every axis at or above
  0.8 — because the executed failing case also has a mean below 0.8.

## What this chapter does not establish

No embodied mentor: the renderer draws no mesh, posture, setting scenery, voice
or visemes. No release: every mentor is drafted, and no rehearsal, measurement,
signoff or rollback exercise exists. No native delivery: the native component
has no caller in the mobile source. No deployed service, production signing,
analytics consent path or measured disclosure exposure. No human lineage,
cultural, accessibility or listener review.
