# Chapter 2 · Platform map and reading routes · brief · 10 September 2026

The second chapter of the _Start here_ 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 [start-here-track.md](start-here-track.md). The receipt is under
`verification/`.

## The job

Chapter one placed the products. This chapter fixes the vocabulary the rest of
the library assumes — four names, three releases, four kinds of evidence — and
then gives the reader an order to take the tracks in.

**Running example.** One Tara practice: a builder prepares it, a review admits
it, and a member eventually starts, interrupts and returns to it.

## Three learning promises (the cover)

1. **Four names, four responsibilities** — Oshun Synthetics, Oshun, Lilith and
   Eve, and the audience each of them is addressed to.
2. **Three releases, one line** — what V1.0, V1.1 and V1.2 admit, and why code
   in the repository is not a member capability.
3. **Where to start, and what next** — the ownership map, the four kinds of
   evidence, and the order to read the tracks in.

## Three things to remember (the close)

1. **A name tells you an audience.** Members meet Lilith; builders work with
   Eve; the platform stays Oshun in the code.
2. **A release tells you a scope.** Code in the tree tells you nothing about
   what a member can reach.
3. **The map is about accountability, not traffic.** When a diagram and a
   request path disagree, the request path is the fact.

**Bridge.** Whichever track the reader's question belongs to — starting with the
Eve course if it is a question about authority.

## Sections

Two sections, opened by a `section-divider` that names both.

| Section                         | Slides                                                                         |
| ------------------------------- | ------------------------------------------------------------------------------ |
| Who is who, and what ships when | choosing a guide, the four names, the release line, the four kinds of evidence |
| How it fits, and where to start | the ownership map, the journey twice, the boundary check, the reading order    |

## Treatment decisions

- **The release table became a timeline**, and its fourth point sits outside the
  sequence deliberately: the deferred code is in the tree during all three
  stages, which is the thing the table could not say.
- **The evidence table became a compare panel.** Every row on the left is real
  evidence about something; the failure is answering the question on the right
  with it. That is a two-sided claim, and a table flattened it into a lookup.
- **A third legacy `graph` retired.** `map-of-the-platform` becomes a five-band
  layer stack, leaving fifteen overrides.
- **The reading route is now a track order, not an audience list.** The
  inherited slide listed four audiences; the rewritten one gives the order the
  tracks are meant to be read in and says what a reader can do after each —
  which stays true as the remaining eleven V1 tracks are declared.

## What the library needed

No layer stack had ever used five bands, and five overflowed at both 1440×900
and 1280×720. Rather than dropping one of the platform's own layers, bands now
compact at counts of five and six, in the same short-screen block that already
compacted four. The three- and four-band stacks elsewhere are untouched.
