Eve library

Chapter 2 · Exact answers nobody asks for · brief · 11 September 2026

Guide

Revision 1

On this page

The second chapter of the Tara · continue track, rewritten in the Eve edition on 11 September 2026. It follows the plan in EVE-V1-REDESIGN-TODOS.md and the track brief in tara-continue-track.md. The receipt is under verification/.

The job#

Chapter one asked whether a practice may start. This one asks what should shape it — how long the member has, what the hour and the day suggest, and which tradition the practice speaks from — and finds three pure helpers that answer exactly. A duration helper turns minutes into candidate bands, a context helper turns a supplied hour and declared signals into tags and filters them by supplied quiet-hours flags, and a lineage resolver decides whether a request that mixes traditions is allowed.

A search found no caller for any of them. The Tara room a member actually opens offers the first sitting on its path that the member has not yet finished, under a kicker that always says twelve minutes, and its data path carries no minutes, hour, signal or lineage.

Running example. Twelve minutes at 21:00, just after an awe event, with quiet hours on; the member asks for Theravada and Yogic material together while the persona is bound to Theravada. Executed: Micro, Short and Standard (whose fifteen-minute default does not fit); Night and Awe-Inspired, both kept through quiet hours; and a refusal that says a comparative persona would be required. The room meanwhile offers its next unfinished sitting under “Today’s sit · 12 min”.

Three learning promises (the cover)#

  1. Minutes become candidates — buckets admitted by their minimum, not a session that fits.
  2. The hour becomes a tag — stored bands and signals, filtered by flags the caller sets.
  3. Lineage becomes permission — the persona mode decides; the record's own flag never refuses.

Three things to remember (the close)#

  1. A candidate is not a fit. Standard admits twelve minutes and defaults to fifteen.
  2. The caller owns the clock. Hour, signals and quiet hours all arrive as inputs.
  3. The room asks none of them. Today's sit is the next unfinished one, under a fixed 12 min.

Bridge. The next chapter moves from what shapes a practice to when a member is invited back: an evening return that quiet hours move to the next morning.

Sections#

Four sections, of six, six, six and four.

Section Slides
Minutes into buckets the evening, three models, five bands, the edges, twelve minutes, the checks
The hour and the signal one tag, ten tags, the day in four bands, signal order, quiet hours, the checks
Lineage and permission eight traditions, one record, the resolver, a declared frame, an unknown one, the check
Three answers, no caller the worked case, three implementations, the room, the room's data path

Treatment decisions#

  • Two catalog instalments became registries. The three context tables — four clock tags and two sets of three event tags — are now one ten-row registry, tara-context-clock-tags, and the two lineage tables one eight-row registry, tara-context-lineages-one. tara-context-event-tags-one, -event-tags-two and tara-context-lineages-two are registered as merged away and their narration tracks pruned. The five-row duration table stays a table, because its exact values are read side by side.
  • The three validator tables became card grids of what each validator checks; the lineage card grid adds the plane it does not check. Two evidence comparisons changed shape as well: the hour edges are a timeline of one local day, and signal order is a compare panel of what the caller sends against what comes back.
  • The room is the chapter's capture. The helpers have no surface. The pinned Tara room's today's-sit crop — taken for Tara · find a practice — shows the offer the product actually makes, and three new callouts say what chose it.
  • The boundary became sequence lanes. The room's real data path — page, BFF route, completion store — carries the member and nothing about their evening.

Corrections to the inherited guide#

  • The feature duration lookup is not gap-free: 2.5, 10.5, 25.5 and 60.5 minutes each throw. The inherited guide kept fractional gaps as a contract-only concern.
  • The context validator checks that hour bands are whole hours and not empty; it does not check overlap, as the inherited guide said.
  • The lineage validator does not check the disclosure label, locale coverage or review date, or that a teacher or text has a name or citation; those checks are the contract schema's.
  • A lineage-bound record's "no cross-lineage" flag does not refuse anything: the same Theravada and Yogic request is allowed from a comparative persona with Theravada as the primary.
  • The assignment's evidence line for the second lineage table named Zen, Interfaith and Contemplative Christian records that the catalog does not have; the entry is removed with the merge.
  • An independent source check of the draft found fourteen overstated or wrong claims — among them that the two context tags' buckets both disagreed with the duration answer, that every tag needs a signal, and that the persona mode is the only gate — and each was fixed before the first build.

What this chapter does not establish#

No application caller of any helper, and no trusted local time, signal source or quiet-hours owner. No concrete duration choice, no rendered disclosure, no source, rights or cultural review of the lineage records, and no claim that the contract schemas and feature modules would agree on every input.