Eve library

Chapter 12 · Operating and changing Eve · brief · 10 September 2026

Guide

Revision 1

On this page

The sixth and last chapter of the How Eve works track, rewritten in the Eve edition on 10 September 2026. It follows the plan agreed on 9 September and recorded in EVE-V1-REDESIGN-TODOS.md. The receipt for the delivery is under verification/; this file records what the chapter is for and why it is shaped this way.

The job#

Chapter eleven ended with a model admitted to a family on current evidence. This chapter is about keeping the whole thing honest while it runs: what state the service is in, what each outage leaves usable, what an incident has to reconcile before it closes, and what a change has to prove before it ships.

The mistake it is written against is reading availability as health. A provider can respond successfully while the wrong family was selected, a source is stale, or a confirmation was never persisted — every one of those is a green endpoint and a broken promise.

Running example. The lost reply from chapter ten, seen from the operator's side: what state the service is in, what is safe to do next, and what proves the path works again.

Three learning promises (the cover)#

  1. Health is a promise, not a process — the operated thing is the journey from an authorized ask to an inspectable result.
  2. Degradation stays honest — each outage leaves something usable and stops claiming something specific, and the two have to agree.
  3. Closure needs reconciliation — an incident closes on end-to-end evidence, and a change ships through the boundary that owns it.

Three things to remember (the close)#

  1. Health is a journey, not a process. A green endpoint answers one question of four.
  2. Degradation owes both halves. What remains usable, and what may no longer be claimed.
  3. Closure is derived from evidence. An incident closes on reconciliation; a charter closes on requirements joined to artifacts that still open.

The track ends here. Not on a finished system, but on the terms under which it could be called finished.

Sections#

Five sections, opened by a section-divider that names all five.

Section Slides
What healthy actually means the promise operated, voice and tours, the posture machine, telemetry bands, one turn record
The health signals response and routing, effects and support, controls and continuity, edge signals and ownership
When a dependency goes the two halves of degradation, the posture decision, three dependency groups, configuration
Incidents and the loop the worked incident, containment, the reconnect timeline, the cadences, the owning boundary
Changing it, and what stays open the release review, release evidence, the reading map, the charter gaps, runtimes, planning, closure

Treatment decisions#

  • Thirty-three inherited slides became twenty-eight, as the plan asked. The three recovery maps became one state machine whose reduced-capability box declares the three postures it stands for; the dependency-health slide, the operations-failure table and the detail change-ownership table folded into the slides that already carried their claims.
  • Five sections, not four. Eight slides between markers would have been the longest unbroken run in the library. Splitting the health-signal inventory into its own section gives 5, 4, 6, 6 and 7.
  • A five-section divider needed a CSS rule. The contract has always allowed up to six sections and nothing had ever 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, because that is the one the divider exists to point at.
  • No five-card grids. Nothing in the library had ever used five cards, and two slides here wanted to. 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.
  • No table, and no capture. The four inherited tables became a compare panel, two card grids and a timeline. assets/eve-product/ holds nothing showing an operating surface, so the treatment checkbox requiring one real capture stays open.