The sixth track of Phase D, and the fourth about the Tara room. Two chapters
about the phone itself: what a native launch actually establishes, and what a
practice needs before it can play with no network at all. The plan is in
EVE-V1-REDESIGN-TODOS.md, Phase D; each chapter has its own brief and its own
receipt under verification/.
Audience#
Somebody who has read the three web-facing Tara tracks and now has to answer a question about a device: why a practice is silent, whether a download is real, and how long it lasts. The earlier tracks asked which records keep a sitting; this one asks what a phone can be shown to have done.
Running example#
Chapter one carries one launch: the evening reset, 720 seconds long, resumed at 344. Executed against the pinned manager and engine with a declared audio-module seam, it emits four manager events and makes five native calls, and ends active at 344 seconds — or, with one native call changed, in error with no player, under a notice that says the audio is ready. Chapter two carries the same practice onto a plane.
Chapter order#
| # | Chapter | Promises |
|---|---|---|
| 1 | Native playback and recovery | Who owns which step of a launch, and what a ready notice actually checked |
| 2 | Offline audio and retention | What a download establishes, what expires it, and what survives a restart |
Chapter two keeps its inherited title until it is rewritten; the name above is what it promises.
Why this track exists#
Everything the earlier tracks taught about a sitting assumed a player that works. This track is where that assumption is inspected. The three parties in a native launch — the screen, the shared session manager and the playback engine — fail in different ways and report differently, and the most common member-facing symptom, silence under a confident notice, is a gap between them rather than a bug in any one of them.
What this track does not do#
It does not run on a device. Every claim in it comes from pinned source and helpers executed on this host with declared seams, so audible sound, decoding, output routing, the silent switch, lock-screen behaviour, background playback and real cache durability all remain owning acceptance work. It also makes no claim about the content network: an address built from an identifier is metadata until something fetches it.