The second chapter of the Tara · find a practice track, rewritten in the Eve
edition on 10 September 2026. It follows the plan in EVE-V1-REDESIGN-TODOS.md
and the track brief in
tara-find-a-practice-track.md. The receipt is
under verification/.
The job#
Chapter one ended on a recommendation. This chapter opens what a recommendation turns into: a caller asks the canonical adapter for a practice catalog, the adapter reads a set of recommended sessions, and a constructor turns that set into four arrays of linked domain objects. Nothing else happens — no media is fetched, no row is written, no route is opened.
The failure it teaches against is reading that output as more than it is. The records are well formed and internally linked, and almost every field in them is a declaration rather than a result: an identifier the builder assembled, a route it composed, a licence it defaulted, an accessibility flag it set to true beside an asset reference that is null.
Running example. One recommendation — session sit-42, content breath-42,
five minutes, a box-breathing hint — followed to practice-sit-42 and its
breathing session, and back again on the last content slide.
Three learning promises (the cover)#
- Four arrays, linked by reference — one practice and exactly one content record per recommendation, plus one teacher.
- The builder decides a great deal — subtype, modality, labels, identifiers and routes are chosen by ordered rules.
- A declaration is not a result — rights, accessibility and media references are strings the builder wrote, not things it checked.
Three things to remember (the close)#
- A declaration is not a result.
- A record can disagree with itself — two durations, two cadences and two cycle answers, none of them reconciled.
- One name, two shapes — compatibility is a conversion somebody writes.
Bridge. How search works in this room, and what a result can claim about what it found — chapter three.
Sections#
Four sections, opened by a section-divider that names all four.
| Section | Slides |
|---|---|
| What one recommendation becomes | the case, the four arrays, the producer, the identifiers, the cardinality |
| What the builder decides for you | subtype precedence, the branch, normalization, modality, taxonomy, labels |
| Where two answers disagree | rounding, the contract lookup, cadence models, cycle arithmetic, shapes |
| What a declaration still owes | teacher, rights, accessibility, media references, invariants, the room |
Treatment decisions#
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 actually doing, and most of them are not peers at all:
- 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 in each case a verdict line is the slide's real claim.
- Two became decision trees. The contract's duration lookup is a question with an admitted branch and a branch that raises; the meditation media rules are two questions with three outcomes. Drawing either as three peer cards would have hidden the branch that matters.
- One became a stat panel. The cycle arithmetic is three exact numbers — thirty cycles, a twelve-second phase sum, and the three hundred and sixty seconds those imply against a declared three hundred — and the third number is the one the record does not carry.
- Two became graph diagrams. The four arrays are a containment relationship, and rights propagation is a relationship with something deliberately missing from it: identity and lineage travel from the teacher, and the licence does not.
- Three stayed card grids, where the rows really are peers: the three input cardinality cases, the three accessibility defaults, and the three contract invariants.
tara-catalog-content-branchkept its two outcomes. A gated flow became a decision tree with an admitted and a refused branch and no third: there is no record that is neither, and inventing a retry outcome to fill the shape would have been a lie about the code.
The capture, and why it is what it is#
This 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: the shipped Tara 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, and the slide exists to stop exactly that step. The capture is the one already taken for the practise track, reused rather than re-rendered, and cited with its own manifest.
What the chapter found in the source#
Nothing here is new to the code; all of it is in the pinned modules. What the rewrite added is naming the four disagreements as disagreements rather than as 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 that belongs 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 — the defect chapter one executes — while the domain 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, so the record implies three hundred and sixty seconds where it declares three hundred.