# Operating and changing Eve · chapter 12 · verification receipt · 10 September 2026

Scope: the sixth and last chapter of the _How Eve works_ track, rewritten in the
Eve edition — thirty-three slides moved out of three shared manuscripts into
one, five of them merged away, seven chrome slides added, and every binding
re-reviewed. This chapter closes the twelve-chapter Eve course. The
[brief](../../authoring/eve-operations-chapter.md) records what the chapter is
for and why each treatment was chosen; [state.json](state.json) holds the exact
counts, durations and tool results.

## What was checked

- **Build freshness.** `build-eve-oshun.py --check` passes on the delivered
  tree: 1,418 unique slides, 658 sources, 75 guides. The chapter is 35 slides in
  five sections of five, four, six, six and seven, running 49.8 minutes.
- **Every enumerated row survives verbatim.** This chapter's assignments do not
  only pin fingerprints — they assert exact source strings. All of them still
  pass: the nine operational dependency-map rows (now on card kickers, details
  and evidence lines), the thirteen health-signal measures (card details, in
  order), the ten telemetry schema groups and the privacy boundary, the four
  release-evidence lines, the twelve operating-state transition conditions, and
  the nine configuration and change-control phrases.
- **The merged state machine still proves every transition.** Three recovery
  maps became one state machine whose reduced-capability box declares the three
  postures it stands for. The test now expands those declared states and derives
  all fourteen documented transitions — including the entry edge — from the
  single slide, so the merge is checked rather than asserted.
- **Assignments re-reviewed, not re-pointed.** Sixteen claims across eight
  assignment files bind slides this chapter rewrote. Each was read against its
  new slide before the fingerprint moved, and each carries a dated note. The
  operating-state unit now binds one slide instead of three.
- **Narration.** All 35 tracks rendered and verified; the library-wide `--check`
  verifies 1,418 tracks (1,851.3 minutes). The five merged-away slides left
  orphan manifest entries, which the whole-library check rejects; their entries
  and MP3s were removed.
- **Browser rendering.** `eve-edition-review.mjs --guide eve-operations` sweeps
  all 35 slides at 1440×900, 1280×720 with audio chrome, 390×844 and in print
  with no findings.
- **PDF.** All 35 pages pass the exact-text contract.
- **Suites and lint.** Python 457 passed; Node 443 of 445; Ruff clean; Prettier
  clean on everything changed. No JavaScript changed, so ESLint had nothing new
  to read.

## What this chapter found

- **A five-section divider had never been rendered.** The contract has always
  allowed six sections and nothing in the library had used more than four; at
  1280×720 the fifth pushed the narration chrome 35px off screen. Sections the
  reader is not standing in now compact at counts of five and six, and the
  current one keeps its size.
- **No card grid had ever used five cards.** Two slides here wanted to, and both
  overflowed at 1280. Both were wrong as grids anyway: the incident response is
  a five-step journey, and the reading map is a glossary of five contracts with
  the question that sends you to each.
- **A plain-voice rewrite cannot paraphrase a pinned enumeration.** The
  operations assignments assert exact strings, and the first draft of this
  chapter broke eleven of them by rewording. The claims were unchanged, but the
  guarantee those tests exist to give was not — so the enumerations went back
  verbatim and the reader-facing framing was built around them.

## What was not checked

- No human reader session and no listening review at normal speed.
- The narration was rendered on this host's CPU rather than the Apple GPU the
  rest of the library used; only the MP3 bytes differ.
- No capture was taken. `assets/eve-product/` holds nothing showing an operating
  surface, so the treatment checkbox requiring one real capture per chapter
  stays open.
- `test_v2_rollback_session` still fails against its published baseline;
  re-baselining it is a decision for the user.
