# Eve operating-state boundary

## Purpose and scope

Teach operators, release owners and assistant-product engineers to distinguish
Eve's documented operating postures and to apply the complete recovery gate.
This package covers source unit `61eaee61ce95060890134639`, exact lines 1–29 of
`V1/docs/eve/operations-observability-and-maintenance.md`, in
`eve-operations-detail`. It adds `eve-detail-operating-postures`,
`eve-detail-degraded-posture-choice` and `eve-detail-reconciliation-gate`. The
dependency table, signal inventory, release links and related-document
navigation remain separate source units.

## Baseline and dependencies

- Implementation baseline: `46ddb7153032eb0e244c32ee08052d1519e42c7a`.
- Inventory/source revision: `1ceae52c7896a59ac74a4429d410f3218f0b91c6`.
- Source file SHA-256:
  `37e2944ae765de1819a9d4801b58aa3f8a75f6795147b89e2c4694bfc704f6d4`.
- Unit SHA-256:
  `1ad49d61dc8dae32f50a68beb56e0986033f1a15f5f1f7c4b04d9a86507041c1`.
- Prerequisite guide: `eve-operations`; existing operations detail slides retain
  the dependency, degradation, telemetry, incident and release detail.

The pinned file and current working copy are byte-identical. This package
teaches the documented state contract. It does not infer a live state machine,
current thresholds, provider health or incident status.

## Source review

The Mermaid graph contains fourteen directed transitions when the `[*]` entry
edge is included. Healthy degrades on dependency quality or telemetry breach.
Degraded branches to ReadOnly when mutation safety is unproven, Fallback when a
measured compatible or deterministic path remains, and Unavailable when no
honest safe fallback exists. Healthy and Degraded have distinct direct Incident
triggers.

ReadOnly, Fallback and Unavailable each enter Recovering through a different
repair condition. Incident must pass through Contained before Recovering.
Recovering advances to Healthy only when routing, grounding, receipts and evals
reconcile; verification or reconciliation failure returns it to Degraded. The
surrounding prose expands that gate across identity, policy, tools, disclosures
and storage and rejects a green health endpoint as sufficient proof.

## Deliverables

- Three canonical field-guide slides in `content/55-eve-operations-detail.json`.
- Ordered membership in `catalog-source.json` before dependency-specific detail.
- One reviewed assignment containing all three assembled slide fingerprints.
- Updated learning map, coverage ledger, TODO/README status and generated
  catalog, HTML, guide maps, narration, PDF and coverage artifacts.
- Exact source, graph, sequence and count regressions plus a dated verification
  receipt with desktop, compact, mobile, PDF and actual-audio evidence.

## Design and story

The source graph is split by decision job rather than squeezed into one page.
The first `recovery-map` shows entry, degradation classification and the
incident override. The second distinguishes all three capability branches from
Degraded. The third shows posture-specific repair, incident containment and the
reconciliation fork. Grouped rows share a destination only when every source
state is still named; their notes retain each distinct trigger.

The guide opens with those three state-contract pages, then asks what end-to-end
evidence proves a repaired dependency has restored the user promise. The
existing degradation and incident slides supply concrete behavior without being
counted as substitutes for the complete state unit. No live dashboard, measured
threshold or executed incident is implied.

## Acceptance

- Expanding the authored `fromStates` arrays yields exactly all fourteen source
  edges and no invented edge.
- Every state, trigger family, repair condition, incident-containment step and
  reconciliation outcome appears in the visible sequence and complete
  explanation.
- All three slides cite the exact source heading, use
  `designEdition: field-guide`, omit redundant mastheads and retain three
  substantive notes and questions.
- The assignment validates at the exact inventory revision and moves only this
  source from five reviewed/five open to six reviewed/four open.
- Static and playing desktop/compact/mobile layouts, Explain/source access,
  accessibility, tagged PDF pages and actual narration playback pass.

## Verification and recovery

Run focused assignment/composition tests while authoring, then the affected
guide and center browser suites, PDF checks, full presentation Python and Node
suites, builder freshness, coverage, inventory freshness and narration
integrity. Run costly gates serially after the repository resource checks.

Generated files are rebuilt only through the canonical builder, narration
renderer and browser PDF exporter. Stop the owned process group if the host
crosses the memory thresholds in `AGENTS.md`; preserve logs and resume with the
focused command. If source or assembled slide hashes change, leave the
assignment stale until the explanation and evidence are reviewed again.

## Closeout

Status: the source review, three-slide sequence, exact hash-bound assignment,
generated artifacts, narration and automated desktop/compact/mobile/PDF review
are complete. The dated verification receipt records all final evidence and the
remaining limits. The next source dependency after this package is the complete
nine-row operational dependency map.
