Eve library

Chapter 1 · Audio is ready, says the screen · brief · 12 September 2026

Guide

Revision 1

On this page

The first chapter of the Tara · native and offline track, rewritten in the Eve edition on 12 September 2026, and the chapter that opens the track. It follows the plan in EVE-V1-REDESIGN-TODOS.md and the track brief in tara-native-offline-track.md. The receipt is under verification/.

The job#

The three web-facing Tara tracks all assumed a player that works. This one inspects that assumption on a phone. A native launch has three parties: the domain screen chooses the practice, commands the session and writes the notice; the shared session manager owns which command is legal in which phase and emits an event for each; the playback engine subscribes to those events and calls a native player.

The chapter teaches what each party actually did, and what the member-facing notice checked before it appeared. The answer is: only the screen's own commands. No native status is awaited anywhere on the path, so the notice can be written over a session that is already in error with no player behind it.

Running example. The evening reset — 720 seconds, resumed at its authored position of 344. Executed on this host against the pinned manager and engine with a declared audio-module seam, the launch emits session created, track loaded, playback started and playback seeked; the engine creates a player for the primary address at a 500 ms update interval, publishes lock-screen metadata, plays and seeks; the session ends active at 344 of 720. With one native call changed — a player that cannot be created — the same launch ends in error, with no player, under the words Audio is ready.

Three learning promises (the cover)#

  1. Three owners, one launch — screen, shared manager, native engine.
  2. A window with no player — attachment can miss the event that creates one.
  3. The notice runs ahead — it reports the caller's commands, not the device.

Three things to remember (the close)#

  1. Name the party. Screen, manager and engine fail differently.
  2. Ask for the player. An active session can hold nothing.
  3. Read the phase, not the notice. The screen holds it, even when it stops printing it.

Bridge. The next chapter asks what any of this can do without a network, and how long a downloaded practice stays.

Sections#

Four sections of five to six.

Section Slides
What the screen knows the running example, five words, twelve entries, three markers, two identifiers
Attaching, before anything plays three owners, what attach does, three ways it misses, three refusals, the launch
Play, seek, and the player the course path, the player, four commands, the status mapping, three failures
What the screen says the nested error, four controls, two phases, teardown, the inspection order

Treatment decisions#

  • A glossary opens the track, because this chapter needs five words to be distinct before anything else can be said: manager, engine, track set, marker, handoff intent. Each card names the mistake it prevents rather than a dictionary sense.
  • Two sequences, for the two paths where the order is the finding: the ordinary launch, and the nested error where a failure inside an event beats the call that caused it back to the caller.
  • The refusals are a decision tree, the library and markers stay record anatomies, and everything that is a set of parallel cases — attachment boundaries, the command branches, the failures, the controls, the surface, teardown — is a card grid. There is no table in the chapter.
  • No capture. The surface is a React Native screen and the pinned capture bundle renders web components only. The chapter's treatments item stays open for Phase E's device captures.
  • An independent source check of the draft found twenty-three wrong or overstated claims, each verified at the pin and fixed before the first build. The largest were about order and about who is told: the session is started before the library is read, not after; the player is created on the second event, not the first; the screen does read the load result, and only the play and seek booleans go unread; a thrown play does not leave a ready screen — it leaves the launch unfinished with the rendered phase still reading ready; the End control only ever abandons; the toggle's label follows the session phase; the helper has three refusals, not two; and the card that prints the phase is unmounted exactly when the session is terminal, which is the chapter's central case.

What this chapter does not establish#

Nothing about a device. No audible sound, no decoding, no output routing, no silent-switch behaviour, no background continuation, no lock-screen surface and no timing guarantee behind the 500 ms interval. The addresses are built from identifiers and never fetched, so nothing here says a file exists on the content network. The executed cases prove ordering, refusal and reporting in source, on this host, with the native module replaced by a declared seam.