Eve library

Lilith web/PWA · foundation revision · 8 September 2026

Guide

Revision 1

On this page

Purpose and scope#

The eighteen-slide chapter introduces the V1.0 member surface and the evidence needed to confirm a result. It preserves all eleven existing slide IDs and spoken explanations, and adds one concrete opening case. The full V1 audit remains active in v1-completion.md; this foundation does not replace the detailed room, account, offline or design guides still to be reviewed.

Audience: product, design and engineering readers. Prerequisite: the orientation guide. Outcome: follow a member choice to its supported surface, identify the owner of the result and distinguish local status from downstream confirmation.

Source documentation is pinned to 1ceae52c7896a59ac74a4429d410f3218f0b91c6; implementation citations retain their individually declared snapshots. The complete 134-file V1 Markdown set is unchanged at baseline c8b82d6fd87184503a1b0d3dcc40309f632f59cc. That establishes continuity of written sources, not deployed capability. The governing brand and release contract take precedence over older descriptions of six launch rooms.

Design and interaction#

Visual thesis: cream paper, ink, Georgia claims and readable Arial evidence, with terracotta for meaningful relationships. Each diagram explains one boundary, choice or ownership distinction. Preserve specific comparisons and exact source excerpts where those forms serve the teaching.

Content plan: concrete result → independent evidence questions → launch scope and optional visit → shared facilities and release consumers → update contract, account controls and truthful status → maturity comparison → update choice and alternate-entry verification. The final cases apply the opening evidence rule.

Interaction thesis: retain reduced-motion-aware navigation, source disclosure and workspace width transitions. Every explanation remains available in static HTML and PDF; no new animation is needed to explain these relationships.

Delivered manuscript decisions, in reading order#

Slide Job and composition Meaning to preserve
lilith-cover Open the chapter on one note saved offline, and name the three things it will teach. The example is illustrative. Three promises: four questions, one shell with room-owned effects, and what “installed” and “saved” claim.
lilith-meaning Open section one: what a saved message was ever able to mean. The four questions are independent, not sequential. Release membership is a claim about eligibility only.
v1-member-first-result A hypothetical offline note introduces three pieces of evidence: the supported surface, the local acknowledgement and the returned result. The scenario applies only where offline actions are supported. It does not claim that every room queues writes or that a live run succeeded.
v1-web-pwa-boundary Four independent question/evidence pairs become a card grid whose evidence line keeps the reviewed third column. Route, release, capability and outcome answer different questions; the cards are not ordered execution stages, and outcome keeps its emphasis.
lilith-v1-0 Replace the containment map with a real graph diagram, and draw the deferred rooms with no edge at all. Lilith admits Tara, Arete, Nyx and Nisaba in V1.0 web/PWA. Veritas and Metis are V1.2; native and fiat are V1.1.
lilith-vocabulary The track glossary: six terms, each with the misreading it prevents and where it is first used. Availability is not one word. It splits into the four questions, and a sentence that uses it without saying which is usually the sentence hiding the gap.
lilith-shell Open section two: where the claim was made, not what it meant. A facility available to every room is not evidence that any particular room consumes it.
member-shell Four labelled contributions to the shared member shell, drawn as a graph with the shell in focus. Navigation, assistant context, shared controls and recovery state contribute facilities; room owners still implement and confirm operations.
release-enforcement Replace the policy-consumer map with the comparison its own takeaway makes: a deferred room and a deferred payment rail, refused differently. One declared cut, three consumers. Governance and settlement exceptions admit no new purchase and no deferred member room, and an unknown rail fails closed.
member-day Retain the optional journey, the skip path and the labelled return. The three activity choices are optional kinds of visit, not a three-room inventory or a compulsory routine. Return uses library, history and permitted memory.
pwa-install-update Retain the exact annotated service-worker helper. Its true return confirms posting an activation request to a waiting worker. Activation, restored content and server acknowledgement need separate evidence.
pwa-update-notice Capture the shipped update notice on the reading route and number five parts of it. A staged build and a held write are states of this device. Neither control on the card observes activation, a restored reading or a server acknowledgement.
v1-web-pwa-worked Replace the gated flow with a decision tree whose three outcomes are all real: keep reading, updated, and offer it again. Requesting activation and continuing to read are distinct choices. Restoration and server effects are subsequent observations, never claimed results of the helper.
lilith-proof Open section three: where the evidence actually lives when a member looks for it. The surface a member reads is almost never the owner of what it says.
member-account Four control families on one panel, each paired with the owner that has to enforce it. Profile/preferences, Iris, persona/safety and connections/rights supply different state or controls. The panel does not acquire their authority, and a preference write does not prove delivery.
member-design-language Use the explicitly illustrative waiting-to-sync message with its status, usability and localization duties. The specimen is not a production screenshot, a device run or proof of localization. Truthful behaviour is part of design.
room-maturity Replace the table with one card per room: the documented substrate, and the boundary that still needs its own evidence. Eligibility and implementation evidence differ. No readiness score is assigned, and Nisaba carries the emphasis because the running note is saved there.
v1-web-pwa-failure Alternate-entry, exception and downstream-effect rows become a compare panel: the distinction to hold beside the evidence that settles it. Menu visibility, request admission, payment policy and channel delivery have different owning evidence. The menu is not the boundary.
lilith-close Close on three habits and bridge to the account chapter. A local acknowledgement is local; a shared facility is not a wired consumer; release scope is eligibility.

All eighteen slides use the Eve edition without the repeated masthead. Descriptions and diagrams were shortened where rendered text exceeded a desktop slide; no smaller body type was introduced to conceal overflow. The diagrams remain selectable text with complete mobile reading order and static meaning.

Review and remaining depth#

The detailed slide briefs are stored with each canonical slide. The v1-design-changes.json record explains each material intervention. The foundation review configuration includes every guide reusing a changed slide, desktop/embedded/mobile views, enlarged text and deliberate missing-content controls. The final delivery receipt records actual results, exact artifacts and model optical review.

Source review for this foundation reconciles the product/release/surface, account/profile and design-system explanations and their cited contracts. It is not an exhaustive assignment of every V1 source unit. The dedicated account and offline mechanisms, comprehensive room features, workbenches and remaining V1 subjects still require their full teaching review.

Unperformed human reader sessions and normal-speed listening sessions remain unperformed. Automated playback, extraction, fit and accessibility checks do not stand in for reader comprehension or human listening.