Eve library

Eve evaluation and release procedure boundary

Guide

Revision 1

On this page

Purpose and scope#

Teach release owners, operators and assistant-product engineers the complete procedure in source unit b04b556baeb22edf9bcbe5c6, exact lines 129–141 of V1/docs/eve/operations-observability-and-maintenance.md. This package adds one page to eve-operations-detail after the existing worked release exercise. The separate related-document navigation unit remains open.

Baseline and source binding#

  • Implementation baseline: 0a6efd8473a7497da0660d04f1953d245eaa2ecd.
  • Inventory/source revision: 1ceae52c7896a59ac74a4429d410f3218f0b91c6.
  • Source file SHA-256: 37e2944ae765de1819a9d4801b58aa3f8a75f6795147b89e2c4694bfc704f6d4.
  • Unit SHA-256: aaa746f9ac1db29d76ac145c1515a8684d0c174faaf6138dd8bb88fd53f5da11.
  • Exact unit shape: lines 129–141, 70 words, no tables or code blocks.
  • Current surface-polish record SHA-256: 682d70ae8952c2972b8c66e2f3cba485d6e13297141ade931dfb61e506ff43b1.
  • Ongoing measured-loop record SHA-256: 93364ba19e44e75b4e8688c80ea9a3e85ce0925c4d61b352dd0e5c687b76ab81.

The pinned operations file and both linked evidence records are byte-identical to their current working copies. The existing eve-detail-release-exercise applies several test classes to a routing example, but it does not visibly name both records or teach their different roles. The new page closes that exact gap without changing the existing worked example.

Editorial partition#

The source order becomes four readable release boundaries:

  1. Changed stage and behavior: narrow unit/integration tests plus the relevant family deck and prompt ratchet.
  2. Affected journey and docs: the affected browser/mobile journey plus Docs Center checks when contracts or behavior changed.
  3. High-risk extension: adversarial, safety, grounded-answer, persistence and release-gate suites.
  4. Evidence lifecycle: Eve Deep Test and Polish records current surface closure; Eve SMX maintenance carries the ongoing measured loop.

The visible middle cell retains every named check. The final cell explains what the evidence contributes without claiming a pass, a live measurement or a future release decision. No row receives positional emphasis.

Delivered contract#

  • One canonical field-guide slide in content/55-eve-operations-detail.json, ordered after the worked release exercise.
  • One reviewed assignment with the exact source-unit and assembled-slide fingerprints.
  • Three notes, three review questions, locally rendered narration and a regenerated complete guide PDF.
  • Updated learning map, coverage report, TODO status, catalog, guide maps, narration artifacts and regression guards.
  • Desktop, compact, mobile, source-dialog, explanation-dialog, accessibility, actual-audio and PDF evidence in the dated receipt.

Acceptance boundary#

Automated acceptance must prove:

  • all standard and high-risk checks remain visibly represented in source order;
  • both linked records remain visible, cited, byte-identical at the pinned revision and assigned to their exact source roles;
  • the slide fingerprint, citation and final guide position match the reviewed assignment;
  • the source-scoped report moves to nine reviewed / one open without errors;
  • the generated library, PDF and narration are complete and fresh;
  • desktop, compact and mobile layouts keep all four rows readable and accessible;
  • the prior 746-slide corpus and narration remain byte-equivalent at the implementation baseline.

This package does not establish a live gate result, current service health, successful release, reader comprehension, normal-speed listening or product acceptance.