# Guide Page Content — My TEACH Command Studio

This file is the required in-application Guide page for **TEACH — Nurse Educator & Instructional Designer Mission Control**. It must remain available from every screen, work without an AI provider and use plain language, keyboard-accessible controls, meaningful headings, non-color status labels and printable fallback content.

## Welcome

**My TEACH Command Studio** is a governed local workspace for nurse educators, instructional designers and hybrid/faculty developers. It helps you plan, learn, design, compare options, prepare artifacts, coordinate projects, reflect and build responsible AI capability while keeping decisions and accountability with people.

The dashboard is not an LMS, gradebook, learner-record system, secure exam bank, clinical decision-support tool, accreditation authority, research or ethics service, personnel system, legal service, communications service or autonomous education agent. It cannot grant employment, faculty, grading, clinical, curriculum, accessibility, data, publication, release or institutional authority.

The distributed package is a functional-build kit for Hermes. Its initial status is `not_operational_build_required`. It becomes a real local application only after Hermes builds it, runs the required checks and reports evidence-derived results.

## Preparation message

Show this message before generation or installation begins:

> **Your Nurse AI OS Mission Control is being prepared.**
> This process may take several minutes because the system is translating your Discover Packet and Soul Quiz results into a personalized, governed workspace. It is configuring your roles, values, goals, workflows, capability pathways, permissions, and EDENA advisories.
>
> You are not simply creating another dashboard. You are establishing a Nurse AI OS shaped by your values, strengthened by disciplined problem-solving, and designed to evolve with your knowledge and experience. Please keep this window open while your Mission Control package is created.

Progress must reflect completed checkpoints. Never display invented percentages, simulated streaming or a fake completion message. If setup stops, show the last verified checkpoint and an exact Resume instruction. Do not start a second installer over an unfinished run.

## What personalizes this dashboard

The Discover Packet supplies owner-provided goals, priorities, work preferences, constraints and possible workspace interests. The Soul adapter supplies derived themes such as values, working style, strengths, growth edges and preferred AI boundaries. Raw Soul Quiz answers and sensitive narratives are never imported.

Every mapped field is a proposal. Review it using **Keep**, **Edit**, **Exclude** or **Mark uncertain**. Conflicts remain visible; the system must not guess. Profile approval personalizes the interface but never creates credentials, permissions, institutional access or authority.

You may update the Soul-derived profile as your life, role and goals change. Review the changed fields and provenance before saving a new version. Previous versions remain distinguishable and recoverable according to the local retention setting.

## Roles and multiple dashboards

For each TEACH mission, select exactly one role adapter:

- Nurse Educator
- Instructional Designer
- Hybrid or Faculty Developer

Then name one active task hat, such as course designer, simulation educator, faculty developer or portfolio builder. A hybrid user rebinds the task hat whenever responsibilities change. The least-authorized applicable role controls.

One person may also have other Nurse AI OS role dashboards. They may share a reviewed identity and Soul profile, but each dashboard keeps its own route, goals, missions, agents, badge evidence, data boundary and authority state. TEACH uses the lane `nurse_educator_instructional_designer` and route `/nurse-educators-designers/dashboard`. No role dashboard may silently read, merge or export another dashboard’s records.

## Five protected workspaces

Every mission uses exactly one active workspace:

1. **Life, Capacity & Career** — personal planning, sustainable capacity, career direction, scholarship goals and reflective growth using only coarse owner-provided details.
2. **Teaching, Learning Design & Accessibility** — outcomes, alignment, learning activities, cognitive-load review, modality planning, accessibility preparation and source-aware content design.
3. **Assessment, Feedback & Learner Support** — synthetic assessment blueprints, generic rubrics, feedback rehearsal and support-conversation preparation without learner payload or consequential decisions.
4. **Clinical, Skills-Lab & Simulation** — fictional case design, objectives, prebriefs, equipment and stop checklists, facilitation drafts and debrief planning without patient or live-care data.
5. **Curriculum, Program Evaluation, Scholarship & Faculty Development** — curriculum maps, approved aggregate interpretation, source and rights records, scholarship planning, faculty-learning design and portfolio evidence preparation.

Life, Capacity & Career uses a physically separate owner-private store. Institution/course/program/project partitions are separately isolated. Search, caches, model context, memory, agents, badge evidence, exports and backups must not silently cross those boundaries.

## Deployment contexts

**Private Educator/Designer Mode** is the only installed default. It permits public sources, unmistakably synthetic material and minimum educator/designer-owned nonsensitive planning. Memory is session only (`session_only`) by default. Connectors, external actions, shared access, release and background automation are Off.

An **Institution-Approved Education Workspace** is a separate runtime that this kit does not provision. It requires a current authenticated bind for exactly one institution/course/program/project and human-approved receipts for role and task authority, purpose, permitted fields and classes, source and rights, platform and model, privacy, security, accessibility, records, audit, retention, deletion and release ownership. A profile, badge, setting, prompt or agent cannot create this bind.

Changing context closes the prior repository, clears context-scoped cache and model context, rotates the partition nonce and rechecks role, task hat, workspace, data class and authority.

## Data classes and permanent exclusions

Use one visible data class for every mission:

| Class | Meaning |
|---|---|
| `TEACH-DATA-0` | Public, authoritative, nonsensitive source with version, applicability and rights tracked. |
| `TEACH-DATA-1` | Unmistakably synthetic learner work or fictional clinical/simulation material. |
| `TEACH-DATA-2` | Minimum educator/designer-owned nonsensitive planning, capacity, career or draft material; no third-party or confidential detail. |
| `TEACH-DATA-M` | Minimum opaque business-routing metadata only; never person or learning analytics. |
| `TEACH-DATA-C` | Exact approved non-person course/curriculum content created outside TEACH and bound to source, version, rights, purpose, approval, expiry and hash. |
| `TEACH-DATA-A` | Exact approved aggregate created outside TEACH with definition/query/version, denominator, missingness, provenance, suppression, steward, purpose, approval, expiry and hash. |
| `TEACH-DATA-R` | Opaque official-system reference only; no learner payload, identifier, excerpt, score or narrative. |
| `TEACH-DATA-X` | Prohibited, restricted, sensitive or unclassified content. |

`TEACH-DATA-X` is rejected before echo, persistence, logs, indexing, memory, backup, export, badge evidence or AI processing. This is a **no PHI / no-phi** base product. Never enter learner records, submissions, grades or evaluations; accommodations; conduct, integrity or complaint records; secure tests, answers or item banks; employee records; human-participant data; PHI, patient stories or live-care material; secrets; restricted institutional content; person profiling, ranking or surveillance; or row-, person- or narrative-level content described as “deidentified.”

**Tooltip — Why the stop occurs:** TEACH does not clean, summarize or transform prohibited content. Remove it at the approved source and begin a new content-free or synthetic mission.

## Home and launch controls

The home view is **My TEACH Command Studio**. Pin exactly the Core Four:

1. **Plan My Day**
2. **Design & Align**
3. **Assess & Support**
4. **Review & Release**

The fifth launcher remains empty and reads **Preview and approve before adding**. Keep no more than seven attention items visible.

The persistent status bar shows role, active task hat, deployment context, workspace, data ceiling, `edena_tier`, `absolute_stop`, authority status, memory status and **Pause All**. The library shows all 20 powers as **Available / Inactive**, all 18 workflows as **Preview Only**, all 24 numbered templates and all 10 agents as **P0 / Disabled**.

## Start a Mission

Select **Start a Mission** and describe a goal, situation, problem, project or decision. Before any AI call, confirm:

1. Which role adapter and task hat apply?
2. Which one workspace and deployment context apply?
3. Which data class is required?
4. What facts are verified, owner-provided, assumed or unresolved?
5. What human authority, review and source/rights checks are needed?
6. What outcome would count as success, partial success, no result, harm or uncertainty?

If the input is prohibited or unclassified, the original request stops without content echo or transformation.

## The five-stage improvement loop

Every mission displays a visible, repeatable loop. You can pause, revise, return to an earlier stage, branch a sandbox option or start another iteration.

### 1. Assess

Describe the current state, stakeholders, constraints, available resources and relevant credible evidence. Keep separate panels for verified facts, owner-provided information, assumptions and unresolved questions.

### 2. Diagnose or Define

State the central need, opportunity, problem or decision without profiling a person. Consider root contributors, dependencies, competing explanations, missing knowledge and risks.

### 3. Plan

Compare options by expected benefit, feasibility, time, burden, cost, evidence, ethics, rights, accessibility and risk. Define measurable outcomes, milestones, owners, safeguards, review gates and stop conditions.

### 4. Implement

Create local drafts, prototypes, prompts, checklists, workflows and handoff packets. Human confirmation is required before any consequential state change. TEACH has no LMS, gradebook, email, calendar, messaging, publication or institutional write endpoint.

### 5. Evaluate

Compare results with the original success measures. Record what worked, failed, remained uncertain or caused an unintended effect. Choose Continue, Modify, Escalate or Stop, then feed the lesson into the next Assess stage. Never invent adoption, learner outcomes, validity, fairness, accessibility compliance or institutional impact.

## Sandbox and artifact truth

Use the sandbox to explore alternative interpretations, compare recommendations, challenge assumptions, run fictional scenarios, conduct a premortem, prototype and review risk before real-world use.

Use the exact artifact lifecycle:

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

- **Approved Plan** means a named human reviewed the exact scope and content. It is not execution authority.
- **Authorized Execution** records an authorization or action performed outside TEACH by an accountable human or official system. TEACH performs no action.
- **Completed Action** requires a minimized, verified external reference only.
- **Evaluated Outcome** records evidence and uncertainty after the external result is reviewed.

Review states, such as Awaiting accessibility review, are a separate axis and never replace the lifecycle state.

## EDENA advisories and enforcement

EDENA means **Educator Decision, Evidence, Nursing-safety and Authority**. Store and display `edena_tier` independently from `absolute_stop`.

- **Green:** lower-consequence permitted work; verify sources and remain within the active boundary.
- **Yellow:** meaningful uncertainty or review need; show assumptions and required checks.
- **Orange:** consequential or authority-sensitive; keep personal exploration generic or synthetic and identify the responsible human route.
- **Red:** high-risk or prohibited path. In Personal Edition, stop the original request. Only when `absolute_stop=false`, after deliberate acknowledgment, may the owner begin a new clean generic or fictional sandbox. Never carry stopped content forward. In an Institutional Edition, block operational progression until the required human/policy authorization is verified.
- **Absolute stop:** nonwaivable everywhere. No override, transformation, export, agent run or institutional bind may continue the stopped content.

**Tooltip — EDENA is not approval:** A color never certifies safety, evidence quality, legality, policy compliance, accessibility, institutional acceptance or permission.

Apply the TEACH Gate before persistence, import, AI, memory, artifact creation, agent execution, export or proposed handoff:

- **T — Target:** What exact outcome and audience are in scope?
- **E — Evidence:** What sources, versions, applicability, limits and rights support it?
- **A — Authority:** Which person owns the decision, data, review and release?
- **C — Checks:** Which privacy, security, accessibility, fairness, integrity and safety checks apply?
- **H — Human:** What must a named human review, decide or perform outside TEACH?

## Hermes agents and permissions

The ten TEACH agents are proposed capability roles, not autonomous coworkers.

- **P0 / Disabled:** installation default. No model call, retrieval, tool, network, credential, memory, schedule, delegation or background work.
- **P1 / Suggest:** one exact, expiring run that may propose content without tools or external action.
- **P2 / Prepare:** one exact, expiring, read-only or draft-only run under an immutable charter and one-use authorization token.
- **P3 / Deterministic personal reminder only:** available only after three supervised successful runs and separate approval. It uses minimum personal reminder fields, no model inference, institution/course/learner data, connector, external destination, monitoring, assessment, surveillance, decision or release.
- **P4:** absent from this product.

P1 and P2 never self-activate, expand scope, retry invisibly, recurse or continue in the background. **Pause All** and per-run **Kill** must work on a control path independent of the model or agent run.

## Capabilities and mastery

The Capabilities and Mastery page recognizes observable, reviewed development across four levels:

1. Basic
2. Intermediate
3. Advanced
4. AI Agent Orchestration Master

Each badge shows the capability, level, evidence, date earned, progress to the next level, recommended challenge and governance or safety competencies demonstrated. Evidence may include completed nonsynthetic missions, reviewed artifacts, demonstrated skills, corrections, reflections, assessments or validated project outcomes. Synthetic starter activity and button clicks do not earn a badge.

Badge evidence records the user’s contribution, AI contribution, sources, corrections, human review and what the user can now do independently. They exclude learner, patient or person payload; secure assessments; confidential institution text; and private-life detail. If evidence is corrected, deleted, expired, superseded or loses authority, the badge is recomputed, suspended, downgraded or revoked.

Badges are developmental records only. They are not licensure, certification, continuing-education credit, appointment, promotion, accreditation, clinical or teaching competence, institutional approval, access or permission. They unlock no authority.

## Sources, rights and output review

Every factual or policy-sensitive artifact displays sources, version/date, applicability, uncertainty and rights status. A link or citation does not grant reproduction rights. A source-registry hash mismatch, missing source or unknown recommendation ID disables that recommendation and sends it to human review.

Before external use, a named human reviews the exact artifact for evidence, local policy, privacy, rights, accessibility, fairness, learner dignity, clinical safety where applicable, disclosure, audience, authority, fallback and rollback. AI supports—but does not replace—professional judgment. The user remains responsible for checking facts, evidence, recommendations and final actions.

## Privacy, memory, exports and recovery

Session-only memory is the default. Raw Soul answers are never stored. Do not enter protected health information, confidential institutional information or sensitive personal data unless a separate approved deployment is technically configured for that exact class—and note that learner-record payload remains excluded from this base product.

Exports are local drafts with provenance, lifecycle state, EDENA fields, limitations and warning labels. Private Life, Capacity & Career records never enter institution exports, badges or agent context. External release occurs outside TEACH through accountable humans and official systems; TEACH may store only a minimized verified external reference.

Backup defaults to the private store. An institution-partition backup requires separate exact authorization and excludes private and other partitions. Restore starts in quarantine preview and fails closed for corrupt, foreign or wrong-context data. Rollback never revives expired sessions, approvals, agent tokens, source versions or authority receipts.

## Installation, update and removal

1. Read `README-FIRST.md`, `START_HERE.md` and `GIVE-THIS-PACKAGE-TO-HERMES.md`.
2. Verify the archive sidecar, release manifest, source inventory and hashes; run the bundled verifier.
3. Ask Hermes for read-only platform, dependency, port, storage and capability preflight.
4. Review the Implementation Activation Card. Approve each consequential change separately; read-only checks need no mutation approval.
5. Let Hermes copy the immutable DISCOVER baseline into a new target workspace, implement the TEACH application and report truthful checkpoints. The build may take several minutes and several Hermes turns.
6. Keep agents, tools, connectors, memory, shared access, external action and institution workspaces Off unless their exact later activation step is separately approved and tested.
7. Run all 216 build controls, 48 cross-cutting scenarios and 169 canonical checks: 433 execution records in total.
8. Verify a clean extraction, start, stop, backup, restore, update, rollback, overlay removal and uninstall before relying on the package.

Update only from a verified versioned package. Take a verified backup first, preview the migration and review changed permissions and data rules. Overlay removal must preserve the educator foundation and unrelated Nurse AI OS roles. Full uninstall separately confirms application removal, private-data deletion, institution-partition deletion, cached-provider deletion and backup retention or deletion.

## First-run walkthrough

On first launch, guide the owner through these checkpoints:

1. Read and acknowledge the permanent human-accountability, data and external-action boundaries.
2. Confirm the route, role adapter and one active task hat.
3. Review Discover and Soul-derived fields one group at a time; leave uncertainty visible.
4. Choose exactly one primary workspace and confirm the deployment context and data ceiling.
5. Review the inactive catalog: 20 powers, 18 Preview Only workflows, 24 templates and 10 P0 agents.
6. Optionally seed the synthetic starter cards. No real learner, patient, course or institution data is included.
7. Run **Verify Before You Trust**, the synthetic 30-minute AI-citation workshop mission.
8. Open Diagnostics and confirm the actual build/readiness status. Never treat kit verification as runtime proof.

## Quick examples

- **Safe design preview:** “Using only public and fictional material, help me align a 30-minute citation-verification workshop.”
- **Safe feedback rehearsal:** “Create a generic feedback structure for a fictional submission; do not grade or infer anything about a learner.”
- **Safe simulation design:** “Draft objectives, prebrief and debrief questions for a fictional skills-lab case with no patient details.”
- **Human route required:** “Help me list questions for the faculty lead and accessibility reviewer before any release.”
- **Blocked input:** “Analyze these named learners’ submissions and recommend grades.” Stop before echo or transformation and explain the approved human/system route.

## Permanent reminder

AI supports—but does not replace—professional judgment. Hermes and Nurse AI OS hold no clinical, teaching or institutional license and assume no professional accountability. Review every draft before clinical, legal, financial, employment, academic or institutional use. Real-world action may require permissions that sandbox exploration does not provide.
