# Chapter 10 · Execution and verified results · brief · 10 September 2026

The fourth 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 nine ended with an action admitted. This chapter is about what happens
next: the record the person actually decides on, the service that applies the
effect, and the evidence that says it finished. The mistake it is written
against is treating one affirmative click as the whole of a write.

**Running example.** A builder asks Eve to revise a content brief's
introduction, and not to publish it. Another operator edits the same brief while
the confirmation card is open, and the approval reply is lost.

## Three learning promises (the cover)

1. **A write is several authorities** — intent, confirmation, execution and
   acceptance are separate, and an approval means only what its stored record
   says.
2. **The decision binds a record and a version** — the card is rendered from
   stored truth, and a lost reply is not a failure.
3. **Reported is not verified** — accepted work becomes an artifact through a
   lease, a report and an independent check.

## Three things to remember (the close)

1. **An approval means its persisted operation.** Not the summary printed next
   to it, and not the operation the target has since become.
2. **A lost reply is not a failure.** Recover the authoritative outcome before
   proposing another attempt.
3. **An executor cannot verify itself.** Reported, verified and delivered are
   three separate states with three separate owners.

**Bridge to chapter eleven.** Which model served the turn, what it cost, and
what a quality claim about it is worth.

## Sections

Three sections, opened by a `section-divider` that names all three.

| Section                            | Slides                                                                                                                    |
| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| One request, checked several times | the separate authorities, the checkpoints, the neighbouring request, the tool contract, the client action                 |
| The decision and its record        | the confirmation record, the race, the version it binds, translating a result, the lost reply                             |
| Accepted work becomes an artifact  | intent to artifact, the work ledger, the three roles, the coding harness, the content loop, where work stops, and failure |

## Treatment decisions

- **The chapter has a real capture.** `assets/eve-product/work-exits.png` — the
  Work lens's last two columns — was captured in the September fixture run and
  never used. It shows a parked task with a real card and a rejected column
  reading zero, which is the honest picture of where accepted work stops. It is
  the one added slide; every inherited slide keeps its own.
- **A legacy `graph` retired.** `eve-intent-to-artifact` is one of the
  `diagrams.json` overrides; rewriting it as a graph diagram leaves eighteen.
- **The approval race is told twice, deliberately.** Once as a sequence across
  four lanes, because the point is who does what and in which order; and once as
  a timeline, because the point of the second slide is that the record has a
  version and the clock moved. Neither says what the other says.
- **No table.** Four inherited tables became a card grid, a compare panel, a
  decision tree and a card grid; the outcome vocabulary needed a two-sided
  panel, not a lookup.
