# TEACH Mission Control — User Guide

## For nurse educators, instructional designers, and hybrid/faculty developers

## What you downloaded

You downloaded a **Hermes functional-build kit**, not an already-installed application. It preserves the Nurse Educator foundation, TEACH SuperPowers, working Mission Control engineering baseline, implementation contracts, synthetic examples, and verification materials needed to create a local application.

Current target status: `not_operational_build_required`.

Hermes must build a separate release and prove its behavior. This can take many minutes and several visible turns. Nothing continues in the background after a Hermes turn ends.

## What the completed Mission Control is for

TEACH is intended to help you:

- coordinate teaching, design, scholarship, professional growth, recovery, and life priorities;
- align outcomes, learning experiences, practice, assessment, and feedback;
- create accessible and inclusive draft learning materials;
- prepare authentic assessment and criterion-linked feedback for human review;
- build synthetic clinical, skills-lab, and simulation materials under human clinical and faculty authority;
- maintain sources, versions, rights, curriculum maps, and evidence gaps;
- rehearse difficult conversations and prepare questions for authorized people;
- develop responsible AI literacy and agent-supervision skills;
- protect workload, faculty/designer voice, learner dignity, and human accountability.

TEACH does not replace an educator, designer, faculty committee, clinical authority, disability service, academic-integrity process, accreditation body, research or ethics authority, student-record system, LMS, gradebook, or official institutional process.

## Safety before convenience

### Do not enter learner records

The general and personal application excludes:

- learner or student names, IDs, contact details, submissions, grades, evaluations, feedback, advising notes, accommodations, conduct or integrity records;
- clinical-performance or competency records;
- recordings, screenshots, identifiable messages, secure examinations, or item banks.

Use synthetic examples, generic patterns, public sources, or educator-authored nonsensitive material. Removing a name from a narrative or submission does not automatically make it safe.

### Do not enter patient information

Do not enter PHI, patient stories, chart excerpts, clinical-event details, rare combinations, recordings, screenshots, or live-care questions. TEACH is not a clinical decision system and must not delay an emergency, escalation, clinical, privacy, or reporting route.

### Keep official work in official systems

Grades, released feedback, student communications, LMS changes, accommodation implementation, integrity findings, clinical clearance, curriculum approval, institutional commitments, publications, and other consequential actions occur outside TEACH through accountable humans and approved systems. TEACH may prepare a draft or review packet; it does not perform the action.

## Install the build kit

1. Keep the original versioned ZIP unchanged.
2. Extract a working copy immediately beside the unchanged ZIP in a private folder.
3. Open a terminal in the extracted package root and run:

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

4. Open a new or verified-isolated Hermes implementation workspace.
5. Give Hermes the complete package and paste the instruction from `README-FIRST.md`.
6. Wait for a read-only preflight and one Implementation Activation Card.
7. Review the exact files, commands, dependencies, downloads, local paths, security model, data boundary, tests, rollback plan, and blockers.
8. Choose **Approve**, **Revise**, or **Cancel**.
9. Save every S0–S4 checkpoint receipt and the final handoff report.

Build-kit verification proves source integrity. It does not prove the target app has been built.

## What the completed app should contain

### Three role adapters

- **Nurse Educator** — only the teaching, assessment, supervision, and release authority currently assigned by the institution, program, or site.
- **Instructional Designer** — may analyze, design, prototype, audit, recommend, document, and coordinate; design access does not confer faculty, clinical, grading, accommodation, integrity, curriculum, or accreditation authority.
- **Hybrid or Faculty Developer** — declares the active task-level hat for each consequential artifact; switching hats triggers a new authority and permission check.

A role adapter changes eligible support and questions. It never grants authority.

### Five protected workspaces

1. **Life, Capacity & Career** — priorities, capacity, protected time, recovery, career, scholarship goals, private life planning, and re-entry after overload.
2. **Teaching, Learning Design & Accessibility** — outcomes, lessons, modules, learner variability, active learning, modality, cognitive load, accessibility, inclusion, sources, and rights.
3. **Assessment, Feedback & Learner Support** — synthetic or generic blueprints, rubrics, calibration, feedback structure, AI-use guidance, support-conversation preparation, and human-review queues; no learner records.
4. **Clinical, Skills-Lab & Simulation** — synthetic cases, objectives, prebriefs, equipment checks, cues, observer tools, stop conditions, accessibility, and debrief plans; no real patient or learner-performance data.
5. **Curriculum, Program Evaluation, Scholarship & Faculty Development** — versioned maps, evidence gaps, approved non-person content, aggregate sensemaking when separately authorized, copyright/OER review, faculty AI literacy, portfolio, manuscripts, presentations, and development plans.

These workspaces are protected scopes inside one Command Center. A mission has one active role/hat and workspace. Context never transfers silently.

### Core Four

- **Plan My Day** — Top Three, fixed commitments, review burden, capacity, protected time, and Plan B.
- **Design & Align** — begin with an approved outcome and learner level; prepare a learning-experience brief and alignment map.
- **Assess & Support** — prepare an assessment, rubric-evidence view, feedback structure, or support conversation without deciding a grade or learner determination.
- **Review & Release** — apply target, evidence, authority, accessibility, inclusion, integrity, clinical safety, privacy, rights, disclosure, and exact human-release checks.

The fifth launcher starts empty.

### TEACH catalog

- 20 SuperPowers, all inactive after installation
- 18 workflows, all Preview only
- 24 canonical numbered templates
- 10 bounded implementation-generated agents, all disabled at P0

Setup does not activate any catalog item. A badge, title, prior use, or technical availability never activates one.

## First-run setup

After Hermes produces and verifies the actual application:

1. Confirm the final package hash and readiness state in the handoff report.
2. Install only by the exact tested command or launcher in that report.
3. Confirm the service binds only to loopback and the URL is `/nurse-educators-designers/dashboard` under the reported local origin.
4. Create the authenticated local owner and protect recovery material.
5. Select a role adapter and active task hat.
6. Review the five workspaces and data boundary.
7. Review the proposed Mission Profile field by field. Edit, reject, or approve; raw Soul Quiz answers and raw `SOUL.md` must not be stored by the app.
8. Review synthetic Starter content. Adopt, edit, clear, or restore it. Starter content is not completed work or badge evidence.
9. Confirm session-only memory, no connections, no sharing, no external actions, empty fifth launcher, inactive powers, Preview workflows, and P0 agents.
10. Start one low-risk mission.

## Start a mission

Every mission uses a repeatable five-stage loop:

1. **Assess** — collect minimum context; separate verified facts, user statements, sources, assumptions, and unknowns.
2. **Diagnose/Define** — define the learning, design, capacity, scholarship, or decision need without making a clinical diagnosis or learner judgment.
3. **Plan** — compare options by benefit, feasibility, time, workload, cost, equity, accessibility, ethics, authority, and values; define success and review gates.
4. **Implement** — create local tasks, drafts, simulations, checklists, and human-owned handoffs. Real consequential execution remains outside TEACH.
5. **Evaluate** — compare results with goals; record what worked, what failed, uncertainty, unintended effects, and whether to retain, revise, pause, remove, escalate, or begin a new cycle.

You can pause, return to an earlier stage, branch, reopen, or begin another cycle.

## Artifact and review states

The mission lifecycle is:

`Exploration → Simulation → Recommendation → Draft Artifact → Approved Plan → Authorized Execution → Completed Action → Evaluated Outcome`

- **Approved Plan** means a human reviewed the plan's scope. It is not permission to act.
- **Authorized Execution** means an accountable human is acting in an approved official system outside TEACH.
- **Completed Action** requires a verified external reference; TEACH does not create the real action.

Review status—such as awaiting evidence, accessibility review, clinical review, faculty review, or institutional guidance—is tracked separately.

## Understanding EDENA

EDENA means **Educator Decision, Evidence, Nursing-safety, and Authority**.

- **Green:** low-risk organization or generic preparation; proceed with visible AI labeling and review.
- **Yellow:** educational or evidence material needing human review before use or release.
- **Orange:** sensitive or consequential support; minimize information, use the appropriate environment, prepare a bounded human-facing brief, and stop before the decision.
- **Red:** high-risk or prohibited material; show the reason and human route.

The application records both `edena_tier` and `absolute_stop`. An absolute stop always blocks the original request. When a Personal Red request is not an absolute stop, you may deliberately begin a **new** generic or synthetic sandbox; the app may not carry the stopped content into it. Institutional Red blocks progression until required authorization. EDENA never grants authority.

## Safe first missions

- “Help me create a seven-day teaching, design, scholarship, family, and recovery plan from these nonsensitive time constraints.”
- “Using a public competency statement and a fictional learner group, help me draft an alignment map and list what a faculty owner must verify.”
- “Using a synthetic assignment, help me create an accessible rubric structure and feedback checklist. Do not grade or infer anything about a real learner.”
- “Create a fictional simulation prebrief and safety-review checklist. Include the human clinical and simulation release gates.”
- “Help me organize public sources for a faculty AI-literacy workshop and distinguish verified evidence from interpretation.”
- “Help me prepare a generic learner-support conversation using observable fictional facts and authorized referral routes.”

## AI, agents, and evidence

The offline core must work when AI is unavailable. AI-only controls must show `Setup required`, `Offline`, `Authentication failed`, `Hermes unavailable`, or another truthful state.

When connected, a real backend must produce genuine streamed output. The interface must expose the selected agent, routing reason, context, data class, tools, limits, approval point, and Stop/Kill control. Production may not use canned completions or fake citations.

Evidence records should show source identity, authority, version/date, applicability, relevant claim, conflict, uncertainty, rights, reviewer, and expiry. A polished response is not evidence.

## Capabilities and badges

The four levels are Basic, Intermediate, Advanced, and AI Agent Orchestration Master. Evidence comes from observable, reviewed activity—not clicks, streaks, time spent, synthetic Starters, AI praise, private life details, learner information, or self-ratings.

Badges are developmental evidence only. They are not licensure, certification, continuing-education credit, teaching qualification, clinical competence, institutional authorization, promotion, or permission.

## Privacy and memory controls

Session-only is the default. A memory proposal must show the exact field, purpose, workspace, source, access, expiry, and deletion behavior before saving. You must be able to inspect, edit, forget, export, or delete permitted memory.

Learner records, patient information, secure assessments, health narratives, employment disputes, confidential institutional content, secrets, and unsupported authority inferences never enter memory, search, badges, agents, exports, or backups.

## Backup, restore, update, and rollback

Before relying on the app, create a scoped backup and prove restoration in a temporary location. Private backups include only the private store. A separately authorized institutional backup includes one institutional store only. Never create a cross-context backup.

Before update, stop the app, verify the new package, record versions and hashes, create and test a matched backup, preview migrations, and define rollback conditions. After update, rerun integrity, accessibility, learner-data/PHI, restart, backup/restore, and release tests.

On failure, stop, preserve redacted diagnostics, restore the matched app and database backup, verify integrity, and record rollback.

## Everyday recovery controls

- **Pause All:** stop pending and new AI runs while preserving records.
- **Stop/Kill:** terminate the selected stream or agent run and record its terminal state.
- **Safe Reset:** preview a return to private synthetic mode, session-only memory, no connectors/sharing/actions, Core Four, empty fifth, inactive powers, Preview workflows, and P0 agents.
- **Correct:** change a source or fact and mark dependent artifacts, approvals, and badges stale.
- **Export/Backup:** show exact included fields and workspace before creating the file.
- **Delete:** show scope and consequences, then remove eligible primary and derived records.
- **Overlay removal:** remove TEACH specialization while preserving compatible educator foundation and unrelated work.
- **Rollback:** restore a verified matched application/database pair.
- **Uninstall:** stop services, offer a scoped backup, preview retained/deleted paths, remove files and launchers, and report any remaining copies.

## If sensitive information appears

Stop the run. Do not ask the AI to repeat, summarize, classify, or redact the content. Prevent further persistence or provider transmission where possible. Use activity and deletion controls, preserve only content-free incident facts, and follow the authorized privacy, security, clinical, student-record, academic-integrity, HR, legal, or incident-response route.

## The benefit and the responsibility

TEACH can make priorities, evidence, accessibility, review burden, authority gaps, and next actions more visible. It can help you create better drafts and more disciplined questions. You remain responsible for learner dignity, professional judgment, source verification, local policy, teaching and assessment decisions, clinical safety, official records, release, and final action.
