# Eve operations related-document reading map

## Purpose and scope

Teach operators, release owners and assistant-product engineers how to use all
five links in source unit `155ff62a850acf8fe5ac1eeb`, exact lines 156–162 of
`V1/docs/eve/operations-observability-and-maintenance.md`. This package adds one
closing page to `eve-operations-detail` after the release-evidence page. It
completes the ten meaningful units in this source without claiming that the
presentation center's wider inventory is complete.

## Baseline and source binding

- Implementation baseline: `6c62dfaed8fbdfe5c439e60faae20ab7abcbe228`.
- Inventory/source revision: `1ceae52c7896a59ac74a4429d410f3218f0b91c6`.
- Source file SHA-256:
  `37e2944ae765de1819a9d4801b58aa3f8a75f6795147b89e2c4694bfc704f6d4`.
- Unit SHA-256:
  `30647370520fb8786bba1b30347a07380ed48116c0c81a06bbbf8d00434e5c9a`.
- Exact unit shape: lines 156–162, 26 words, no tables or code blocks.
- Safety, Governance, and Privacy SHA-256:
  `5e51235b32bf5149059aaf0598574584b83e1d24cff23c967a1e571e1c7576fa`.
- Models, Quality, and Evaluation SHA-256:
  `c8d8da74ffcafbc90687d03e786c0b4174f0088da50e6c71c19616fb1f23d281`.
- Observability and Quality Architecture SHA-256:
  `58be1312c2dfb5aa8f9e3173bea8bd1a433c77f39eec3543c66f530670938fcb`.
- Platform Foundations and Security SHA-256:
  `0b1b734aaf6c59f5b5703dedff26644dc18546089864f7ccb5eafc9a3b3adf5f`.
- Eve SMX Maintenance SHA-256:
  `93364ba19e44e75b4e8688c80ea9a3e85ce0925c4d61b352dd0e5c687b76ab81`.

The pinned operations file and all five resolved link targets are byte-identical
to their current working copies. Existing slides cite and teach parts of these
documents, but no operations page preserves this exact five-link set and
explains what question each target owns. Citation presence alone cannot close
the unit.

## Editorial partition

The comparison starts from five operating questions and gives each linked
document a distinct contribution:

1. **Safety and privacy:** policy order, authorization, confirmation, consent,
   audit and abuse boundaries.
2. **Models and evaluation:** family routing, quality floors, escalation, judge
   validation and model-facing change control.
3. **Quality architecture:** shared traces, logs, metrics, evaluation manifests,
   tests, accessibility and performance gates.
4. **Platform foundations:** contracts, persistence alignment, authorization,
   queues, integrations, residency, audit and launch-security controls.
5. **SMX maintenance:** weekly evidence, held-out rotation, route-price review
   and measured demotion or rollback triggers.

The two platform documents remain separate: one supplies cross-platform
instrumentation and readiness evidence, while the other supplies underlying
control and infrastructure contracts. SMX remains the ongoing operating loop,
not a replacement for release evidence or the other four owners.

## Delivered contract

- One canonical field-guide evidence comparison in
  `content/55-eve-operations-detail.json`, ordered after the release-evidence
  page.
- 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 a dated receipt.

## Acceptance boundary

Automated acceptance must prove:

- every source link resolves to the expected repository path in source order;
- all five linked files remain byte-identical at the pinned revision;
- each visible relation retains its distinct owner and contribution;
- the slide fingerprint, citation and final guide position match the reviewed
  assignment;
- the source-scoped report becomes ten reviewed / zero unassigned, with no
  errors and `complete: true`;
- the generated library, PDF and narration are complete and fresh;
- desktop, compact and mobile layouts keep all five relations readable and
  accessible;
- the prior 747-slide corpus and narration remain byte-equivalent at the
  implementation baseline.

This package does not establish live platform health, a current gate result, a
completed maintenance run, release readiness, reader comprehension, normal-speed
listening or product acceptance.
