# Meet Eve · the operator chat surface · verification receipt · 10 September 2026

Scope: one slide, `eve-meet-reply`, added to _Meet Eve_ after the Explore-lens
capture. It closes the open Phase B item for chapter one — "capture the operator
chat surface (Eve's own conversation UI) and add it as a second capture; today
the chapter shows only the Explorer". The chapter is now eleven slides.
[state.json](state.json) holds the exact counts, durations and tool results.

## What was checked

- **The transcript is the component's output, not markup assembled here.**
  `assets/eve-operator-chat/operator-turn.png` is `AdminAssistantChat` from the
  admin console. The capture typed the request into the composer, pressed send,
  and answered the component's own two `fetch` calls — a session, then a turn
  stream — with the frames declared in the fixture. The stream is written with
  the shipped `ASSISTANT_TURN_EVENTS` constants rather than string literals, so
  a rename breaks the run instead of silently changing what it records, and any
  request the fixture does not declare throws. 585 repository files were read
  from the pin and hashed into `provenance.json`.
- **The card names a real tool, and that tool really needs the card.** Both
  names in the example — `list_work_items` for the read, `create_work_item` for
  the proposed write — are registered workbench tools, and a test reads the
  registry at the pin to confirm it. The registry marks every workbench write
  `mutating`, which makes execution without the confirm bridge refuse rather
  than fall back to a direct write, and the route offers those bindings only to
  a client that declared `action_confirm`. The capture asserts the component
  declared it.
- **The drawer is at the console's own width.** 460px, read out of
  `AdminAssistantPanel.module.css` rather than chosen to suit the slide; a test
  holds that number against the stylesheet. The drawer's own padding around the
  chat is not reproduced, and the receipt says so.
- **The card was captured live, not expired.** The confirmation carries a
  deadline; an absolute instant in the past renders a different card, headed
  "Expired", with both decisions gone. The run sets the deadline relative to
  itself and asserts no expired card is present.
- **Narration.** One track rendered on this host's CPU and verified with
  `--check --ids`; the whole-library check reports 1446 verified tracks.
- **Browser rendering.** `eve-edition-review.mjs --guide eve-meet` sweeps all
  eleven slides at 1440×900, 1280×720 with audio chrome, 390×844 and in print —
  44 measurements, no spill, no document overflow, no findings.
- **PDF.** Eleven pages, exact authored visual text on every one, in order.
  `decks/eve-meet.pdf` refreshed.

## The correction this receipt records

The first capture taken for this slide was the **member assistant**
(`AssistantPanel`), not the operator chat. It rendered correctly and passed its
own verification, and it was still the wrong surface: `eve-cap-surfaces` names
four doors, and the member assistant is a different one — presented as Lilith,
with no confirm bridge at all, because the workbench write tools are offered
only to a builder- or operator-scoped session. A builder's question about
journey coverage, asked in the member panel, is also not a thing that surface
would carry. The slide was re-pointed at `AdminAssistantChat`, and the
member-assistant capture, its harness and its fixture were removed rather than
left in the tree unused.

## What this slide found

- **A capture harness that could only reach shallow components.** Every product
  capture so far was a component with almost no imports, because the shared
  bundler could pin an import only when the specifier was already a repository
  path. `@/lib/...` and `@oshun/...` are not, so both assistant surfaces — 921
  and 585 files deep through path aliases — were out of reach, and three earlier
  chapters recorded "no capture" partly for that reason. `pinned-bundle.mjs`
  reads the app's own tsconfig chain from the same commit, merges its `paths`
  tables the way TypeScript does, and resolves every aliased import against
  them. A relative import inside a pinned file that the commit does not hold is
  now an error rather than a silent read from the working tree.
- **Callouts land on the text they name.** At the width a capture gets on a
  slide, a numbered pin is several percent of the frame; the first two passes
  put pins on top of the sentences the legend was asking the reader to read.
  Every pin is now placed in space the row leaves empty, measured from the
  rendered geometry, and the test fails if two come within nine percent.
- **The transcript is a crop, and the caption says so.** The whole drawer is
  over 1200px tall at its own width. The capture is a consecutive slice from the
  transcript to the end of the decision, with no pixels rearranged; the composer
  and the activity disclosure below it are outside the frame.

## What was not checked

- No human reader session and no listening review at normal speed.
- The capture is a rendered turn, not a live one. No model was called and no BFF
  answered; the reply text and the proposed write are declared fixture.
- Nothing was approved or declined. The card is captured in the state it waits
  in; what a confirmed write does next is chapter four.
- No assignment or teaching binding moved: the new slide teaches no bound source
  unit.
