# Eve operations · configuration and secrets boundary

## Work package

**Purpose and scope.** This package teaches the complete **Configuration and
secrets** unit at lines 44–56 of the pinned Eve operations handbook. It serves
builders and operators who need to distinguish reviewable configuration names,
resolved runtime settings, secret material and the evidence required for a
change. It adds `eve-detail-configuration-boundary` to `eve-operations-detail`,
after degraded-capability behavior and before telemetry. It does not certify a
deployment's environment, secret-store integration, startup result, redaction,
rollback or release acceptance.

**Baseline and sources.** The implementation baseline is the published parent of
this package. Teaching remains pinned to
`1ceae52c7896a59ac74a4429d410f3218f0b91c6`. The primary unit is
`9e873279050f7a1ad6aea0fa` in
`V1/docs/eve/operations-observability-and-maintenance.md`; the linked quality
procedure is **Prompt and skill change control** in
`V1/docs/eve/models-quality-and-evaluation.md`. The source describes operating
policy. It does not identify the live environment values or prove enforcement.

**Source review.** Complete teaching must retain all seven startup-controlled
families: provider endpoints, model bindings, limits, feature flags, release
scopes, tool availability and kill switches. It must distinguish the committed
canonical map of names from resolved values, preserve startup validation and log
redaction, and keep secrets out of prompts, tool descriptions, client bundles
and evidence attachments. Model/provider settings follow a release-affecting
registry path; prompts, skills, tool descriptions and evaluation dependencies
follow the quality path.

**Design and story.** A four-row evidence comparison gives equal weight to the
name map, runtime binding, secret boundary and change path. The visual asks the
reader to connect each boundary to evidence rather than infer a deployment
sequence. The main slide stays sparse; the Explain layer supplies rationale and
the two distinct release-review cases. No credential, invented environment
value, dashboard or product screenshot is introduced.

**Acceptance.** The exact unit, revision, source digest, slide fingerprint,
citation heading and guide membership must bind in a reviewed assignment. The
slide and narration must name all controlled setting families, all four
forbidden secret locations and both change paths. Desktop, compact, mobile,
source-dialog, accessibility, print/PDF and actual-audio checks must pass for
all eight guide slides. Visual review must confirm readable four-row comparison
and mobile reflow without clipping or horizontal document overflow.

**Recovery and closeout.** Generate only the new narration track before the full
audio-integrity check. Stop its process group if the repository resource
threshold is reached. Rebuild catalog, guide, coverage and PDF outputs from
canonical inputs; do not patch generated artifacts. The dated verification
receipt records final hashes, observed exits, review findings and publication.
Five meaningful units in the same source remain open after this package.
