Eve library

Tara practice catalog and records · Tara · find a practice, chapter 2 · verification receipt · 11 September 2026

Guide

Revision 1

On this page

Scope: the second chapter of the Tara · find a practice track. Twenty-two inherited slides became twenty-nine: a cover, four section dividers, twenty-three content slides and a close, in sections of five, six, five and seven. The brief records what the chapter is for and why each treatment was chosen; the track brief is tara-find-a-practice-track.md; 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. The chapter is 29 slides running 41.7 minutes, with no table in it.
  • Every treatment was re-decided, not applied. The plan asked for twelve of the twenty-two slides to become card grids, which would have made the chapter one shape repeated twelve times. Each of the twelve was re-read for what its rows are doing. Four became compare panels, because their rows already asked one question twice — two construction paths for a modality, two cadence models, two shapes with the same name — and a verdict is the slide's real claim. Two became decision trees, because a lookup that raises and a pair of conditional media rules are branches rather than peers. One became a stat panel, because the cycle arithmetic is three exact numbers and the third is the one the record does not carry. Two became graph diagrams, because containment and rights propagation are relationships. Three stayed card grids, where the rows really are peers.
  • One treatment was refused. tara-catalog-content-branch became a decision tree with two outcomes and no third. There is no record that is neither breathing nor meditation, and adding a retry outcome to fill the shape would have been a lie about the code.
  • Bindings. No assignment file and no teaching guard binds a slide in this chapter. Every assignments/*.json evidence entry was checked by id against the chapter's twenty-nine slides, and the node suite is green on the rewritten manuscript — which is what would have caught a prose guard like the one the previous chapter had to re-point.
  • Browser rendering. eve-edition-review.mjs --guide tara-practice-catalog sweeps all 29 slides at 1440×900, 1280×720 with audio chrome, 390×844 and in print — 116 measurements, no spill, no document overflow, no page errors, no findings.
  • Narration. Twenty-nine tracks rendered on this host's CPU in batches of six and verified; the library is complete at 1916.0 minutes with nothing pending.
  • PDF. 29 pages, exact authored visual text on every one, in order, read back from the downloadable decks/tara-practice-catalog.pdf.
  • Suites and lint. Python 473 passed, 0 failed. Node 489 of 489. ruff check and Prettier clean on every touched file.

The capture, and why it is a reuse#

The chapter is about a constructor. It has no surface of its own, and giving it one would have been the dishonest way to satisfy the plan's rule. What it has instead is the surface it is most likely to be confused with: assets/tara-web-practice/course-rows.png, the shipped room's sitting list — twelve rows with durations and states, none of which this catalog produced. They come from a curated path declared in the service that serves the room, with the states overlaid from declared completions. A reader who has just spent twenty slides learning what a catalog record contains is one step from assuming that list is a rendering of one.

The image is reused rather than re-rendered. It was taken for the practise track at the same pin this chapter cites, it is recorded in that harness's own manifest, and re-running the harness here would move bytes that two other slides already pin.

What the chapter names that the source already does#

None of the following is new to the code. What the rewrite added is naming the four disagreements as disagreements rather than as four separate facts:

  • The stored duration is rounded to nearest, and the duration band is computed upward from the original input — so a record routinely carries a stored value belonging to the band below the one it declares.
  • The contract's bucket lookup uses literal ranges and raises for a fractional value in a gap, which is the defect chapter one executes, while this builder produces exactly such durations.
  • A breathing record's label can come from an explicit modality while its timing comes from the original pattern, so its name and its numbers describe different practices.
  • The default cycle count is multiplied out of the minutes rather than divided out of the phases stored beside it: thirty cycles of twelve seconds is three hundred and sixty, against a declared three hundred.

What was fixed#

  • The containment graph was four rows tall, ran 49.6px past the page at 1440×900, and printed its two edge labels on top of each other. Hanging each content array off the practices rather than off the result — which is what the code does — made it three rows and separated the labels.
  • test_eve_design held the containment-map parentage contract on tara-catalog-object-family, which this chapter converted. It is re-pointed at tara-search-local-inventory, which still uses the layout.
  • test_composition guarded the untouched field-guide record specimens with a fixed census of more than a hundred; four conversions here took the population to ninety-six. The bar is now a substantial sample of fifty, with a note that the population falls as chapters are promoted.

What was not checked#

  • No human reader session and no listening review at normal speed.
  • Nothing about the recommendation set the catalog is built from. How that set is chosen and ranked is a separate subject with its own chapter.
  • Nothing downstream of construction: no media was resolved, no route was opened, no record was persisted, and no rights or accessibility owner was consulted. That is the chapter's subject rather than a gap in it.