Eve library

Chapter 4 · Follow delivery and operator state · brief · 10 September 2026

Guide

Revision 1

On this page

The fourth chapter of the Use Eve 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 three left one work item in review: Add Enrollment journey, with its closure condition written down and a decision recorded behind it. This chapter takes it the rest of the way — to an observed merge, to a verifier's verdict or an honest gap, and to a note a member can read — and then turns around and reads the operator surfaces that decide whether anything should ship at all.

Running example. Add Enrollment journey, in review, followed to a verdict and a release note.

Three learning promises (the cover)#

  1. Who is holding it — a lease is a time-bounded observation of ownership, not evidence that work is happening.
  2. What actually closed it — an observed merge, one machine-checkable condition, and everything neither of them proves.
  3. What the operator sees — queues, incidents, crashes, models, health and gates, each over its own window.

Three things to remember (the close)#

  1. A hold is not progress. A lease says who acquired the item and until when; a completion report only reaches review.
  2. Verified names one condition. A stored, inspectable condition was met in the current artifact — not a test run, not a causal claim, not acceptance.
  3. Every number has a window. Lifetime or rolling, complete or truncated, live or seeded.

Bridge to chapter five. The same discipline, applied to content a member will actually read.

Sections#

Four sections, opened by a section-divider that names all four so a reader arriving in the middle can place themselves.

Section Slides
Hand the work over fleet attention, lease, the agent's brief, the board, the merge observation
Close it honestly artifact rules, verdicts, triage, the manifest comparison, the release note
Read operator state workspace overview, the four queues, incidents, crash groups
Judge readiness the model registry, health windows, release gates, docs and memory

Treatment decisions#

  • One new content slide. eve-cap-delivery-board was added so the chapter has a real capture. It is the Work lens cropped to the four delivery columns, with the Enrollment task sitting in in-review — exactly where chapter three left it. That crop was captured in the September fixture run and is already provenanced, so no new capture was needed.
  • No fleet or health capture. The plan asked for captures of the fleet/attention view and the assistant-health view. Both are admin surfaces with no component in apps/oshun/web/src/components/assistant/, which is the only tree the capture harness mounts; and a capture taken on this host renders under a different Chromium build from every committed asset, which would make the recorded capture environment false. Those two slides are a card grid and a compare panel instead. The capture task stays open in the TODOS with this reason.
  • Two decision trees, for two real gates. The merge observation branches on one configuration flag, and the verifier's four outcomes fall out of two questions. Both were flows or gated flows that hid the branch inside prose.
  • A timeline for the shipped history. The teaching point is that the query range selects ship events while the verification state reported can be later than the range end. Only a timeline shows an event outside the boundary that is still reported.
  • The chapter's one table. The four operator queues return genuinely different field sets, and comparing them exactly is the slide's job. It is the only table in twenty-five slides, and it scrolls horizontally on a narrow screen by design.
  • Three compare panels, deliberately. Triage dispositions, lifetime against the recent window, and a recorded verdict against a remembered note are all two-sided distinctions that readers collapse into one thing.

What was rebound#

  • content/64-eve-operator-analysis.json merged into content/62-eve-delivery-tracking.json; every slide id kept.
  • catalog-source.json and authoring/eve-capability-guides.json: one entry for the guide, with all twenty-five slides in reading order.
  • authoring/eve-capability-teaching.json: seventeen assignments carry the rewritten titles; every boundary was re-read and still holds.
  • The gated-flow contract in test_eve_design moved to eve-cap-studio-transition, because eve-cap-verification-outcomes is now a decision tree.