Eve is the builder-side assistant (since the 2026-08-04 brand split the
member-visible persona of the same platform is Lilith; Eve is never
member-visible, so every frame here is an operator/builder surface). The
original ten screenshots plus two later closure frames show Eve doing work, not
posing. The promoted set was refreshed and visually re-inspected on 2026-08-29.
Each capture spec checked its live mutations against Postgres when it ran, and
each read answer carries its Consulted: <tool> trace in the pixel. The
provenance table distinguishes durable, replayable evidence from historical
database state that was not retained.
Provenance#
| Frames | Captured | Spec (in apps/oshun/web/e2e-inspect/) |
Verdict |
|---|---|---|---|
| 01, 05, 06, 07 | 2026-08-29 | phase-15-1b-operator-loop.spec.ts |
current isolated build, 1/1 passed, zero findings; mutation and read-back verified in Postgres |
| 08 | 2026-08-29 | phase-15-1c-explorer-item.spec.ts |
current isolated build, 1/1 passed, zero findings; server truth, painted title, and hit target checked |
| 02, 03, 04, 09, 10 | 2026-08-29 | capture-eve-builder-showcase.spec.ts |
current isolated build, 1/1 passed, zero findings |
| 11 | 2026-08-29 | capture-eve-content-walk.spec.ts |
current isolated build, 1/1 passed, zero findings |
| 12 current proof | 2026-08-29 | capture-eve-circle.spec.ts |
self-owned replay, 1/1 passed, zero findings; row and events removed after verification |
| 12 history archive | 2026-08-22 | capture-eve-circle.spec.ts |
immutable screenshot/Git proof retained separately; original ledger unavailable and never described as replayed |
Stack for every frame: admin app on :3020 (frame 08: member web :3010, whose
customer shell hosts the workbench explorer), BFF on :4010, local Postgres as
the witness. Model binding per CLAUDE.md's test rule:
deepseek/deepseek-v4-flash-0731 via OpenRouter.
The frames#
- 01-operator-drawer-context — the Operations Copilot opens context-scoped
before a word is typed: the workspace it is standing in, the operator
identity (
Studio Operator 01), and memory pinned to Session only. - 02-review-queue — "What is in the review queue right now?" answered from
the live queue, not recall: four items, all past SLA; the three highest-risk
rows are named with state, priority, and owner.
Consulted: admin_review_queue. - 03-workspace-overview — the portfolio view names the current urgent
workspaces and their live counts: incidents, privacy, support, moderation,
models, and policy.
Consulted: admin_workspace_overview. - 04-graph-neighborhood — Eve walks
tara.sessionsin the compiled product graph: parent domain, child flow, the routes that visit it.Consulted: get_graph_neighborhood. - 05-work-item-draft-card — asked to log a follow-up for the member audit,
Eve drafts the structured issue (run-specific title, medium priority, graph
ref
tara.sessions) and parks it: "Awaiting your approval … nothing happens until you decide." - 06-work-item-approved — the operator taps Approve and only then does the row exist: "Approved and executed." The spec polled Postgres for the row before this frame was taken.
- 07-work-item-read-back — the read tools see what was just made: state
draft, no lease, "the only event on its ledger is its own creation" — and Eve proposes the next transition.Consulted: list_work_items, get_work_item. - 08-explorer-work-lane — the workbench explorer paints the approved item in the work lane, on top of the compiled graph ("19/19 domains verified · 32/35 flows verified · 729/729 journeys mapped").
- 09-parked-card — the decline arc begins on the FIRST natural ask ("Log a work item…"): the card parks and the reply says so plainly — "nothing is written until you confirm." The spec asserted zero rows at this instant. (Re-shot 2026-08-29 on an isolated current-build stack; the card arrived on the first natural ask.)
- 10-declined-nothing-written — the operator declines and the outcome note
is the point: "Declined — nothing was changed." Asserted in Postgres after
the click. (Re-shot 2026-08-29: the earlier frame opened with Eve calling
this console "read-only" — measured as defect G1 of
EVE_EVERYWHERE_TODOS_2026-08-19.md(a router miss clamped the write tools away) and fixed in its Phase 1; the current frame cards the natural ask directly.)
Why the original ten#
The set was chosen to cover Eve's builder-plane behaviors, one frame each: context-scoped session, live queue triage, portfolio triage, graph literacy, draft-then-park, approve-then-execute, ledger read-back, explorer projection, parked-means-parked, and declined-means-nothing-happened. A first cut of frame 10 caught the card mid-flight ("Working…") and was rejected — a screenshot captioned "declined" is only evidence once the declined state has actually rendered and the absence of the row has been checked.
Frame 11 — the content loop (added 2026-08-21, EVE_EVERYWHERE 5.6)#
- 11-content-loop-promote-card — the content lane end to end in one frame:
Eve lists the ideation lab's real candidates over the Hathor HTTP seam (the
idea's FULL id and capture date in the reply), and the promotion into a
content brief sits PARKED on its confirmation card — "nothing happens until
you decide".
Consulted: list_ideation_candidates, promote_ideation_candidatein the pixel, beside the drawer's newer chrome (voice input, synthetic-voice playback label, curated Tours). Captured bycapture-eve-content-walk.spec.tswalk A on 2026-08-29 — a run that finished 1/1 with zero findings (the promote's Postgres landing asserted by the spec; the status read-back adjudicated grounded via the equivalentget_work_itemledger read; the dispatch leg guarded by the dispatch-claim checker that shipped the same day).
Frame 12 — the full circle (added 2026-08-22, EVE_EVERYWHERE 9.3)#
-
12-full-circle-what-shipped — the loop, anchored to a REAL defect: the 12.1 exit battery found the crisis catalog's bare-"withdrawal" false positive (member-visible — consent-withdrawal conversation was replaced by the critical safety block, reproduced 3/3), and the real fix commit is
87ebda4b8a95bb92eabe07fcdfb830c013c8b1f6. The promoted frame is the 2026-08-29 self-owned regression replay: work itemwi-99c513ff-8e50-49df-88a9-3c9006641073is attributed to the claude-code lane, cites the observed fix SHA and exact shipped-event sequence, and honestly reports the verifier'snot-machine-checkableterminal.Consulted: what_shipped_sinceis visible in the pixel. The same run parked the release-note card, proved it inert before approval, approved it, checked the member-safe feed row, and deleted the fixture row and all events.The completion re-audit on 2026-08-29 found an evidence-retention gap: the historical Postgres row and its event sequence were not committed with the original frame and no longer exist in any local database. Accordingly, the 2026-08-22 screenshot is preserved as
12-full-circle-what-shipped-2026-08-22.png, but its old ledger is not independently replayable and is no longer described as though it were. The immutable anchors that do remain are recorded infull-circle-provenance.json: fix commit87ebda4b8a95bb92eabe07fcdfb830c013c8b1f6, capture commit4d75a3fd988f7311f9177a946a7d6b925a9c5c45, checkbox commitb20d83a563dacb923afe3e36b5a7014f16b0422a, and historical screenshot SHA-256036bd2fa76f4ad199d195d536c3e58c9a70405a870000c16c7e308d07ef70125. The manifest separately records the current proof hash60a404eab7274db3384830cfa3f283840587ae27e438d8d5ce87e94254a50a06. Runnode tools/eve-everywhere/verify-full-circle-provenance.mjsto check both images and the Git ancestry.capture-eve-circle.spec.tsis now a self-owned regression replay anchored to that real fix commit. Every run creates an assistant-attributed finding, leases it toclaude-code, records completion and the observed commit, appends the honest verifier terminal, demands exact id/SHA/ledger-sequence citations fromwhat_shipped_since, proves the publication card is inert before approval, verifies the member-safe feed row, and deletes the row and all events afterward. This keeps the full mechanism reproducible without fabricating replacement provenance for the lost historical ledger.