Eve library

Eve runtime, tools and actions · whole-source review

Guide

Revision 1

On this page

This map records a complete editorial read of the pinned 173-line V1/docs/eve/runtime-tools-and-actions.md. It adds one exact failure/fallback assignment to three existing runtime assignments and keeps six meaningful units open. It does not establish current provider, router, tool, workbench, agent, failure-exercise, reader, listening or product acceptance.

Reviewed assignments#

The earlier eve-opening-boundaries.json file binds Task-family routing, Confirmation bridge, and Client actions and page control. The new eve-runtime-fallback-boundaries.json file binds:

Source unit Guide and slide Complete teaching boundary
f98dc798024dc5df22b8edf4 · Failure and fallback behavior, lines 153–166 eve-request-detail / eve-detail-unknown-outcome Provider unavailability, bounded unknown intent, invalid arguments, stale confirmation, timeout/partial receipt, safety supersession and disconnect recovery without non-idempotent replay.

The slide cites the exact heading and source at inventory revision 1ceae52c7896a59ac74a4429d410f3218f0b91c6. Its deeper lost-reply example does not widen the assignment beyond the complete failure/fallback unit.

Units that remain unassigned#

The source contains ten meaningful units. Four now have reviewed assignments; six remain open:

  • Eve Runtime, Tools, and Actions, lines 1–37: the guides teach the checkpoint concept but do not preserve the complete seven-participant sequence and every alternate-path message as one unit.
  • End-to-end request path, lines 38–61: the detail slide preserves the nine numbered stages, but does not identify the two named owning documents and their customer-scope versus model-selection/escalation roles.
  • Tool layers, lines 80–94: the overview and tool-contract slides cover all six categories in broad terms, but omit table details including the client browser allowlist/current-route/visible-actor boundary and several concrete room and workbench examples.
  • Workbench and content round trips, lines 125–140: the work-ledger slide preserves the complete responsibility sequence, but does not identify the exact workbench catalog path and breadth-tracking record required by the source unit.
  • MCP and coding-agent lane, lines 141–152: the slides explain attribution, lease scope, artifact reports, independent verification and repository rules, but do not teach both exact server/harness paths named by the source.
  • Related, lines 167–173: no slide explains all five linked documents and their roles beside the runtime contract.

No assignment follows from citation or high lexical overlap. Each future assignment must cover its whole unit and pass exact unit, revision, slide, citation, guide and assembled-fingerprint checks.