Purpose and scope#
Teach operators, release owners and assistant-product engineers the complete
monitoring contract in source unit 022925e97e597994da3e1e43, exact lines 77–96
of V1/docs/eve/operations-observability-and-maintenance.md. This package adds
four pages to eve-operations-detail: response/routing, effects/evidence,
controls/continuity and quality/action. The release procedure and related-link
navigation remain separate source units.
Baseline and source binding#
- Implementation baseline:
5d634757f7fab353984ef3c0cc5f065cc534636c. - Inventory/source revision:
1ceae52c7896a59ac74a4429d410f3218f0b91c6. - Source file SHA-256:
37e2944ae765de1819a9d4801b58aa3f8a75f6795147b89e2c4694bfc704f6d4. - Unit SHA-256:
04c0885034aa82d9f210120686ce85d9098eb40abd41f9fd797ae16bc5e542db. - Exact unit shape: lines 77–96, 123 words, twelve list items, no tables or code blocks.
The pinned file and current working copy are byte-identical. The existing
eve-detail-monitor-maintain page combines selected health measures with the
separate routine-maintenance unit. It remains useful synthesis, but its visible
cadence table and narration omit required qualifiers and cannot bind the whole
health unit.
Editorial partition#
The source order becomes four readable decision groups:
- Response and routing: first render, first sentence, family/provider-leg total latency, route distribution, unknown/misroute audits and family fallback.
- Effects and evidence: success, timeout, denial, invalid-argument and partial tool outcomes; confirmation decision/stale/replay behavior; grounding holds, unsupported claims and corpus freshness.
- Controls and continuity: policy-versioned refusal and safety supersession; provider escalation/retry/budget/kill-switch state; persistence/reconnect failures and duplicate prevention.
- Quality and action: crash and client voice/tour failures, family eval floors, prompt-hash drift, successful-outcome cost and alert ownership.
The visible middle cell on every row preserves the source measure. The final cell explains the diagnostic distinction without inventing a threshold or a measured result. No page ranks a row or claims current service health.
Delivered contract#
- Four canonical field-guide slides in
content/55-eve-operations-detail.json, ordered after the telemetry-schema page and before incident triage. - One reviewed assignment with exact source and assembled slide fingerprints.
- Three notes and three review questions per page, plus locally rendered narration and a complete regenerated 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 twelve source bullets and the runbook/affected-plane sentence remain visibly represented in source order;
- the measure groups remain paired with their operating interpretations;
- all four slide fingerprints, citations and guide positions match the reviewed assignment;
- the source-scoped report moves to eight reviewed / two open without errors;
- the generated library, PDF and narration are complete and fresh;
- desktop, compact and mobile layouts keep every row readable and accessible;
- the prior 680-slide corpus and narration remain byte-equivalent at the implementation baseline.
This package does not establish live telemetry, threshold configuration, alerting, service-level attainment, runbook execution, reader comprehension, normal-speed listening or product acceptance.