Eve library

Audio is ready, says the screen · Tara · native and offline, chapter 1 · verification receipt · 12 September 2026

Guide

Revision 1

On this page

Scope: the first chapter of the Tara · native and offline track, and the declaration of that track. Nineteen inherited slides became twenty-six: a cover, four section dividers, a glossary, nineteen content slides and a close. Nothing was merged. The track now carries both of its chapters in the catalog, the reading routes and the position strip. The chapter brief and the track brief record what each is for; state.json holds the exact counts, tool results and findings.

What was checked#

  • Build freshness. build-eve-oshun.py --check passes on the delivered tree: 1,531 slides and 663 sources across 73 guides. The chapter is 26 slides running 30.5 minutes, with six diagrams, one glossary and no table.
  • Executed evidence. The inherited harness, pinned-tara-native-launch.mjs, passes its 9 exact native caller cases on this host. Beyond it, the pinned session manager and playback engine were executed together through a loader that reads each file at the citation pin and compares it byte-for-byte with the working tree, with the native audio module replaced by a declared seam. Eight cases were run: the ordinary launch (four events, five native calls, active at 344 of 720); attaching after the track loaded (no player, session still active); a failing module loader (attach returns false and reports nothing); creation throwing inside track_loaded (load still returns true, the session is already in error, the following play and seek are refused); a track with no address; a rejected seek; a seek past the end, clamped to 720; and the status mapper.
  • An adversarial source check. An independent reviewer checked every claim against the pinned engine, manager, session model, controls and screen, and found twenty-three that were wrong or overstated. Each was verified at the pin and fixed before the first build. The substantial ones: the session is started before the audio library is read, not after; the player is created on the second manager event, not the first; the screen does read the load result, so only the play and seek booleans go unread; a thrown play does not leave a ready screen — it propagates out of the emit, skips the state notification and leaves the launch unfinished with the rendered phase still reading ready; the End control abandons and never completes; the toggle's label follows the session phase; the track helper has three refusals; four steps share the engine's try block, not three; ten of the twelve entries declare their own size; and the card that prints the phases is unmounted whenever the session is terminal — including the error case this chapter is built on.
  • Bindings. No assignment or teaching file binds a tara-native-audio slide, and check-center-coverage.py --check reports no stale bindings.
  • Browser rendering. eve-edition-review.mjs --guide tara-native-audio sweeps all 26 slides at 1440×900, 1280×720 with audio chrome, 390×844 and in print — 104 measurements, no findings, no page errors. The first run found the ownership sequence pushing the narration chrome 2px off a 1280×720 screen; two detail lines moved into the notes.
  • Narration. Twenty-six tracks rendered on this host's CPU, and the library-wide --check verifies all 1,531.
  • PDF. 26 pages, exact authored visual text on every one, in order, and check-pdf.py passes; the chapter has no table.
  • Suites and lint. Python 479 passed, 0 failed. Node 489 of 489. ruff check on the touched tests and Prettier on every touched file are clean. The tracked-chrome count rose to 904, because declaring the track brings both of its chapters into the position strip.

What was not checked#

  • No device. Nothing ran on a phone. Audible sound, decoding, output routing, the silent switch, background continuation, the lock screen and the real cadence behind the 500 ms interval are all owning acceptance work.
  • No capture. The surface is a React Native screen; the pinned capture bundle renders web components only. The chapter's treatments item stays open for Phase E.
  • No network. The track addresses are built from identifiers and never fetched, so nothing here says a file exists on the content network — and the offline cache itself belongs to the next chapter.