Eve library

One note, and who actually reads it · Tara · continue, chapter 5 · verification receipt · 12 September 2026

Guide

Revision 1

On this page

Scope: the fifth and last chapter of the Tara · continue track, and the second planned merge of this programme. Fifty-two inherited slides across two guides become fifty-one: a cover, six section dividers, forty-three content slides and a close. Nine inherited ids merged into a neighbour and are registered in MERGED_AWAY_SLIDES; tara-companions leaves the catalog and its manuscript, deck, PDF and coverage file retire with it. The brief records what the chapter is for, why each slide merged, and why each treatment was chosen; 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,524 slides and 663 sources across 73 guides. The chapter is 51 slides running 58.1 minutes, with five registries, thirteen diagrams and no capture.
  • Executed evidence. Both inherited characterization harnesses pass on this host: pinned-tara-reflection.mjs (11 native owning tests, 43 library owning tests, 19 source and caller cases) and pinned-tara-companions.mjs (29 native and 30 library tests, 19 source cases). Every claim that carries a number was re-executed through a loader that reads each file at the citation pin and compares it byte-for-byte with the working tree: the running example's chips, the append helper, the twelve-hour boundary on both sides, the six-family classifier on five titles, all twenty-four cells of the destination map, and the study branch on three notes.
  • An adversarial source check. An independent reviewer checked every claim against the pinned model, route, components, relationships, helpers and gating, and found sixteen that were wrong or overstated. Each was verified at the pin and fixed before the first build. The substantial ones: five of the six companion memos are handed the member's note and two of them read it (the draft said two were given it); only the Nisaba and Metis relationships have a resolver seam, so Arete and Nyx return literal paths; the Assistant offer neither builds a domain stack nor changes route, and its card shows a handoff count rather than the titles; the pending-reflection flag matters to the continuation branch, not the live one the running example takes; the structured classifier checks a sleep subtype before any transition trigger; and four of the six text vocabularies were missing a word each, one of which (reflection beside reflect) changes which family matches.
  • Bindings. assignments/v1-tara-companions.json was re-reviewed: the two merged slides dropped from its evidence, the remaining six repointed to tara-reflection with fresh fingerprints, explanations and a rationale that describes the merged chapter. check-center-coverage.py --check reports no stale bindings.
  • Browser rendering. eve-edition-review.mjs --guide tara-reflection sweeps all 51 slides at 1440×900, 1280×720 with audio chrome, 390×844 and in print — 204 measurements, no findings, no page errors. The first run found the closing trace pushing the narration chrome 6px off a 1280×720 screen; it reads three boundaries now instead of four.
  • Narration. Fifty-one tracks rendered on this host's CPU, and the nine merged slides' tracks and manifest entries were pruned. The library-wide --check verifies all 1,524 tracks.
  • PDF. 51 pages, exact authored visual text on every one, in order, and check-pdf.py passes, including its table-header floor on all five registries.
  • 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 untouched-record guard in test_composition.py had its sample floor lowered from 50 to 40: promoting this chapter took the remaining field-guide record-anatomy population to 45, which is what that guard's own comment anticipates.

What was not checked#

  • No capture. The surface is the Oshun mobile Tara route, and the pinned capture bundle renders web components only. The chapter's treatments item stays open for Phase E.
  • No device. Nothing here ran on a phone: no keyboard limit, no haptic, no mounted-screen lifecycle, and no evidence about what survives leaving the route.
  • No destination. No passage opened, no habit created, no Iris memory written, no evidence pack resolved and no Metis course entered. A handoff in this chapter means a link with context attached.