Eve library

Exact answers nobody asks for · Tara · continue, chapter 2 · verification receipt · 11 September 2026

Guide

Revision 1

On this page

Scope: the second chapter of the Tara · continue track. Twenty-four inherited slides became twenty-eight: a cover, four section dividers, twenty-two content slides and a close. The two event-tag tables folded into a ten-row context registry and the second lineage table into an eight-row lineage registry, so tara-context-event-tags-one, -event-tags-two and tara-context-lineages-two are merged away. The brief records what the chapter is for 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,512 slides and 664 sources. The chapter is 28 slides running 36.4 minutes, with three tables (down from nine), five diagrams and one capture.
  • Executed evidence. The inherited guide's harness, pinned-tara-context-lineage.test.mjs, was re-run on this host: all 14 checks pass, including its direct-symbol search for an application caller (source-report.json). The running example and each new claim were executed against the same modules through a transpile loader — the twelve-minute availability, the fractional minutes between bands, the hour edges, the quiet-hours cases at 21:00, and five lineage resolutions.
  • An adversarial source check. An independent reviewer checked every claim in the draft against the modules, the contract schemas, the room component, its builder and route, and found fourteen that were wrong or overstated. Each was verified and fixed before the first build: Awe-Inspired's buckets match the duration answer and only Night's leave out Standard; a tag needs no signal; the quiet-hours filter reads two caller flags, not one; the persona mode is not the only way to be refused; an unknown primary throws inside the resolver; and the capture's offer is sitting 02 because the fixture finished 01 and 03.
  • Capture. The pinned Tara room's today's-sit crop, taken for Tara · find a practice, carries three new callouts in the empty space its first use had already verified.
  • Bindings. assignments/v1-tara-context-lineage.json keeps three units; the merged slides' three evidence entries are removed (4, 6 and 6 remain), every fingerprint is fresh, each explanation is re-set to its slide, and the rationales are rewritten. The owning test expects the new counts, and check-center-coverage.py --check reports no stale bindings.
  • Browser rendering. eve-edition-review.mjs --guide tara-context-lineage sweeps all 28 slides at 1440×900, 1280×720 with audio chrome, 390×844 and in print — 112 measurements, no findings, no page errors, on the first run.
  • Narration. Twenty-eight tracks rendered on this host's CPU and verified with --check --ids; the three merged slides' tracks are pruned, and the library-wide check verifies every track.
  • PDF. 28 pages, exact authored visual text on every one, in order, and check-pdf.py passes, including its table-header floor on all three 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#

  • Four claims the inherited guide made about the source. The feature duration lookup has the same fractional gaps as the contract (2.5 minutes throws). The context validator does not check that hour bands overlap. The lineage validator does not check disclosure, locale or review date — the contract schema does. And a lineage-bound record's "no cross-lineage" flag refuses nothing: a comparative persona gets the mixed request through.
  • The last containment map. tara-context-three-models was the library's last delivered containment map, and a design test fails loudly when none is left. The validator still accepts the layout, so the test now holds its contract on that slide as last delivered, frozen under tools/presentations/tests/fixtures/retired-layouts/.
  • A stale assignment line. The evidence entry for the second lineage table named Zen, Interfaith and Contemplative Christian records; the catalog has none of them. The entry went with the merge.

What was not checked#

  • No caller. A name search found none of the three helpers called from the application; that supports an unresolved consumer, not proof of absence.
  • No trusted inputs. No local clock, time zone, signal source or quiet-hours owner was exercised; every input is declared.
  • No lineage review. The records' names, texts and disclosures are source data; credentials, rights and cultural acceptance were not reviewed.