# Operator Handoff — TEACH Mission Control

## Audience

Use this page when a human implementation operator is giving the package to Hermes. The full executable instruction is `GIVE-THIS-PACKAGE-TO-HERMES.md`; this page is the handoff checklist.

## Frozen target

- Kit: `NAIO-NEID-TEACH-FUNCTIONAL-BUILD-KIT-1.0.0`
- Product: `TEACH — Nurse Educator & Instructional Designer Mission Control`
- Product ID/version: `nurse-educator-instructional-designer-mission-control` / `2.0.0`
- Build-layer route/home: `/nurse-educators-designers/dashboard` / `My TEACH Command Studio`
- Source programs: `NAIO-NEID-COMPLETE-TEACH-1.0`, `NAIO-NE-LPEF-1.0`, `NAIO-NEID-TEACH-1.0`
- Namespace: `neid_teach.*`
- Starting target status: `not_operational_build_required`

## Before transfer

- Preserve the original ZIP.
- Run the bundled verifier.
- Confirm the workspace contains no learner, patient, employee, credential, secret, or confidential institutional information.
- Use an isolated implementation workspace.
- Do not pre-authorize downloads, profile changes, connectors, agents, powers, or external actions.

## Exact operator instruction

> Treat this package as the complete TEACH functional-build contract. Verify its manifest, checksums, source inventory, and immutable hashes. Display `PROCESSING_MESSAGE.md`. Read `INPUT-PRECEDENCE.md` and `implementation/HERMES-HANDOFF-README.md`, then execute `GIVE-THIS-PACKAGE-TO-HERMES.md`. Begin with read-only preflight. Return one Implementation Activation Card and stop for my exact decision. Preserve source files, unrelated work, learner-data exclusion, no-PHI boundaries, three role adapters, five protected workspaces, Core Four plus empty fifth, 20 inactive powers, 18 Preview workflows, 24 templates, and 169 canonical checks. Do not claim a functional application until runtime evidence supports the permitted handoff state.

## Check the first Hermes response

It must contain:

- package-integrity result;
- actual environment and capability inventory;
- immutable source and proposed work-copy paths;
- detected dependencies, licenses, downloads, and network requests;
- proposed storage, authentication, secrets, backup, update, and rollback model;
- explicit learner-data and patient-data rejection paths;
- all five workspaces and three adapters;
- build/test phases, expected duration, blockers, and recovery;
- one Activation Card with **Approve**, **Revise**, and **Cancel**;
- no mutation before approval.

## Operator stop conditions

Stop the build if Hermes:

- requests learner records or PHI;
- treats “deidentified” narrative or individual learner data as safe;
- invents authority, a Hermes capability, source, test result, or institutional approval;
- edits immutable `source/` material;
- starts a service, dependency installation, migration, or network request before approval;
- creates a second educator Command Center or competing EDENA model;
- activates a power, agent, connector, schedule, sharing, or external action by default;
- substitutes a mock AI response for an unavailable backend;
- calls a preview, screenshot, development server, or test double Operational.

## Required final evidence

Hermes must complete `implementation/HERMES-FINAL-HANDOFF-REPORT-TEMPLATE.md` and reconcile:

- 216/216 build controls;
- 48/48 cross-cutting scenarios;
- 169/169 canonical checks;
- clean installation, restart, persistence, backup/restore, update/rollback, deletion, overlay removal, and uninstall;
- accessibility and learner-data/PHI negative tests;
- genuine backend stream and cancellation when claiming Operational;
- archive, manifest, checksums, source, dependency, migration, and secret-scan evidence.

Every failure, blocker, unsupported feature, not-applicable item, and not-run test remains visible.
