The third 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 two ends by producing one work item: the Enrollment flow in Tara has no mapped journey, and the evidence that would close that gap is named. This chapter follows that item — into a record a stranger could act on, through the states that look like progress, and into the decision that has to be made when the evidence runs out and a judgement is needed. It stops at the point where delivery begins, which is chapter four.
Running example. The Enrollment gap, captured as one task and followed to a recorded decision — carried through all twenty-one slides.
Three learning promises (the cover)#
- How to capture it — a record a fresh implementer could act on without the conversation that produced it.
- What its states mean — a lease is not a promise, a merge is not a verification, and an exit is not a deletion.
- Where the reasoning lives — an anchored thread, a decision with its alternatives, and the receipt that it was exported.
Three things to remember (the close)#
- The closure contract is part of the capture. If a stranger cannot say what would close the item, it is not ready, whatever its state says.
- A state is a checkpoint, not an achievement. A completion claim, an observed merge and a verified closure are three different milestones.
- Agreement is not acceptance. A thread settles nothing on its own, an accepted decision ships nothing, and an exported file is not a merged change.
Bridge to chapter four. One item, leased and worked, reported and reviewed, until something other than its holder says it is done.
Sections#
Three sections opened by a section-divider that names all three, so a reader
arriving in the middle can place themselves.
| Section | Slides |
|---|---|
| Capture the work | record, kinds, preparation, edit and relink, the Work board |
| Follow it to delivery | delivery states, exits and reopens, priority, exercise |
| Discuss and decide | thread vs decision, thread walk, draft, acceptance, supersession, export, exercise |
Treatment decisions#
- The ten states are shown on the real board, not in the diagram. The plan
called for the ten-state lifecycle as a
state-machine. Ten states with their transitions cannot be laid out legibly at slide width, so the ten columns are read from the actual Work board capture (capture-callouts,wide), and thestate-machineoneve-cap-work-recoverydraws only the exits and reopen paths. Every box there declares the machine states it stands for, so the drawing can be — and is — checked against the pinned machine. - Two state machines, deliberately. The decision machine on
eve-cap-decision-acceptanceis drawn the same way as the work machine, so the reader reads the second one with the habit the first one taught. It is complete: four transitions, five states, and no arrow from draft to accepted. - The board capture is pannable.
work-full.pngis ten columns wide; thewideimage layout gives it a focusable, scrollable region with a declared reading width, and print takes thework-review.pngcrop instead. - A compare panel, not three cards, for thread against decision. The slide exists because the two are confused for one another; five shared rows put the difference where it can be seen. The conversation — the third thing people mean — is answered inside the rows rather than given a column of its own.
- The export is a sequence, not a list. What matters is the order: the
eligibility refusal happens before any file exists, and the ledger write is
what makes the receipt meaningful.
sequence-lanesis the only treatment that keeps that order visible. - Both exercises keep their shape. The delivery exercise is ordered in time,
so it is a
step-journeyrather than the plan's card grid. The decision exercise is four independent attempts, so it is a card grid.
What was rebound#
content/61-eve-discussions-decisions.jsonmerged intocontent/60-eve-work-tracking.json; every slide id kept.catalog-source.json: one entry for the guide, with all twenty-one slides in reading order and a summary written from the new chapter.authoring/eve-capability-guides.json: the two entries for this guide became one, with the merged manuscript and all twenty-one slides.authoring/eve-capability-teaching.json: eight assignments carry the rewritten slides' titles; every boundary was re-read and still holds.- Tests bound to the old layouts were rebound: the gated-flow contract to
eve-cap-verification-outcomes, the relation-direction contract toeve-cap-studio-tara-evidence, and the recovery contract to the new state machine's declared states and transition names. A new test holds the preparation decision tree to both its questions and all three outcomes.