Eve library

Eve operating-state assignment · 2026-09-08

Guide

Revision 1

On this page

This receipt records a complete editorial read of the pinned top-level Eve Operations, Observability, and Maintenance unit and its reviewed assignment to three new eve-operations-detail slides. The sequence classifies operating state, chooses a safe degraded posture, contains incidents and requires end-to-end reconciliation before returning Healthy.

Reviewed boundary#

The assignment binds source revision 1ceae52c7896a59ac74a4429d410f3218f0b91c6, exact lines 1–29, all 166 words, the unit digest, three assembled slide digests, the top-level citation heading and guide membership. The review record retains the exact source unit, five earlier operations assignments and all four meaningful units still open. The learning map explains the missing detail in each open unit.

The unit is integrated on top of published configuration-teaching revision 46ddb7153032eb0e244c32ee08052d1519e42c7a. Each new slide uses the approved field-guide edition and recovery-map composition. The three slides are the sole additions to that 597-slide baseline.

Expanding grouped visual rows yields the source graph's fourteen directed transitions:

  • Entry establishes Healthy; a dependency-quality or telemetry breach moves Healthy to Degraded.
  • Degraded becomes ReadOnly when mutation safety is unproven, Fallback when a measured compatible or deterministic path remains, and Unavailable when no honest safe fallback exists.
  • Tenant-safety, privacy and false-effect signals take Healthy directly to Incident. Blast radius or a confirmed control breach takes Degraded directly to Incident. Incident moves to Contained before restoration.
  • ReadOnly, Fallback and Unavailable have distinct repair conditions for Recovering. Contained also enters Recovering with control and evidence retained.
  • Reconciliation moves Recovering to Healthy when all affected request-path promises agree and back to Degraded when a required check fails.

This assignment establishes complete teaching of the documented state contract. It does not certify a live environment, current alerts, an executed incident, successful recovery, reader comprehension or product acceptance.

Coverage result#

The global report moves from 70 reviewed / 103,256 unassigned to 71 reviewed / 103,255 unassigned, with 10,018 structural units unchanged. The source-scoped result is six reviewed / four unassigned with no errors. The strict global completion gate continues to return 1.

Delivery and evidence#

  • The generated portal contains 61 guides, 600 unique slides, 623 guide-slide instances and 365 cited paths.
  • The affected guide contains 11 slides and remains completely narrated at 986.988 seconds. The three new CPU-rendered tracks total 248.010 seconds and 1,986,375 bytes. Their hashes and individual durations are recorded in review.json. The unrestricted integrity audit decodes and verifies all 600 tracks, totaling 14.94 hours.
  • The complete pinned source inventory matches 9,262 authored sources and 96,443 authored meaningful units; generated material contains 319 sources and 6,883 meaningful units.
  • The full Python and Node presentation suites pass 307 and 291 tests, respectively. Focused source, assignment, graph, design-preservation, PDF, builder, coverage, inventory, formatting and syntax checks also pass.
  • The standalone guide suite passes 12 checks across all 11 slides at desktop, compact and mobile sizes. It covers source/dialog behavior, accessibility, the 11-page PDF and actual narration decode, pause, resume, seek, speed and end transitions.
  • The center smoke suite passes 12 integrated checks across all 61 guides, including search, history, desktop/mobile navigation, drawer focus, audio interruption and runtime stability.
  • The task-specific browser proof opens each new slide at 1280×720 and 390×844. It verifies exact visible routes, complete explanations and source excerpts, accessibility, horizontal fit and actual MP3 playback at ready state 4.
  • The PDF review and visual review retain the inspected PDF pages and desktop/mobile captures. The delivered tagged PDF contains eleven 960×540-point pages and passes the repository checker.

Findings and retests#

The first single-page graph measured 1,019.5625 pixels in a 900-pixel desktop viewport. Splitting it into classification, capability and reconciliation pages preserved the source sequence, but the first recovery page still measured 960.96875 pixels. Shortening only visible labels brought the static layouts within bounds while retaining exact trigger language in the explanations.

The compact active-playback check then measured 725.953125 pixels in its 720-pixel viewport. Moving Incident-to-Contained to the classification page balanced the first and third maps at four rows each. The complete static and playing desktop, compact and mobile guide flow passed after that revision.

The layout-only candidate correctly failed because the new narration did not exist yet. The three tracks were generated on CPU and the complete browser flow was rerun. A first narration render is retained because later visual rebalancing changed the first slide's speech fingerprint; the final render regenerated that track, while the unchanged third track remained current.

The initial focused Python command used a nonexistent top-level test module, a phrase check found source words in the wrong order, the first coverage writer used an unsupported --write flag and one formatter call ran from the wrong directory. Each issue was corrected and the corresponding targeted and full checks passed.

A competing checkout started a large TypeScript build after the narration resource admission check. Available memory fell to about 4.5 GiB, remained above the required 2 GiB stop point and returned above 13 GiB after the other process ended. The serial render remained supervised and completed normally.

Before publication, origin/main added the V1 foundation and account-control deliveries. The operations commit was rebased onto that 597-slide baseline; generated catalog, coverage, index and narration metadata were rebuilt from the combined authored sources. The V2 preservation guard now pins that published baseline and admits exactly these three additional slides. The first integration command also used the wrong import context, and a later attempt used an abbreviated commit ID with an incorrect expansion. Those attempt records are retained; the corrected 53-test integration set and both full suites pass. The combined browser, inventory, narration, PDF and freshness gates were rerun after the rebase.

origin/main then advanced through three computer-use provider commits without changing any presentation-center or presentation-tool path. The commit was rebased again onto the final published parent; the exact preservation set, builder, coverage and focused narration checks were rerun against that parent.

Normal-speed listening remains open. The MP3s are covered by full decode/integrity checks and real browser playback, but this environment does not provide an audio-listening tool, so this receipt makes no listening claim.

Reproduce#

Run broad and browser checks serially after the host resource checks required by AGENTS.md:

sh
CHROME_CHANNEL=chromium \
  OSHUN_DECK_QA_DIR=/tmp/eve-operations-state-guide \
  python3 tools/presentations/run-supervised.py \
  node tools/presentations/tests/eve-oshun-deck.mjs \
  --guide eve-operations-detail

CHROME_CHANNEL=chromium \
  OSHUN_CENTER_QA_DIR=/tmp/eve-operations-state-center \
  python3 tools/presentations/run-supervised.py \
  node tools/presentations/tests/presentation-center.mjs --smoke

CHROME_CHANNEL=chromium \
  node docs/presentations/presentation-center/verification/eve-operations-state-assignment-2026-09-08/export-state-pdf.mjs
CHROME_CHANNEL=chromium \
  node docs/presentations/presentation-center/verification/eve-operations-state-assignment-2026-09-08/verify-state-browser.mjs

/tmp/oshun-presentations-venv.pot9EA/bin/python -m unittest discover \
  -s tools/presentations/tests -p 'test_*.py'
node --test tools/presentations/tests/*.test.mjs
/tmp/oshun-presentations-venv.pot9EA/bin/python \
  tools/presentations/inventory-center.py --check
/tmp/oshun-presentations-venv.pot9EA/bin/python \
  tools/presentations/build-eve-oshun.py --check
python3 tools/presentations/check-center-coverage.py --check
python3 tools/presentations/check-center-coverage.py --require-complete  # exits 1
/tmp/oshun-presentations-venv.pot9EA/bin/python \
  tools/presentations/render-eve-oshun-narration.py --check

The receipt self-verifier rechecks the source and unit pins, exact graph, assignment, slide sequence, generated artifacts, narration, PDF/browser reports, retained evidence hashes, task path boundary, scoped/global counts and live focused gates:

sh
/tmp/oshun-presentations-venv.pot9EA/bin/python \
  docs/presentations/presentation-center/verification/eve-operations-state-assignment-2026-09-08/verify-receipt.py

Four meaningful units in this source and 103,255 units globally remain open. This receipt completes one reviewed unit; it does not close the presentation center's exhaustive teaching backlog.