# TEACH Product Specification

**Build ID:** `NAIO-NEID-TEACH-FUNCTIONAL-BUILD-KIT-1.0.0`  
**Product:** TEACH — Nurse Educator & Instructional Designer Mission Control  
**Product ID:** `nurse-educator-instructional-designer-mission-control`  
**Application version to build:** `2.0.0`  
**Lane:** `nurse_educator_instructional_designer`  
**Route:** `/nurse-educators-designers/dashboard`  
**Namespace:** `neid_teach.*`  
**Home:** My TEACH Command Studio  
**Distributed state:** `not_operational_build_required`

This contract directs Hermes to create and test a real, local Mission Control application from the supplied working DISCOVER v2 implementation reference and the immutable educator/TEACH sources. The distributed ZIP is a verified functional-build kit, not the finished installed application. Source-document completeness and kit integrity are not runtime proof.

## Intended outcome

The target helps a nurse educator or instructional designer coordinate teaching design, accessibility, synthetic assessment preparation, clinical/simulation design, curriculum and program-evidence work, scholarship, faculty development, career goals and sustainable whole-life capacity. It preserves educator voice, learner dignity, human judgment, source and rights integrity, and explicit institutional accountability.

It is not an LMS, gradebook, student-record system, exam bank, clinical decision-support system, accreditation authority, research/ethics service, personnel system, legal service, communications service or autonomous education agent.

## Exact source identity and inventories

- Complete Edition: `NAIO-NEID-COMPLETE-TEACH-1.0`
- Foundation: `NAIO-NE-LPEF-1.0`
- Overlay: `NAIO-NEID-TEACH-1.0`
- Three adapters: Nurse Educator; Instructional Designer; Hybrid or Faculty Developer.
- Five foundation departments, nine records, eleven foundation workflows, five response formats and NURSE Compass.
- Core Four: Plan My Day; Design & Align; Assess & Support; Review & Release. The fifth launcher is empty.
- Twenty TEACH powers, all Available/Inactive at installation.
- Eighteen TEACH workflows, all Preview Only at installation.
- Twenty-four numbered templates.
- Ten build-layer agents, all `PERM-P0 Disabled`.
- Four developmental mastery levels, seventeen domains and seventy-seven criteria.
- 216 build controls + 48 cross-cutting scenarios + 169 canonical checks = 433 execution records, all initially `Not Run`.

## Role and context bind

Every mission binds exactly one adapter, one active task hat, one deployment context, one workspace, one institution/course/program/project partition where applicable, and one data ceiling. A title never grants authority. The Instructional Designer adapter never inherits grading, clinical, accommodation, integrity, curriculum, accreditation or faculty authority. A Hybrid user must rebind on every hat change; least privilege wins.

## 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

The private store is physically separate from every institution-approved store. Each institution/course/program/project is isolated. Search, cache, model context, memory, agents, badges, exports and backups cannot silently combine stores. Private-life detail never enters institutional analytics, badges, agent context or institutional exports.

## Deployment contexts

### Private Educator/Designer Mode

This is the only installed default. It accepts public, synthetic and minimum educator-owned nonsensitive data. It has session only (`session_only`) memory; connectors, shared access, external actions, release and background automation are off. It contains no institution authority.

### Separately Provisioned Institution-Approved Education Workspace

This context is absent by default and requires a distinct authenticated runtime bind for one institution/course/program/project. Current human receipts must cover role and task authority, purpose, allowed fields/classes, source and rights, platform/vendor/model, privacy, security, accessibility, records, retention/deletion, audit and release ownership. A Mission Profile, prompt, setting, badge or agent cannot create this authority.

The base target still accepts no learner-record payload. A future learner-record or assessment-processing function requires a separate purpose-built governed module, schema, threat model, security testing and release decision.

## Closed data classes

| Class | Permitted meaning |
|---|---|
| `TEACH-DATA-0` | Public, authoritative, nonsensitive source with version, applicability and rights tracked. |
| `TEACH-DATA-1` | Unmistakably synthetic/fictitious learner work and clinical/simulation cases. |
| `TEACH-DATA-2` | Minimum educator/designer-owned nonsensitive planning, preference, capacity, career and draft data; 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, bound to source/version/rights/purpose/approval/expiry/hash. |
| `TEACH-DATA-A` | Exact approved aggregate evidence 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. Reject before echo, persistence, logs, indexing, memory, backup, export, badges or AI. |

Learner records, submissions, grades/evaluations, accommodations, conduct/integrity/complaints, secure tests/answers/item banks, employee records, human-participant data, PHI/patient stories/live care, secrets, restricted institutional content, person profiling/ranking/surveillance, and purportedly “deidentified” row/person/narrative content are `TEACH-DATA-X` in this build.

## Mission workflow

Each mission visibly loops through Assess → Diagnose or Define → Plan → Implement → Evaluate. Users may pause, revise, return upstream, branch and start another iteration. Assess distinguishes verified facts, owner-provided information, assumptions and unresolved questions. Plan compares benefit, feasibility, time, burden, cost, ethics, rights, accessibility and risk. Implement creates local drafts, checklists, prototypes and handoff packets only. Evaluate records intended, partial, null, adverse and unknown results without inventing impact.

Artifact truth uses exactly:

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

`Approved Plan` is human scope/content review only. `Authorized Execution` occurs outside TEACH through an accountable human or official system. `Completed Action` requires a minimized verified external reference. TEACH performs no LMS, gradebook, message, email, calendar, course, assessment, simulation, publication, accreditation or institutional write. TEACH review states such as Awaiting accessibility review remain a separate axis.

## EDENA and TEACH Gate

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

- Personal Green/Yellow proceeds only inside the permitted class and review boundary.
- Personal Orange stays generic/synthetic and names the responsible human route.
- Personal Red stops the original request. Only when `absolute_stop=false`, after deliberate acknowledgment, may the owner start a new clean fictional/generic sandbox. Stopped content is never transformed or carried forward.
- Institutional Red blocks operational progression until current human/policy authorization is verified; it never creates an in-app action.
- `absolute_stop=true` is nonwaivable everywhere.

Apply the TEACH Gate—Target, Evidence, Authority, Checks, Human—before persistence, import, AI, memory, artifact creation, agent execution, export and proposed handoff.

## Agent permissions

All ten agents start P0/disabled. P1 and P2 are exact, expiring, one-run draft/read-only ceilings with one-use tokens and immutable charters. P3 is permitted only as a separately approved deterministic local personal reminder after three supervised successes; it uses no model, course/learner/institution data, connector, external destination, monitoring, assessment, surveillance, decision or release. P4 is absent. No self-activation, self-expansion, hidden retry, recursion or background work.

## Capabilities and badges

Levels are Basic, Intermediate, Advanced and AI Agent Orchestration Master. Evidence must be observable, adopted/evaluated and minimized. Badges do not prove CE credit, teaching or clinical competence, certification, licensure, appointment, promotion, accreditation, institutional approval, access or permission. They unlock nothing. Evidence excludes learner/patient/person payload, secure assessments, confidential institution text and private-life detail. Correction, deletion, expiry, supersession or authority change causes recomputation, suspension, downgrade or revocation.

## Required screens

- First Run and processing message
- My TEACH Command Studio
- Start a Mission and five-stage loop
- Workspace switcher and persistent role/hat/context/data/authority bar
- TEACH Library for 20 powers, 18 workflows and 24 templates
- Evidence, Sources & Rights
- Agent Center with Pause All and Kill
- Memory & Privacy
- Capabilities & Mastery
- Guide and first-run walkthrough
- Diagnostics, Backup, Update, Rollback, Overlay Removal and Uninstall

All screens require keyboard operation, screen-reader semantics, non-color status meaning, 200% zoom/reflow, contrast, reduced motion, plain language, printable/manual degraded views, exact disabled reasons and no fake progress.

## Processing message

> **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 is milestone-based, never simulated. A failed or interrupted step returns a truthful checkpoint and exact safe resume instruction.

## Hermes Implementation Activation Card

Before any mutation, dependency installation, service start, profile change or package build, Hermes must show one card containing:

- exact source and destination paths;
- proposed files and commands;
- platform/dependency status;
- data classes and prohibited inputs;
- role, hat, context and authority assumptions;
- connectors, network, tools and permissions requested;
- expected duration and visible checkpoints;
- backup, rollback and deletion path;
- verification plan and evidence locations;
- controls unavailable in the current environment;
- a separate approval checkbox for each consequential change.

Read-only preflight needs no mutation approval. Work pauses for user approval after the card. A later approval never silently expands the card.

## Definition of done

Hermes may call the future target operational only after it builds a real local application, executes applicable controls on the exact package, demonstrates genuine Hermes capability/stream/cancel behavior or a truthful unavailable state, passes security/privacy/accessibility/backup/recovery/fresh-extraction tests, produces a clean versioned archive with manifest/checksums/SBOM, and supplies evidence for every status claim. Until then, the only honest state is `not_operational_build_required` or a narrower evidence-derived partial state.
