Eve library

Named and scored, not yet drawn · Tara · practise, chapter 5 · verification receipt · 11 September 2026

Guide

Revision 1

On this page

Scope: the fifth and last chapter of the Tara · practise track. Forty-three inherited slides became fifty: a cover, six section dividers, forty-two content slides and a close, in six sections of seven. The two setting tables became one registry, so tara-mentor-night-settings is merged away into tara-mentor-settings. The brief records what the chapter is for and why each treatment was chosen; the track brief is tara-practise-track.md, now listing all five delivered titles; 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,504 slides and 664 sources. The chapter is 50 slides running 71.0 minutes, with four tables, thirteen diagrams and three captures.
  • Evidence. The inherited guide's executed fixture recorded 27 checks on 9 September 2026 against sources that are byte-identical at b418a8d, at the pin 1ceae52 and at HEAD. Re-running pinned-tara-mentor-presence.mjs on this host fails before its first check: it resolves zod from apps/oshun/web, which has no linked copy here. The recorded evidence stands for the claims it covers; the one new claim — that the web player's walk-in score parses, and fails with a grieving mood — was executed directly against the pinned contract.
  • Captures. The three existing component captures became numbered callouts, with every pin placed in empty space beside what it names and checked on the rendered slide.
  • Bindings. assignments/v1-tara-mentor-presence.json keeps twelve units and 49 evidence entries, each with a fresh fingerprint and an explanation re-set to the rewritten slide; the merged night-settings entry is removed. The owning test now expects the fifty-slide chapter and allows an emphasis only when it names one of the slide's own nodes.
  • Browser rendering. eve-edition-review.mjs --guide tara-mentor-presence sweeps all 50 slides at 1440×900, 1280×720 with audio chrome, 390×844 and in print — 200 measurements, no findings, no page errors.
  • Narration. Fifty tracks rendered on this host's CPU and verified with --check --ids; the merged slide's track is pruned, and the library-wide --check verifies every track.
  • PDF. 50 pages, exact authored visual text on every one, in order, and check-pdf.py passes, including its table-header floor on all four tables.
  • 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.

What was fixed#

  • Six-section dividers. The divider validator admits six sections, but at the four-section rhythm six rows ran 80px past the narration chrome at 1440×900 and 47px at 1280×720. deck.css now tightens the rows the reader is not standing in for six-section dividers — at desktop size, and again on 1001px-wide, 800px-tall screens after the existing short-screen rule — while the current row keeps its size and no authored text is hidden. No other chapter has six sections.
  • The running example's request. The inherited score slide showed an already-present request; the web player sends a walk-in, and asks for already-present only under reduced motion. The slide now shows the request as the capture recorded it.
  • Three questions a slide. The inherited guide asked two; each slide now asks three.
  • The bridge to the next track. The close first said Tara · continue opens with "what carries a sit from one room into the next". Reading that chapter's source showed it is about Lilith's crisis policy deciding whether a sit may start at all; the close now says so, and its one narration track was rendered again.

What was not checked#

  • No embodied mentor. The renderer draws a gradient, a moving band and a watermark; no mesh, posture, setting scenery, voice or visemes.
  • No release. Every mentor is drafted; no rehearsal, measurement, signoff or rollback exercise exists, and nothing enforces the release report.
  • No native delivery, deployed service, production signing, analytics consent path or measured disclosure exposure, and no human lineage, cultural, accessibility or listener review.