Scope: the first chapter of the Tara · practise track, and the delivery that declares the track. Twenty-one inherited slides became twenty-eight: a cover, four section dividers, twenty-two content slides and a close, in sections of seven, five, five and five. The brief records what the chapter is for and why each treatment was chosen; the track brief is tara-practise-track.md; state.json holds the exact counts, tool results and findings.
What was checked#
- Build freshness.
build-eve-oshun.py --checkpasses on the delivered tree: 1,477 slides and 663 sources. The chapter is 28 slides running 38.7 minutes, with no table in it. - Track setup.
tara-practiseis declared incatalog-source.jsonwith its five chapters, a matching reading route in the same order, andpath = ["Products", "Oshun V1", "Tara · practise"]on each. One prerequisite was added —tara-ritual-sessionsnow depends ontara-web-practice— so every chapter after the first depends on an earlier one of its own track, astest_every_track_has_a_reading_route_in_the_same_orderrequires. The four chapters still in the field-guide edition carry the position strip from today; declaring the whole track at once is what keeps it from renumbering as each one is rewritten. - Every treatment was re-decided. The plan defaulted seven slides to card grids; five of them are card grids here. One became a compare panel, because its rows already asked one question twice of two reads over the same table. One became a capture, because the contrast it teaches — an authored six-line script against five fixed caption lines — has a half that can be shown. The recovery map became the track's first state machine, and the two ownership handoffs became sequence lanes unchanged in substance.
- A glossary.
sit-vocabularydefines the eight terms the chapter borrows across four surfaces, which is the glossary slide this track's D0 setup asks for in chapter one. Two of the eight — completion state and completion method — mean different things in the player and in the canonical insert, and that is the reason the card exists. - Bindings. No assignment file binds a slide in this guide; every
assignments/*.jsonevidence entry was checked by id.test_tara_web_practice.pyguards the asset manifest and the media-path contract rather than any slide, so the rewrite leaves it untouched, and it still passes against all eight images and thirteen capture checks. - Browser rendering.
eve-edition-review.mjs --guide tara-web-practicesweeps all 28 slides at 1440×900, 1280×720 with audio chrome, 390×844 and in print — 112 measurements, no spill, no document overflow, no page errors, no findings. - Narration. Twenty-eight tracks rendered on this host's CPU and verified
with
--check --ids; the library is complete at 1,966.1 minutes with nothing pending. - PDF. 28 pages, exact authored visual text on every one, in order, read
back from the downloadable
decks/tara-web-practice.pdf, andcheck-pdf.pypasses. - Suites and lint. Python 473 passed, 0 failed. Node 489 of 489. Prettier clean on every touched file; no Python or JavaScript changed.
The captures, and where they came from#
Four, all from assets/tara-web-practice/, all pinned at
1ceae52c7896a59ac74a4429d410f3218f0b91c6 and rendered from the actual
component over a declared five-minute fixture with a deliberate ambient 503. Two
of the four had been taken for the original delivery in September and never
used; the product-view slides they replace cited narrower crops of the same
run.
- The course rows, four pins: the first unfinished row, the duration the Begin control computes its minutes from, a done mark that is set membership and nothing more, and a next mark whose link still opens.
- The player, four pins, on the full control surface rather than the 114-pixel transport strip the old slide cited — a banner that narrow has no clear space for a pin beside anything it annotates. The position and the input that sets it, the clamped seek, the three text controls, and the caption chosen by position.
- The authored transcript, three pins: the selected row's own six lines, printed whole with no position selecting any of them, and the generic fallback that stands in when a row has no script.
- The reflection surface, four pins: the partial branch's own copy, text typed after the completion request had already gone, the Saved label produced by a timer, and three room links that carry no payload.
Every pin was placed by scanning the PNG for a centre whose radius is clear of ink, rather than by estimating one from a rendering.
What was fixed#
- The state machine's edge labels were full sentences, and three of them
collided over the one empty cell that two long transitions cross. They are the
source's own transition names now — Begin, Pause, Resume, Ninety idle seconds,
Scrub, End sitting — with the sentence each stands for in the notes, and the
precise source name carried in the
transitionfield the renderer keeps as a data attribute. tara-web-start-receiptcarried supporting detail on three of its four messages and ran 38px past the page at 1280×720. Two details are in the notes now; the one that remains is the header set the request actually sends.- The course-row legend wrapped to three lines a card at 1280×720 and pushed the chrome 20px off screen. The four legend lines are shorter.
What was not checked#
- No live member persistence. The repositories are read and characterised; the database they would write to is not exercised here, and the second-insert failure is an injected one in a source characterisation rather than a rollback experiment.
- No deployed route behaviour. The page and route wrappers are read in source, and the capture harness mounts the component directly with declared callbacks.
- No audible playback. The capture's ambient response is a declared 503, and the chapter says that a prepared media object is not a sound anyone heard.
- No human reader session and no listening review at normal speed.
- No connection between this page and the canonical checkpoint model or the shared audio-session manager. Both are named on the slide where the web player does not use them, and native device work belongs to the V1.1 surface.