# Chapter 2 · Account, preferences and personal controls · brief · 10 September 2026

The second chapter of the _Meet Lilith_ track, rewritten in the Eve edition on
10 September 2026. It follows the plan in `EVE-V1-REDESIGN-TODOS.md` and the
track brief in [meet-lilith-track.md](meet-lilith-track.md). The receipt is
under `verification/`.

## The job

The account hub is the one place in Lilith where a member changes the product
rather than uses it — and it is a single composition over identity, preferences,
personalization, memory, consent, safety, data requests, connections, devices
and billing, almost none of which it owns. The failure it teaches against is
reading the hub as one system that either worked or did not.

**Running example.** "Turn push off." One preference change, followed from the
panel that accepts it to the transport that would have to deliver anything at
all — and it never gets there, which is the point.

## Three learning promises (the cover)

1. **One panel, many owners** — where each control lives, and which service has
   to enforce it.
2. **What "saved" costs** — the durable write, the refresh race, and every state
   between a click and a record.
3. **A control is not its effect** — memory, voice, safety and rights controls
   that front somebody else's record.

## Three things to remember (the close)

1. **A saved preference is a saved preference.** Not a verified channel, and not
   a delivered message.
2. **A readback is not an editor**, and an editor is not the owner of what it
   writes.
3. **A local control can be honest and local.** Memory clears, recovery choices
   and cached indexes all are.

**Bridge.** The same account with the connection gone — where the note from
chapter one is still waiting.

## Sections

Four sections, opened by a `section-divider` that names all four.

| Section                            | Slides                                                                        |
| ---------------------------------- | ----------------------------------------------------------------------------- |
| What the panel actually is         | the opening change, readback vs editor, the five families, the profile record |
| Saving, and knowing it saved       | six preference groups, the durable write, the refresh race, the avatar upload |
| Controls that front somebody else  | memory, voice, safety, the notification handoff, the channel link             |
| Rights, connections and the return | data rights, connection labels, billing, the return check                     |

## Treatment decisions

- **Two gates became decision trees with a third outcome each.** The refresh
  race gained the partial read the provider still labels successful, and the
  channel link gained _opened, still unlinked_. Both are the branch a two-way
  gate leaves out, and both are the state most likely to be reported as done.
- **Two handoff diagrams became sequence lanes**, keeping the same
  responsibilities and the same ordered exchanges. On the notification lanes the
  emphasis is the BFF, because every claim on that slide is something the BFF
  returned and no lane on it can deliver a message.
- **The preference table became a compare panel**, not a card grid: six groups
  read across the same two questions — what a member can set, and where that
  choice stops — is a comparison, and the verdict is that none of the six
  reaches an effect on its own.
- **Three evidence comparisons became card grids** whose evidence line keeps the
  reviewed third column: where the action happens, what the result proves, what
  settles it.
- **Five case studies and two record specimens were kept.** The plan asked for
  them to be kept and restyled, and each is the best available treatment of its
  claim: an illustrative member request, an upload failure order, a real safety
  record beside a local choice, a billing handoff, an acceptance check, and two
  field-group specimens. Their prose was rewritten; their compositions were not.

- **The chapter gained its capture on 10 September**, after the rewrite shipped
  without one. `account-deletion-record` is the shipped danger zone of the
  data-rights controls over one scheduled request, and it sits directly after
  the card grid that names the four records, because it is the one of those four
  the account surface can actually show. The fixture is shaped exactly as the
  store writes: `requestDataDeletion` mints the id, sets the status to
  `scheduled` and computes the date as the request plus a thirty-day grace
  period, and the harness asserts that arithmetic back off the rendered record.

## What the re-review needed

`assignments/v1-account-controls.json` binds seven pinned units of the account
feature reference to twenty-one pieces of slide evidence — every slide in the
chapter except the chrome. Each unit was re-read against its rewritten slides
before any fingerprint moved, and each carries a dated note naming what changed
and what did not.

One thing nearly went missing. The _Related_ unit is explained by the closing
paragraph of `account-return-check`, which names Product Surfaces, Iris,
privacy, support, crypto and the walkthrough route evidence. The first draft of
the rewrite replaced that paragraph with a bridge to chapter three; the
assignment would have kept its rationale while the sentence it rests on was
gone. It is restored, and the bridge sits after it.
