# Account, preferences and personal controls · V1 completion package

## Purpose and source boundary

A dedicated guide follows a member who turns push off, from the account editor
through the write and its readback. Seventeen slides when this package was
written; rewritten on 10 September 2026 as _Meet Lilith_ chapter two, where the
same teaching runs across twenty-four. It covers the hub's control families,
payloads, save and refresh behavior, avatar storage, memory, voice, safety,
notifications, Telegram, data rights, connections and billing.
Product/design/engineering readers should first read Lilith web and PWA. The
canonical home is Products → Oshun V1 → V1.0 → Member experience.

Implementation baseline: `ea93aa4add`. Primary source snapshot:
`1ceae52c7896a59ac74a4429d410f3218f0b91c6`. The account feature, cited profile
code and account walkthroughs are byte-identical between those revisions. The
complete 133-line account feature has seven meaningful inventory units. The
assignment file binds their reviewed explanations, including the reading map, to
expanded slide fingerprints. It does not claim complete review of every
supporting feature or walkthrough page. The full V1 program remains active in
[v1-completion.md](v1-completion.md).

## Composition and sequence

Visual thesis: a calm paper field guide, with readable ink typography and
terracotta reserved for an actual owner, decision or relationship. Native
selectable diagrams expose data ownership and branches. Source field specimens
show real field names without fabricated member records.

Content plan: introduce a concrete preference change; locate its editor and the
hub's broader controls; inspect payloads and persistence; explain refresh and
avatar failure paths; visit specialist journeys; return to the original change
with a reproducible acceptance task. Each slide has a distinct job, three
explanatory paragraphs and three review questions.

Interaction thesis: retain source disclosure, reduced-motion-aware navigation
and workspace transitions. The complete explanation survives in static PDF and
mobile reading order. No new shared animation or renderer behavior is required.

| Slides                         | Job and visual choice                                                                                   |
| ------------------------------ | ------------------------------------------------------------------------------------------------------- |
| `account-first-change`         | Open with a concrete push-off request and three pieces of evidence.                                     |
| `account-surface-map`          | Compare hub, readback and specialist surfaces using purpose and action-location columns.                |
| `account-control-families`     | Show four useful families connected to the hub with verbs that agree with arrow direction.              |
| `account-profile-record`       | Expose identity, projected account state, activity and response context as one field specimen.          |
| `account-preference-groups`    | Give all six groups their own table row and qualify consent, transport and release scope.               |
| `account-durable-save`         | Follow the write through client, BFF and state store; emphasize the store that awaits persistence.      |
| `account-refresh-race`         | Branch on local mutation-generation change and preserve both discard and apply outcomes.                |
| `account-avatar-storage`       | Work through an old-object cleanup failure after new metadata has committed.                            |
| `account-memory-controls`      | Compare controls by where they act and what their results establish.                                    |
| `account-voice-readback`       | Connect registry, consent, selection and provenance to the voice readback.                              |
| `account-safety-record`        | Separate a real server record from locally retained recovery choices.                                   |
| `account-notification-handoff` | Follow the index-to-editor journey, preference write and subsequent summary read; emphasize the editor. |
| `account-telegram-link`        | Branch on issued-link expiry, including refreshing the nonce.                                           |
| `account-data-rights`          | Compare consent, export, scheduled deletion and completed effects as different records.                 |
| `account-deletion-record`      | Capture the shipped danger zone over one scheduled request and number four parts of it.                 |
| `account-connected-services`   | Interpret actual OAuth and binding projections, including verification pending.                         |
| `account-billing-handoff`      | Follow a request for an invoice through the directory and issued-invoice requirement.                   |
| `account-return-check`         | Revisit the push preference after success, unavailable write and cached return.                         |

The guide used the field-guide edition with no repeated masthead when this
package was written, and the Eve edition since the chapter-two rewrite; neither
repeats the masthead. Comparison rows remain peers. The two owner accents have
explicit purposes and occur in different columns. No ordinal position creates
emphasis. Draft optical review caught incorrect incoming verbs in the
control-family map; the final verbs describe controls being edited or summarized
through the hub.

## Source reconciliation

The account feature describes revision counters as supporting concurrent-edit
detection. The actual client adapters discard `revision` and `generatedAt`, and
the PATCH bodies carry no expected revision. The provider instead uses a local
mutation-generation guard to discard an older refresh after a successful local
save. The guide teaches that implemented mechanism and its cross-device limit.

The BFF profile routes authenticate and parse public fields. The profile state
store and its durability tests establish candidate-persist-publish ordering,
shared revisions, deletion fences and failure preservation. A required but
unbound snapshot store fails; non-required configurations may be memory-only.
Public writes accept name/email; internal plan and verification mutation do not
make those fields customer-writable. Persistence failure is 503; a deleted
subject write is 409. No live deployment binding is certified by this review.

The avatar uploader allows at most 1,500,000 decoded bytes and a 3,000,000-byte
route body. Validation of content type and base64 is distinct from decoding an
image. Object bytes precede metadata; obsolete-key cleanup follows it. A cleanup
error can therefore occur after the new metadata is committed. Tracked keys
remain discoverable for later cleanup/deletion, and an object-backed record
cannot lose them through an unavailable-store inline fallback.

The account walkthroughs refine broad route descriptions: notification and data
indexes are readbacks with explicit editor links; the voice catalogue is read
only, selection belongs to the persona picker, and preview URLs are currently
null. The billing index is a rail directory, despite its broader metadata.
Missing or invalid crypto invoice input shows pending issuance. V1.0 remains
crypto-only; preferred-domain values do not open the V1.2 rooms.

The memory walkthrough distinguishes server-backed pause, single-fact deletion
and export receipts from local edits, opt-outs, scope changes and broader
clears. Local full-clear grace is separate from account deletion; attaching a
DSAR ID to a local bundle does not fulfill the server request.
Safety-frame/report reads are real, while recovery choices remain local and do
not close operator frames. Telegram requires an unexpired account nonce and bot
confirmation. OAuth and verified-binding summaries describe connection state;
downstream requests have their own evidence. Calendar and cross-device session
integration retain their explicit end-to-end qualifications.

## Review and delivery requirements

Use [the guide review configuration](v1-account-review-config.json) for all
seventeen slides in four standalone and three embedded views, with six enlarged
text cases and deliberate lost-branch, lost-authority and lost-readback
controls. Run the existing build/composition/source/PDF tests, the configured
browser review with accessibility, the focused center navigation/playback/PDF
gate and encoded narration verification. Generate only the seventeen new
recordings; retain all 580 earlier entries and MP3 hashes. Export and inspect
the final PDF, including exact visual-body text and actual-size pages. Shared
playback/CSS remain unchanged, so unrelated guides need continuity checks rather
than another whole-bank playback cycle.

Reader tasks: identify where to turn push off; explain what a successful write
proves; follow the stale-refresh branch; distinguish local memory edits from
server deletion; locate the voice selector; interpret expired Telegram and
scheduled-deletion states. These tasks are prepared for reader review. No human
comprehension session, normal-speed listening session or new live member action
has been performed for this guide. Automated checks and model optical review
must be labeled separately in the delivery receipt.

Recovery: work is isolated on `codex/v1-presentation-completion-20260908`. Stop
only owned supervised processes, preserve valid partial audio and retain failed
reports. Publish the package only when its relevant delivery checks pass, then
continue with offline mechanics and the room feature guides.

The center check uses `--guides member-account-controls --base-revision` with
the full immutable account baseline commit. This mode checks the selected guide
completely and requires every other guide HTML and shared UI file to equal that
commit byte for byte. It records continuity rather than claiming prior guide
acceptance. The existing ordered passing-report mode retains its stricter
cumulative acceptance semantics. This avoids replaying unchanged guides when
historical reports predate a separate published design revision.
