Eve library

Account, preferences and personal controls · Meet Lilith chapter 2 · verification receipt · 10 September 2026

Guide

Revision 1

On this page

Scope: the second chapter of the Meet Lilith track, rewritten in the Eve edition. Seventeen inherited slides became twenty-four: a cover, four section dividers, eighteen content slides and a close. Amended later the same day with the chapter's capture, which the first pass left open — and with the correction of the reason it gave for leaving it. The brief records what the chapter is for and why each treatment was chosen; the track brief is meet-lilith-track.md; state.json holds the exact counts, durations and tool results.

What was checked#

  • Build freshness. build-eve-oshun.py --check passes on the delivered tree. The chapter is 24 slides in four sections of four, four, five and five, running 36.1 minutes, with no table left in it.
  • Seven pinned units re-read, not re-pointed. assignments/v1-account-controls.json binds seven units of the account feature reference to twenty-one pieces of slide evidence — every slide in the chapter except the chrome. Each unit was read at its pinned revision against its rewritten slides before any fingerprint moved, and each carries a dated note naming what changed and what did not.
  • The six preference groups are the source's six. The pinned profile route declares exactly theme, language, notifications, accessibility, assistant and personalization, and returns a validation error for a body with no usable update. The compare panel's six rows are those groups in that order.
  • Narration. All 23 tracks rendered on this host's CPU and verified with --check --ids; the whole-library check reports no orphan manifest entries.
  • Browser rendering. eve-edition-review.mjs --guide member-account-controls sweeps all 23 slides at 1440×900, 1280×720 with audio chrome, 390×844 and in print — 92 measurements, no spill, no document overflow, no findings.
  • PDF. 23 pages, exact authored visual text on every one, in order. The downloadable decks/member-account-controls.pdf was still the seventeen-page pre-rewrite export and is now the delivered one.
  • Suites and lint. Python 458 passed, 0 failed. Node 444 of 446 — the two failures are pre-existing Cannot find module 'zod' from an incomplete node_modules in this worktree. Ruff, ESLint and Prettier clean.

What this chapter found#

  • A rewritten slide can keep an assignment's rationale while losing the sentence it rests on. 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 replaced that paragraph with a bridge to chapter three. Nothing would have failed: the fingerprint would have moved, the test would have passed, and the assignment would have been quietly false. Re-reading the unit rather than the fingerprint is what caught it, and it is now the rule for the rest of the plan.
  • Both gates had a third outcome. The refresh race gained the refresh the provider still labels successful after only one of its two reads returned; the channel link gained opened, still unlinked. Each is the state most likely to be reported as done, and a two-way gate had no room to say so.
  • A six-row compare panel is the library's first. Five was the previous maximum, and the count that has never been rendered is where every layout overflow so far has been found. This one holds: the existing short-screen compaction block carries it at 1280×720 with no findings.

What was not checked#

  • No human reader session and no listening review at normal speed.
  • The narration was rendered on this host's CPU rather than the Apple GPU the rest of the library used; only the MP3 bytes differ.
  • The chapter explains the account hub's own contracts. It does not verify that any substrate behind them — memory, persona, safety, a transport, the rights executor — behaves as its own guide describes.

Amendment · the chapter's capture · same day#

  • The reason the first pass gave was wrong. It recorded that a capture on this host would falsify the environment, because its Chromium is 148 where the committed assets were made under 152. But provenance.json records the browser per capture directory, and no other slide pins these bytes; the offline chapter took its own capture on this same 148 on the same day. The version rule protects a re-run of a harness whose output is already pinned. It never applied to a new surface.
  • The surface. assets/account-controls/deletion-record.png is the shipped danger zone of DataRightsSection, rendered from its pinned component over browser storage seeded with one example request. Fifty-six repository files were read from the pin and hashed. The records are not handed to the component: they are written to oshun.data-rights.store, and the run asserts on what the shipped hydrate, getActiveDeletionRequest and getLatestExportRequest give back, so a wrong storage key or a rejected record fails the capture instead of quietly producing an empty panel.
  • The fixture is shaped like the code's own writes. requestDataDeletion mints deletion_<id>, sets the status to scheduled and computes the date as the request plus a thirty-day grace period; requestDataExport mints export_<id>, marks the request completed at the moment of the click and sets a download URL of oshun://exports/<format>/<id>. Every field in the fixture is one of those shapes, and the harness asserts the thirty days back off the rendered record rather than trusting the number it seeded.
  • Where it sits. Directly after account-data-rights, the card grid that names four records in one lifecycle. The capture is the third of those four — the scheduled deletion — and the emphasised card, the completed effect, is exactly the one this surface cannot show. That is the slide's takeaway.
  • What it found, and did not fix. These controls write their own outcomes. An export request is stored as completed at the moment of the click with an oshun:// download URL that no browser resolves, and an immediate deletion is stored as completed with no executor involved. The panel mounts a server-backed export section directly above this one, so the surface a member sees carries both kinds at once. The slide's Explain paragraph says so; making the local one honest is product work, not a chapter's.
  • One layout finding. The capture slide first carried five callouts and ran 18.6px past its page at 1440×900, pushing the narration chrome off screen: five legend columns wrap their titles where four do not. The crop lost the deletion-history row along with the fifth callout, and the slide clears the chrome at every reviewed viewport.
  • Re-verified after the amendment. build-eve-oshun.py --check clean; the full sweep re-run at all three viewports and in print with no findings; one narration track rendered and verified, taking the chapter to 36.1 minutes; 24 PDF pages read back with exact authored visual text in order, from the re-exported downloadable deck; Python 472 passed, Node 444 of 446 with the two pre-existing zod failures; Ruff, ESLint and Prettier clean.