# TEACH Nurse Educator & Instructional Designer Mission Control

## Hermes functional-build kit — start here

**Build-kit ID:** `NAIO-NEID-TEACH-FUNCTIONAL-BUILD-KIT-1.0.0`  
**Target product:** `TEACH — Nurse Educator & Instructional Designer Mission Control`  
**Target product ID:** `nurse-educator-instructional-designer-mission-control`  
**Target application version:** `2.0.0`  
**Build-layer lane:** `nurse_educator_instructional_designer`  
**Build-layer route:** `/nurse-educators-designers/dashboard`  
**Home:** `My TEACH Command Studio`  
**Canonical namespace:** `neid_teach.*`

This package is the complete set of instructions, source references, implementation contracts, synthetic examples, and verification material Hermes needs to build a real downloadable local Mission Control for nurse educators, instructional designers, and hybrid/faculty-development roles.

It is a verified **build kit**. It is not the already-built or already-installed application.

## Honest status

**Target application status: `not_operational_build_required`.**

The bundled Mission Control baseline demonstrates useful offline behavior. The educator foundation and TEACH materials are authoritative program specifications. Hermes must still implement the educator specialization, durable storage, authentication, learner-data admission controls, accessibility gates, real backend streaming, bounded agents, backup and recovery, clean installation, and the complete test suite before it may issue a readiness claim.

A screenshot, dashboard preview, development server, source tree, generated code, or statement that tests were written does not make the target operational.

## What Hermes must preserve

Canonical source identity:

- Complete program `NAIO-NEID-COMPLETE-TEACH-1.0`
- Foundation `NAIO-NE-LPEF-1.0`
- Overlay `NAIO-NEID-TEACH-1.0`
- Namespace `neid_teach.*`

Canonical product contract:

- Three role adapters: **Nurse Educator**, **Instructional Designer**, and **Hybrid or Faculty Developer**
- Five foundation departments and the NURSE Compass
- Five protected 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**
- Core Four: **Plan My Day**, **Design & Align**, **Assess & Support**, and **Review & Release**
- One deliberately empty fifth launcher
- 20 TEACH SuperPowers, all `Available Inactive`
- 18 TEACH workflows, all `Preview Only`
- 24 canonical numbered templates
- 33 foundation checks + 120 overlay tests + 16 integration checks = **169 canonical checks**
- 216 build controls + 48 cross-cutting scenarios + 169 canonical checks = **433 required execution records**, all initially `Not Run`

The lane, route, home label, executable schemas, data-class codes, agent IDs, and stable `TEACH-*` catalog keys are build-layer additions. They must never be presented as legacy source identifiers.

## Learner and patient information are excluded

Do not enter or upload:

- PHI, patient stories, chart excerpts, screenshots, recordings, clinical-event details, rare combinations, or live-care questions;
- learner or student names, IDs, submissions, grades, feedback, advising notes, accommodations, conduct or integrity records, clinical-performance records, recordings, secure assessments, or item-bank content;
- employee records, complaints, investigations, private third-party information, confidential institutional material, credentials, tokens, secrets, or financial-account data.

Removing a name does not make a narrative safe. The shipped personal workspace accepts public material, synthetic material, and minimum necessary educator-owned nonsensitive information only.

A future institution-approved workspace is not installed or authorized by this kit. If separately provisioned, it may accept only minimum routing metadata, exact approved non-person course/curriculum content, an exact separately approved aggregate created outside TEACH, or an opaque reference to an approved official-system record. Every object must be purpose-bound, current, and receipted; an aggregate also requires provenance, definition/query/version, denominator, suppression or small-cell review, approval, expiry, and content hash. TEACH must never receive individual-, row-, submission-, event-, or narrative-level learner data.

## Give the package to Hermes

1. Keep the original ZIP unchanged in a private local folder.
2. Extract a working copy immediately beside the unchanged original ZIP.
3. From the extracted package root, run:

   ```text
   python3 tools/verify-build-kit.py --package . --zip ../TEACH-Nurse-Educator-Instructional-Designer-Mission-Control-Hermes-Build-Kit-v1.0.0.zip
   ```

   Windows may use `py` or `python` instead of `python3`.
4. Open a new or verified-isolated Hermes implementation workspace.
5. Give Hermes the complete ZIP or extracted package and paste:

   > Verify this TEACH build kit, open `GIVE-THIS-PACKAGE-TO-HERMES.md`, and follow it exactly. Begin with read-only preflight. Show me one Implementation Activation Card and wait for my approval before installing dependencies, editing a work copy, starting a service, changing a Hermes profile, saving personalization, activating a power or agent, or making a network call.

6. Save every checkpoint receipt and the final handoff report.

## Allow enough time

The build may take many minutes and several visible Hermes turns. Nothing continues invisibly after a turn ends. Hermes must identify any live process, report completed evidence, state blockers honestly, and give the exact resume command at each checkpoint.

The required processing message is in `PROCESSING_MESSAGE.md`.

## Read in this order

For the owner:

1. `START_HERE.md`
2. `INSTALL.md`
3. `implementation/EDUCATOR-User-Installation-Guide.md`

For Hermes or an implementation operator:

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

## The promise

TEACH may help organize, research, design, map, draft, rehearse, compare, and evaluate. Authorized humans teach, assess, supervise, decide, approve, release, and remain accountable. It is not an LMS, gradebook, student-record system, clinical platform, accreditation authority, research determination, surveillance tool, or autonomous instructor.
