Eve library

Track · Start here · brief · 10 September 2026

Guide

Revision 1

On this page

The library's front door, and the first track of Phase D. Two chapters, in the order a new reader should meet them. 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 opening this library for the first time, who does not yet know what a V number means, which of fifty-odd guides answers their question, or why two products that look related are not versions of each other.

Running examples#

The two chapters carry different ones, because they teach different things.

Chapter one follows a mystery clue arriving quietly on the Rail. V10 decides whether to show it, V8 had to prove the case was solvable before it was written, and the investigation happens on a third surface again. One clue, three products, three owners — which is exactly the confusion the product map exists to prevent.

Chapter two follows one Tara practice: a builder prepares it, a review admits it, and a member eventually starts, interrupts and returns to it. The clue crosses products, which is chapter one's subject; the practice crosses layers and releases, which is chapter two's.

Chapter order#

# Chapter Promises
1 V1 to V10: the product map What the four words mean, what each product is for, and how to follow one thing across two
2 Platform map and reading routes Four names and their audiences, three releases and their scopes, and the order to read the tracks in

Why this track exists#

Every other track in the library assumes its reader can place a subject. That assumption fails in a specific way: a V number reads as a version, a release reads as a product, and a shared capability reads as somebody's feature. Chapter one fixes those four words before anything else is described, and it is the reason the glossary slide sits third rather than in an appendix.

What this track does not do#

It does not summarise the products. Each chapter-one slide says what a product is for and nothing about how well any of it works: maturity, coverage and release status belong to the guides that own them, and the source review behind this chapter records that boundary explicitly. The portfolio guide's status line still says "Reviewed portfolio overview; detailed expansion in progress", and the README still states that this overview is not comprehensive V2–V10 coverage.