# Hermes Handoff README — TEACH Mission Control

## Purpose

This page orients Hermes before it executes the implementation program. It does not authorize work and does not replace `GIVE-THIS-PACKAGE-TO-HERMES.md`.

## Starting truth

- Build kit: `NAIO-NEID-TEACH-FUNCTIONAL-BUILD-KIT-1.0.0`
- Target: `nurse-educator-instructional-designer-mission-control` `2.0.0`
- Route: `/nurse-educators-designers/dashboard`
- Target status: `not_operational_build_required`
- Institutional deployment: not provisioned by this kit
- Learner records: excluded
- Patient information and live care: prohibited
- External/consequential action: outside the application

## Read order

1. `../PROCESSING_MESSAGE.md`
2. `../INPUT-PRECEDENCE.md`
3. `../SOURCE-NOTES.md`
4. `EDUCATOR-Functional-Build-Master-Prompt.md`
5. `EDUCATOR-Product-Specification.md`
6. `EDUCATOR-Architecture-and-Data-Model.md`
7. `EDUCATOR-Governance-EDENA-and-Data-Boundaries.md`
8. `EDUCATOR-Personalization-Mapping-Crosswalk.md`
9. `EDUCATOR-Starter-Workspace-Crosswalk.md`
10. `EDUCATOR-Agent-Team-and-Routing.md`
11. `EDUCATOR-Capability-and-Badge-Evidence-Model.md`
12. `EDUCATOR-Guide-Page-Content.md`
13. `EDUCATOR-Security-and-Privacy-Checklist.md`
14. `EDUCATOR-Control-Completeness-Matrix.csv`
15. `EDUCATOR-Acceptance-and-Test-Ledger.md`
16. `HERMES-FINAL-HANDOFF-REPORT-TEMPLATE.md`
17. immutable `../source/` material
18. `../GIVE-THIS-PACKAGE-TO-HERMES.md`

If a document conflicts with a higher-priority boundary, follow `INPUT-PRECEDENCE.md` and record the conflict.

## Frozen domain contract

Adapters:

1. Nurse Educator
2. Instructional Designer
3. Hybrid or Faculty Developer

Workspaces:

1. Life, Capacity & Career
2. Teaching, Learning Design & Accessibility
3. Assessment, Feedback & Learner Support
4. Clinical, Skills-Lab & Simulation
5. Curriculum, Program Evaluation, Scholarship & Faculty Development

Catalog and checks:

- Core Four plus empty fifth
- 20 powers inactive
- 18 workflows Preview
- 24 numbered templates
- 10 implementation-generated agents at P0
- 33 + 120 + 16 = 169 canonical checks
- 216 + 48 + 169 = 433 total execution records

## Closed admission model

- `TEACH-DATA-0`: public
- `TEACH-DATA-1`: synthetic
- `TEACH-DATA-2`: educator-owned nonsensitive private
- `TEACH-DATA-M`: minimum institutional routing metadata
- `TEACH-DATA-C`: exact approved non-person course/curriculum content
- `TEACH-DATA-A`: exact approved aggregate created outside TEACH
- `TEACH-DATA-R`: opaque official-system reference
- `TEACH-DATA-X`: prohibited or unclassified

The shipped personal app admits only 0, 1, and screened 2. M, C, A, and R require a separately provisioned purpose-bound institutional workspace and current authority. X is rejected before persistence/provider use.

Learner submissions, grades, evaluations, feedback, accommodations, conduct/integrity records, clinical-performance records, secure items, and other learner payloads are not accepted in any form by the base application. An institutional integration may keep those records in its approved official system and expose only permitted C, A, M, or R objects; it does not import the learner record into TEACH.

## Required preflight result

Return exactly one Implementation Activation Card after read-only inspection. Do not install, edit, start, migrate, connect, save, or probe non-loopback services before approval.

The card must reveal actual—not assumed—environment, dependencies, paths, Hermes capabilities, data boundaries, security model, tests, duration, blockers, rollback, and next step.

## Implementation sequencing

- S0: freeze, verify, approve, copy
- S1: durable authenticated offline core and workspace isolation
- S2: educator/TEACH domain, catalogs, governance, accessibility, canonical tests
- S3: genuine backend, evidence, memory, and bounded agents
- S4: full assurance, clean install, recovery, package, independent verification

Do not build AI before the offline admission, persistence, isolation, and recovery controls work.

## Release truth

The final report must distinguish:

- build kit verified;
- target built;
- release archive verified;
- application installed;
- offline core passed;
- live Hermes connected;
- genuine stream/cancel passed;
- separately provisioned institutional context, if any;
- every test result.

Only the final evidence-derived status may be reported: Operational; Core operational, AI setup pending; or Not operational.
