# Eve learning sequence · 7 September 2026

The complete course pairs an introduction with its detail. Context and authority
precede execution; evaluation precedes operations; the dated implementation
update ends with a course review. The separate six-guide overview uses the same
introductions in the same conceptual order. Both routes reuse the existing guide
URLs, sources and recordings rather than duplicating the library.

Visual thesis: retain the cream reading surface and restrained ink typography;
make the topic hierarchy and one running example carry the learning sequence.
Content plan: introduce the draft revision, establish context and authority,
follow execution and recovery, evaluate and operate the result, then apply the
whole model to the dated implementation. Interaction thesis: use ordinary route
links, existing topic disclosure and slide transitions; preserve history,
keyboard focus, mobile dismissal and reduced motion.

## Sequence and prerequisites

| Topic                     | Introduction → detail                                                       | Question carried forward                                                                 |
| ------------------------- | --------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| Purpose and invocation    | Charter and architecture → Identity, surfaces and invocation                | Who is asking to revise which brief, through which surface?                              |
| Context and evidence      | Context, memory and grounding → Context, memory and evidence lifecycles     | What may this turn carry, remember and cite?                                             |
| Authority and safety      | Safety, trust and authority → Authority, safety and consequential decisions | What permits a draft revision without permitting publication?                            |
| Execution and recovery    | Governed execution → From request to verified result                        | Which record authorizes the edit, and what if its reply is lost?                         |
| Models and evaluation     | Models, quality and cost → Model selection, evaluation and change control   | Did the complete path meet its behavioral floor at an acceptable cost?                   |
| Operations and change     | Operations and acceptance → Operating and changing Eve safely               | How is that promise maintained during incidents and changes?                             |
| Implementation and review | Current runtime: authority, voice and inspection                            | What does the dated evidence establish, and can the learner reconcile the original task? |

Introductions recommend the preceding introduction. Details recommend their own
introduction. This permits the short route without making omitted detailed
guides into prerequisites. The complete route supplies the richer preparation by
placing each detail immediately after its introduction. Platform orientation
remains available through the preparation link, including from a filtered route.

## Editorial changes

The foundations case moves from slide 10 to slide 3, following the charter and
preceding the four-plane explanation. It now names the running case explicitly:
an operator revises a content brief's introduction without publishing. The other
five introductions place their worked decision immediately after the opening
boundary, then explain the mechanisms and finish with failure/recovery.

Three exact repetitions have one home: the four planes in foundations, and
grants/budgets plus audit/data rights in trust. The later guides apply those
concepts in different decisions. No unique slide is deleted. Each Eve slide is
encountered once in the complete course, while the overview remains shorter.

The old `eve-to-lilith` transition retains its stable identifier and becomes the
final course review. The reader resolves changed access, a competing brief edit
and a lost approval reply, then connects the result to evaluation and operating
ownership. It teaches the architecture contract at the original source pin; the
preceding implementation slides retain their separate later pin. It does not
claim a live execution or introduce new implementation facts.

Five detailed-guide openings now reconnect explicitly to the running brief.
Request execution already starts with that exact case. Guide summaries explain
the handoff to the next subject and are available in Guide details. Seven spoken
tracks change: these five openings, the foundations example and the final
review. Other recordings and the player remain unchanged.

## Review boundaries

The author reviewed order, prerequisites, the early examples, exact repetition,
opening/closing explanations and the final exercise. The seven-section route now
has an explicit progression; this is an editorial judgment, not a recorded
reader-comprehension trial. The existing reader tasks remain useful; the new
course review connects them. Source-unit assignments are retained only where
their exact explanatory slides remain unchanged.

Verification is scoped to catalog/route contracts, current narration, affected
guide rendering and PDFs, and route navigation on desktop, mobile and short
viewports. The unchanged 470-slide player does not require another complete bank
run for this editorial change. Historical receipts describe their original
artifacts and are not relabeled as fresh results.
