Eve library

Chapter 6 · What happens in the moment, and what it costs · brief · 13 September 2026

Guide

Revision 1

On this page

The sixth chapter of the Shared systems track, rewritten in the Eve edition on 13 September 2026. Fifteen inherited slides become a twenty-slide chapter under the psyche-lilith id. It follows the plan in EVE-V1-REDESIGN-TODOS.md; the receipt is under verification/.

The job#

A member is in a live session. Something is being said, something is being streamed back, and every part of it can fail: the provider can stall, the network can thin out, the device can turn out to be unable to render what was asked for, and the member can say something that stops the session being an ordinary conversation at all.

The previous chapter asked what the platform may remember. This one asks what may happen in the moment — and it ends where memory begins, because inside a crisis frame Iris records nothing.

Running example. One live avatar session that degrades and then hits a safety boundary. Executed on this host against the pinned modules: a turn reducer where an approved interruption ends the turn itself, four codified latency targets, an admission rule that never sheds a paying member, a cascade that steps avatar to voice to text, a recovery step that can only offer an upgrade, and a crisis entry that breaks persona, halts synthesis and suspends memory writes at one timestamp.

Three learning promises (the cover)#

  1. Who decides — the server holds the turn, not the two ends of the call.
  2. What degrades first — a fixed cascade, and a shed order that never reaches a paying member.
  3. What safety costs — persona, synthesis and memory writes stop together.

Three things to remember (the close)#

  1. Ask which half. The contract layer is real; the transport and the providers are not built.
  2. Ask what the offer was. Recovery offers an upgrade and waits for confirmation; it performs nothing.
  3. Ask what the catalog lists. Crisis detection matches listed phrases, and a paraphrase comes back safe.

Bridge. The next chapter turns to creation — Isis and the generation path — where the question moves from how an interaction behaves to what the platform will make on a member's behalf.

Sections#

Three sections of five, plus the cover and the close.

Section Slides
What a live session is the two halves, the gap-free stream, the turn, the latency targets, admission and shedding
When it degrades the cascade, the priority ladder, recovery as an offer, the worked turn, the returned-plan failure
What governs it the tone bands, the persona packs, the assistant context, handoffs and the crisis catalog, the member's day

Three sections, not six. Fifteen content slides cannot carry one divider per five to seven slides across six sections without sections of two and three. Three sections of five each is the shape that fits the rule, and each is a real question rather than a bucket.

Treatment decisions#

  • No capture, deliberately. A capture is possible here — apps/psyche/admin ships real page components at the pin — and it is still the wrong thing to show. Those are operator surfaces for the half of the substrate the source itself calls partially built, so a screenshot of a working dashboard would imply a working runtime, which is the one claim this chapter exists to refuse. Every number is executed against the pinned modules instead, and the "at least two diagrams and one real capture" checkbox is left unchecked, as it is for chapters five, seven, eight, nine and eleven and for Iris. The chapter has eleven diagram layouts and one table.
  • One slide is carried. member-day is already Eve edition and belongs to the web PWA chapter, which also lists it. The guide lists it; this chapter authors it nowhere.
  • Two manuscripts retire. content/06-psyche-runtime-detail.json and content/06-lilith-experience.json held nothing but this chapter's slides.
  • Five slides are new: a cover, three section dividers and a close.
  • One table stays. psyche-latency-targets keeps its table because every cell is bound to a pinned export and three of the four metrics configure only a median — the dashes mean not configured, not zero, which a stat panel cannot say. One table in twenty slides.
  • psyche-runtime-fallback keeps its priority ladder. The plan asked for a decision-tree restyle, but its branches are checked exhaustively against the pinned resolver over all sixty-four signal subsets in each mode, and the decision-tree contract requires the tree to open with a question node. Re-roling the conditions would break the binding that makes the check mean anything.
  • psyche-turn-outcomes becomes a compare-panel and psyche-lilith-worked a case-study, both recorded in the receipt.

What this chapter does not establish#

No live transport was used, no speech or avatar provider was called, and no session was run. The turn reducer, latency targets, admission and shed planners, provider backpressure policy, fallback resolver, upgrade planner, Lilith crisis catalog and tone-band enforcement were executed in isolation against declared inputs; the crisis frame, the diagnostics tooling and the persona registry were read at the pin. Every module returns a decision, a plan or an envelope and performs nothing — which the chapter states on its own slides rather than only here.