# Start Here — TEACH Mission Control

This download gives Hermes the materials needed to build your local Nurse Educator & Instructional Designer Mission Control. It is not yet the finished application.

## Your five-minute start

1. Save the original ZIP unchanged.
2. Do not add learner, patient, employee, or confidential institutional information.
3. Extract a working copy immediately beside the unchanged ZIP and verify it:

   ```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 private, isolated Hermes implementation workspace.
5. Give Hermes the complete package and paste the instruction from `README-FIRST.md`.
6. Review the Implementation Activation Card. Choose **Approve**, **Revise**, or **Cancel**.
7. Keep the checkpoint receipts. The build may require several visible turns.
8. Accept the final application only when the handoff report states what was actually built, tested, blocked, and supported.

## What you should expect

The finished product is intended to provide one educator/designer Command Center with three role adapters, five protected workspaces, the Core Four, 20 inactive SuperPowers, 18 Preview workflows, 24 templates, a five-stage mission loop, a Guide, capability growth, and recovery controls.

The five workspaces are:

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

They are protected scopes within one Command Center, not five disconnected applications.

## What you must not provide

Do not provide names, IDs, submissions, grades, feedback, accommodations, conduct records, clinical evaluations, secure items, patient information, clinical events, employee files, passwords, tokens, or private institutional documents. Use public or synthetic material for setup and testing.

## The honest completion states

Hermes may end with only one of these:

- **Operational** — every applicable criterion passed, including a real configured streamed response and cancellation through the packaged application.
- **Core operational; AI setup pending** — all offline/core criteria passed, but a live backend was unavailable for the real-stream test.
- **Not operational** — one or more core criteria failed or remain blocked.

Until that report exists, the target remains `not_operational_build_required`.
