# Chapter 2 · Downloaded, and never ready · brief · 12 September 2026

The second and last chapter of the _Tara · native and offline_ track, rewritten
in the Eve edition on 12 September 2026. It follows the plan in
`EVE-V1-REDESIGN-TODOS.md` and the track brief in
[tara-native-offline-track.md](tara-native-offline-track.md). The receipt is
under `verification/`.

## The job

Chapter one left a launch holding a native player. This one asks what any of it
can do with no network. Tara's mobile cache keeps a short window of recent
meditations: it resolves a session key, picks a quality, asks a download manager
to transfer the track, writes a recent row, and later resolves a playback source
from whatever it finds.

The chapter teaches the three records that answer different questions — a recent
row for display, a manifest entry for state and accounting, and a file on the
device — and then the comparison between them that decides everything. For Tara
audio, that comparison cannot succeed: the expected checksum the cache supplies
is a colon-separated description of the track, and the manager compares it with
a digest of the downloaded file.

**Running example.** The evening reset's standard track, 9,500,000 bytes.
Executed on this host against the pinned cache, manager and budgets, with the
file-transfer port as a declared seam:

- with a port returning a real digest, the comparison fails, the manifest entry
  is **corrupt**, the recent row is **pending**, and playback resolves to the
  remote track;
- with a port that echoes the expected value, the entry is **complete**, the row
  is **ready**, and the resolver returns an offline address.

The second is the shape the Tara cache's own tests use, which is why they pass.

## Three learning promises (the cover)

1. **Three separate records** — a recent row, a manifest entry, a file.
2. **A label, not a hash** — the comparison cannot succeed as written.
3. **Three, for fourteen days** — inside a tier nothing in the app ever sets.

## Three things to remember (the close)

1. **Name the record.** A row, an entry and a file are three things.
2. **Say what was hashed.** A checksum without a representation proves nothing.
3. **Forgetting is not deleting.** Four paths drop an entry; one removes a file.

**Bridge.** The track ends here; the programme moves to the other rooms.

## Sections

Four sections of five to seven.

| Section                        | Slides                                                                       |
| ------------------------------ | ---------------------------------------------------------------------------- |
| Three records, one meditation  | the running example, three owners, three records, the identity, enrollment   |
| The transfer, and the digest   | the transfer, the comparison, presence digests, repair, resolution, an image |
| What is kept, and for how long | a second quality, three rows, fourteen days, the tier table, two sizes       |
| Clearing, settings, storage    | four ways to forget, the preference, in-memory storage, the inspection order |

## Treatment decisions

- **Two decision trees, for the two places the source really branches**:
  enrollment (enabled and keyed, then already complete) and playback resolution
  (exact, then any complete entry).
- **The catalogue of limits is the chapter's one table**, and it lost a row in
  review: Tara's own window is not a tier and does not belong in the same
  columns, and two of the three tiers are unreachable in the shipped app.
- **Everything that is a set of parallel cases is a card grid**; the transfer,
  the repair trace, the two qualities, the retention window and the closing
  inspection stay case studies, because each is a sequence with an outcome.
- **No capture.** The chapter is about a cache and a manifest, and its only
  surface is the mobile storage dashboard, which the pinned capture bundle
  cannot render. The treatments item stays open for Phase E.
- **An independent source check** of the draft found seventeen wrong or
  overstated claims, each verified at the pin and fixed before the first build.
  The largest: the plan tier is a constructor argument that nothing in the app
  ever supplies, so the free tier is the only reachable one, and the method that
  would change it has no caller; each room's cache builds its own download
  manager, so the total is per cache rather than per app; the per-domain cap
  evicts only complete items and never actually refuses; pruning runs on
  hydration as well as after a cache call, so merely resolving a track set
  enforces the window; the echoing test port belongs to the Tara cache's own
  suite rather than the manager's; a variant's offline flag can be synthesized
  from a recent row with no manifest lookup; an `evicted` state is never
  observable because the entry is deleted in the same breath; and a launch with
  no resolvable session key writes no row at all.

## What this chapter does not establish

Nothing touches a device or a network. No file was fetched from the content
network, no platform filesystem was written, and the Expo transfer adapter
itself cannot run on this host — the executed cases use a port that reproduces
its base64 hashing step. Whether a cached file opens in the native player,
survives a restart, or matches the practice a member asked for all remain owning
acceptance work, and the library ships no durable storage implementation for
either the recent list or the manifest.
