# TEACH Nurse Educator & Instructional Designer Mission Control — Reference Architecture and Data Model

**Target product:** `TEACH — Nurse Educator & Instructional Designer Mission Control`  
**Product ID:** `nurse-educator-instructional-designer-mission-control`  
**Build-layer lane:** `nurse_educator_instructional_designer`  
**Build-layer route:** `/nurse-educators-designers/dashboard`  
**Home label:** `My TEACH Command Studio`  
**Canonical source namespace:** `neid_teach.*`  
**Target application version:** `2.0.0`  
**Readiness at build-kit assembly:** `not_operational_build_required`

This document is a binding implementation contract, not evidence of a completed application. The immutable domain authority remains complete program `NAIO-NEID-COMPLETE-TEACH-1.0`, foundation `NAIO-NE-LPEF-1.0`, and overlay `NAIO-NEID-TEACH-1.0`. The route, lane, storage model, `TEACH-DATA-*`, `TEACH-AGT-*`, permission levels, schemas, and database tables are build-layer decisions and must be labeled accordingly.

## 1. Frozen product contract

Hermes must preserve:

- exactly three role adapters: **Nurse Educator**, **Instructional Designer**, and **Hybrid or Faculty Developer**;
- the five foundation departments and NURSE Compass;
- one Command Studio and one visible EDENA model;
- the TEACH Gate: Target, Evidence, Authority, Checks, Human;
- the Core Four: **Plan My Day**, **Design & Align**, **Assess & Support**, and **Review & Release**;
- one empty optional fifth launcher;
- exactly 20 optional powers, all `Available Inactive` after installation;
- exactly 18 workflows, all `Preview Only` after installation;
- exactly 24 templates;
- 33 foundation checks, 120 TEACH overlay tests, and 16 integration checks: 169 canonical checks;
- 216 build-layer controls and 48 cross-cutting scenarios, producing 433 total execution records with the canonical checks; and
- a private, synthetic, no-PHI, no-learner-record, session-only, Manual/Assist/Preview default.

The base target is not an LMS, gradebook, student-record system, secure assessment platform, clinical system, simulation controller, accreditation system, research-determination service, personnel system, surveillance system, publication service, or institutional execution engine.

## 2. Non-negotiable architectural invariants

1. The application remains useful without AI or network access.
2. One authenticated owner has exactly one active role adapter, task-level hat, workspace, deployment context, institution-or-Personal context, purpose, authority ceiling, and data ceiling per mission.
3. A title, course assignment, file, platform access, committee role, or model inference never proves authority.
4. Private whole-life data and institutional education data are stored separately and never silently joined.
5. The base application never accepts learner-record or assessment payloads. It may retain only an opaque official-system reference under `TEACH-DATA-R`.
6. Clinical, skills-lab, and simulation content is synthetic only. Patient information and live-care questions are rejected before persistence and AI.
7. Every consequential artifact follows the exact eight-state lifecycle defined in Section 9.
8. All teaching, release, grading, contact, posting, submission, publication, institutional change, and other external execution occurs outside TEACH through accountable humans and official systems.
9. Every agent installs `PERM-P0 Disabled`. P1 and P2 are expiring one-run permissions. P3 is a deterministic local personal reminder only. P4 is absent.
10. Readiness comes only from executed evidence against the final packaged artifact. Source presence, screenshots, mocks, and documentation do not constitute Passed tests.

The exact ten-agent registry is `TEACH-AGT-01` through `TEACH-AGT-10`; definitions and routing are controlled by `EDUCATOR-Agent-Team-and-Routing.md`.

## 3. Recommended local architecture

```text
Browser UI
  │ same-origin authenticated API and genuine streamed events
  ▼
Loopback application server (127.0.0.1 by default)
  ├── authentication, rotating sessions, CSRF, Origin/Host and size/rate controls
  ├── identity, role, hat, workspace, deployment-context and authority guard
  ├── pre-persistence data admission service
  ├── EDENA + absolute_stop + TEACH Gate policy service
  ├── repository router (deny by default)
  │    ├── private owner store
  │    └── one isolated store per provisioned institutional workspace
  ├── missions, NURSE Compass, projects, tasks, artifacts and evaluation
  ├── five protected workspace services
  ├── TEACH catalog and lifecycle service
  ├── evidence, source, rights and provenance service
  ├── capability-evidence service
  ├── AI backend adapter
  │    ├── capability-discovered Hermes adapter
  │    └── optional explicitly configured compatible adapter
  ├── deterministic agent router, one-run coordinator, Stop and Kill
  ├── consent-controlled structured memory
  ├── backup, restore, update, rollback, removal and uninstall
  └── content-free audit, governance and diagnostic receipts
```

The browser is not a trust boundary. The server revalidates authentication, owner, active role/hat, workspace, deployment context, institution/course/project bind, purpose, data class, authority receipt, policy version, `edena_tier`, `absolute_stop`, TEACH Gate, object revision, permission, and expiry on every mutation, import, retrieval, model call, memory operation, agent run, artifact transition, export, backup, and cross-record link.

Browser storage may hold only nonsecret display preferences and an expiring safe cache. It may not be the authoritative store for credentials, missions, approvals, data-class decisions, evidence, memory, institutional binds, agent permissions, or artifact state.

## 4. Storage and partition isolation

Use at least:

1. `educator-private.sqlite` for owner-private life, capacity, career, public/synthetic teaching design, and other permitted private records; and
2. one `education-<opaque-workspace-id>.sqlite` for each separately provisioned Institution-Approved Education Workspace.

If encryption at rest is offered, it must be genuinely implemented and verified. Do not imply that SQLite or a password automatically encrypts content.

A small registry may hold only opaque store identifiers, safe labels, schema version, coarse health, and path references. It must not hold learner data, course content, private-life detail, aggregate values, source text, artifacts, or agent prompts.

No SQL query, search index, cache, embedding store, prompt assembly, model session, memory retrieval, analytic job, badge calculation, backup, export, or agent route may join private and institutional stores. Switching context must:

1. close the prior repository handle;
2. clear scoped caches and pending retrieval;
3. rotate a context nonce;
4. invalidate incompatible drafts, approvals, agent charters, and memory consent;
5. open only the selected store; and
6. create a content-free context-switch receipt.

Private backup covers only the private store. Each institutional backup covers one authorized institutional store. A combined or cross-context backup is prohibited.

## 5. Identity, adapters, task hats, and contexts

### 5.1 Exact role adapters

- `nurse_educator` — may use only current, documented teaching, assessment, clinical/simulation, supervision, design, and release authority for the exact task. Final grades, feedback release, progression, remediation, discipline, accommodation, integrity findings, clinical clearance, competency, curriculum approval, accreditation determination, and institutional commitments remain authorized-human actions outside the app.
- `instructional_designer` — may analyze, design, prototype, audit, compare, document, and recommend. Technical access or design responsibility does not confer faculty, grading, clinical, accommodation, integrity, curriculum, accreditation, research, or release authority.
- `hybrid_faculty_developer` — must select a task-level hat for every mission and consequential artifact. A hat change triggers a new authority/data/context evaluation. Least privilege wins.

Task hats may describe classroom or online faculty, clinical instructor, simulation or skills-lab educator, curriculum/program coordinator, faculty developer, scholarship author, or personal/career planner. They are descriptive selectors, not authority grants.

### 5.2 Exact five protected workspaces

1. **Life, Capacity & Career** — private NURSE Compass, workload, protected time, recovery/capacity categories, career, scholarship, leadership, and whole-life goals. Personal details never enter institutional views, badge evidence, institutional analytics, or default agent context.
2. **Teaching, Learning Design & Accessibility** — outcome alignment, learning experiences, course journey, modality, cognitive load, active learning, accessibility, inclusion, public/OER content, and release preparation. It accepts only permitted public, synthetic, owner-private, or exact approved non-person course content.
3. **Assessment, Feedback & Learner Support** — synthetic assessment, blueprint, rubric, calibration, feedback, AI-use rule, and support-conversation design. The base product retains only opaque official-system references; learner submissions, grades, evaluations, identifiers, accommodations, conduct, complaints, and integrity records do not enter.
4. **Clinical, Skills-Lab & Simulation** — synthetic cases, objectives, prebrief, roles, equipment, cues, stop rules, accessibility, observation-tool design, and human-led debrief preparation. It never processes patient data, live care, learner evaluation payloads, or competence/clearance decisions.
5. **Curriculum, Program Evaluation, Scholarship & Faculty Development** — versioned curriculum/competency/accreditation maps, source and rights records, exact approved aggregates, program-evaluation preparation, AI-literacy/faculty-development designs, scholarship, portfolio, and leadership. It cannot determine accreditation, compliance, research/ethics status, authorship, legal sufficiency, or outcome causality.

Institution, program, course/cohort, clinical/simulation, faculty-development, scholarship, personal/career, and public are nested task contexts inside the five workspace families. An institutional workspace is further partitioned by one institution, program, course/cohort or project, purpose, and authority bind.

### 5.3 Per-request context envelope

Every request carries:

- `owner_user_id`;
- `role_adapter` and `task_hat`;
- `workspace_family`;
- `deployment_context`;
- `institution_or_personal_context`;
- `institution_workspace_id` or `none`;
- `program_course_cohort_or_project_id` or `none`;
- `purpose`;
- `data_class`;
- `authority_snapshot_id`;
- `policy_snapshot_id`;
- `retention_policy_id`;
- object revision; and
- request/context nonce.

Missing, unknown, stale, expired, contradictory, or materially changed context fails closed for persistence, AI, memory, agent use, artifact advancement, export, and external-reference reconciliation.

## 6. Two deployment contexts

### 6.1 Private Educator/Designer Mode

This is the only context available after ordinary installation. It accepts `TEACH-DATA-0`, `TEACH-DATA-1`, and screened `TEACH-DATA-2`. It may create generic or synthetic drafts and private plans. It cannot process institution-confidential content, learner data, secure assessments, patient information, real clinical content, official records, or institutional aggregate evidence.

Private approval never provisions institutional access or authority.

### 6.2 Separately Provisioned Institution-Approved Education Workspace

This context is unavailable by default. Provisioning occurs outside ordinary installation and requires an authenticated runtime bind covering:

- exact legal institution, program/course/project, purpose, user, role, task hat, and decision ceiling;
- approved platform, vendor, model, deployment, agreements, and network boundary;
- allowed data classes, exact sources/fields, volumes, and rights;
- privacy, security, accessibility, student-record, academic, clinical, records, copyright, research, legal, HR/labor, and IT owners as applicable;
- access, authentication, encryption, logging, retention, deletion, correction, incident, downtime, backup, export, and revocation rules;
- external release owner and official system; and
- effective date, expiry, renewal, and revocation.

The base application remains non-person, reference, and aggregate level even in this context. It is not an institution-approved student-record processor merely because an institutional workspace exists.

## 7. Closed data classification

- `TEACH-DATA-0` — public authoritative nonsensitive information. Record owner/publisher, title, canonical reference, version/date, applicability, rights, retrieved date, limits, corrections, and expiry.
- `TEACH-DATA-1` — unmistakably synthetic or fictional fixtures, simulated learner work, synthetic clinical/simulation cases, and synthetic measures. Label at every surface and never present as real.
- `TEACH-DATA-2` — minimum educator/designer-owned nonsensitive private planning, preferences, capacity categories, career goals, source notes, and drafts. No patient, learner, employee, third-party, confidential-institution, secure-assessment, health-narrative, or employment-dispute detail.
- `TEACH-DATA-M` — minimum business routing metadata: opaque institution/program/course/project identifiers and an authorized human's name, role, and approved work contact when required. It is not learner, workforce, or analytic data and is excluded from agent analysis.
- `TEACH-DATA-C` — exact separately approved non-person institutional/course/curriculum content created outside TEACH, such as outcomes, competency statements, generic rubrics, policies, course specifications, or approved materials. Bind source/version, rights/license, local adoption, purpose, owner, approval, expiry, and content hash. Exclude secure assessments, answers, learner content, and confidential person records.
- `TEACH-DATA-A` — exact separately approved aggregate learner/program evidence created outside TEACH. Bind exact definition/query/version, denominator, missingness, provenance, suppression/small-cell rule, purpose, steward, access, retention/deletion, approval/expiry, release owner, and content hash. It contains no row, learner, person, submission, event, narrative, or reidentifiable rare combination.
- `TEACH-DATA-R` — opaque official-system reference only for a learner, assessment, grade, feedback, support, clinical-evaluation, release, or other official record. It contains no payload, name, student ID, score, excerpt, narrative, direct URL token, or reversible identifier and is used only for human reconciliation.
- `TEACH-DATA-X` — prohibited or unclassified content. Reject before persistence, logs, indexing, embeddings, memory, backup, export, badges, analytics, model forwarding, or agent routing.

Claims such as `approved`, `public`, `synthetic`, `anonymous`, `deidentified`, `redacted`, or `aggregate` must be verified; they do not grant permission. Direct learner/assessment payload is `TEACH-DATA-X` in the base application. A future purpose-built learner-record module requires separate schemas, threat model, institutional approval, release ledger, and tests; it cannot be enabled by prompt or feature flag.

## 8. Persistent domain model

Use opaque UUIDs, UTC timestamps, explicit schema versions, foreign keys, optimistic revisions, append-only events for consequential changes, and explicit archive/deletion states. Every mutable record includes owner, role/hat, workspace, deployment context, institutional partition, purpose, data class, policy/authority snapshots, retention, created/updated times, revision, and status.

### 8.1 Platform and context

- `app_meta`, `schema_migrations`;
- `local_users`, `credential_verifiers`, `sessions`;
- `mission_profiles`, `profile_field_provenance` — approved derived fields only; no raw quiz answers or raw `SOUL.md`;
- `workspace_registry`, `role_contexts`, `authority_profiles`;
- `institution_workspace_bind_receipts`, `context_switch_receipts`;
- `policy_snapshots`, `retention_policies`, `data_classification_receipts`.

### 8.2 Mission and work management

- `missions`, `mission_cycles`, `mission_stages`;
- `projects`, `goals`, `milestones`, `tasks`, `task_dependencies`;
- `facts`, `user_statements`, `assumptions`, `unknowns`, `risks`, `safeguards`;
- `measures`, `evaluations`, `decisions`, `human_routes`;
- `artifacts`, `artifact_versions`, `artifact_reviews`, `external_action_references`;
- `starter_seed_versions`, `starter_records`, `starter_adoptions`.

### 8.3 Educator and TEACH records

- `educator_profiles`, `north_stars`, `ninety_day_results`;
- `capacity_plans`, `minimum_modes`, `reentry_plans`, `support_maps`;
- `teaching_design_briefs`, `alignment_maps`, `course_journey_maps`;
- `accessibility_reviews`, `inclusion_reviews`, `human_teaching_reviews`;
- `synthetic_assessment_blueprints`, `synthetic_rubric_calibrations`, `generic_feedback_patterns`;
- `learner_support_rehearsals`, `official_system_references`;
- `synthetic_clinical_simulation_briefs`, `simulation_release_preparations`;
- `curriculum_competency_maps`, `accreditation_evidence_maps`;
- `aggregate_evidence_receipts`, `aggregate_sensemaking_briefs`;
- `source_records`, `claim_source_links`, `rights_license_records`, `correction_events`;
- `scholarship_plans`, `portfolio_evidence_maps`, `faculty_development_designs`;
- `neid_teach.power_states`, `neid_teach.workflow_previews`, `neid_teach.template_instances`.

### 8.4 Governance and agent records

- `edena_assessments` with independent `edena_tier` and `absolute_stop`;
- `teach_gate_results`;
- `artifact_transition_receipts`, `human_review_receipts`;
- `agent_definitions`, `agent_charters`, `agent_run_events`, `agent_run_receipts`;
- `memory_consents`, `memory_items`, `memory_events`;
- `capability_models`, `capability_evidence`, `capability_reviews`, `capability_events`;
- `audit_events`, `pause_kill_events`, `recovery_receipts`.

Audit and index records contain minimum IDs, versions, classifications, hashes, decisions, and timestamps—not prohibited or private payloads.

## 9. Mission loop and exact artifact lifecycle

Every mission supports pause, revision, branch, return to an earlier stage, evaluation, reopening, and a new cycle:

1. **Assess** — identify the goal, role/hat, workspace/context, authority, permitted data, sources, constraints, capacity, stakeholders, verified facts, owner statements, assumptions, and unknowns.
2. **Diagnose/Define** — frame the educational need, design problem, opportunity, decision, or question without diagnosing or profiling a person.
3. **Plan** — compare options by learning value, evidence, feasibility, workload, accessibility, inclusion, integrity, clinical safety, rights, cost, time, reversibility, authority, risk, and whole-life alignment.
4. **Implement** — create local tasks, questions, drafts, synthetic prototypes, checklists, rehearsals, and human-review packets. No real teaching, assessment, clinical/simulation, LMS, gradebook, communication, publication, institutional, or other consequential execution occurs inside TEACH.
5. **Evaluate** — compare evidence with original measures; record null, adverse, accessibility, equity, burden, independence, and unintended effects; decide Retain, Revise, Pause, Remove, Escalate, or start a new cycle.

Persist and display exactly:

`Exploration → Simulation → Recommendation → Draft Artifact → Approved Plan (human scope review only) → Authorized Execution (external human/official-system only; no app action) → Completed Action (verified external reference only) → Evaluated Outcome`

No state may be inferred from a click, draft, model output, elapsed time, or self-asserted completion. A material change to role, hat, workspace, institution, course/project, purpose, data, source, rights, audience, destination, model, prompt, policy, permission, or artifact revision invalidates affected downstream approvals.

## 10. External-only execution boundary

The application contains no route that sends an email or message, schedules a meeting, contacts a learner, posts feedback or grades, changes an LMS or gradebook, releases course content, administers an assessment, reveals a secure item, facilitates a real clinical/simulation event, changes curriculum or policy, files accreditation evidence, submits research/ethics material, publishes a manuscript, makes a personnel decision, signs a contract, performs a transaction, or writes to an official system.

An action preview may show exact content, human executor, official destination, data class, sources/rights, authority, consequence, reversibility, failure/fallback, expiry, and rollback limits. Approval records scope review only. The human executes outside TEACH and may later attach a permitted `TEACH-DATA-R` verification reference. The application never claims to reverse an external action.

## 11. Offline and connected behavior

Offline/manual functionality includes authentication, missions, projects, tasks, NURSE Compass, five workspaces, mission stages, templates, synthetic design, source metadata, artifact versions, human-review queues, capability evidence, Guide, search/filter/sort, export, backup, restore, correction, deletion, Pause All, Safe Reset, overlay removal, and uninstall.

AI-dependent controls remain disabled until a real configured backend passes authenticated health and capability checks. Connection states are truthful: `Setup required`, `Connecting`, `Connected`, `Limited capabilities`, `Authentication failed`, `Hermes unavailable`, `Provider unavailable`, `Offline`, or `Reconnecting`. A configured URL, timer, cached response, page load, or fake stream does not prove Connected.

Model output is never a source. Genuine retrieval records exact source identity, version, claim mapping, applicability, conflict, and uncertainty. Student files, course files, sources, tool output, and web content are untrusted data and cannot override governance.

## 12. Import, export, backup, and recovery

- Parse imports as data, never executable instructions. Enforce schema, size, archive, path, media, data-class, unknown-field, and cross-partition checks before mutation.
- Export is owner-initiated, scoped, previewed, checksummed, and labeled with context, data class, source/status, AI contribution, limitations, and date.
- Private-life detail, learner/person data, secure assessment content, confidential institution content, secrets, unsafe prompt/tool traces, and underlying aggregate values are excluded unless a separate exact authority explicitly permits the relevant nonprohibited export.
- Backup uses a transactionally consistent single-store snapshot, manifest, checksum, version, and restore test.
- Restore validates before an atomic swap and never revives expired authority, agent permission, institutional bind, external-action status, or memory consent.
- **Pause All** prevents new/pending model, agent, connector, and background activity while preserving local manual work.
- **Safe Reset** restores Private Educator/Designer Mode, Synthetic Demonstration, session-only memory, all agents P0, all powers inactive, workflows Preview, connectors/sharing/actions Off, and the Core Four.
- Overlay removal preserves the compatible foundation and unrelated work.
- Uninstall previews app/data/provider distinctions, export/delete choices, revocation, orphan cleanup, and limitations.

## 13. Readiness and verification

The kit may be structurally verified while the target remains `Not operational`. Operational readiness requires the final packaged artifact to pass all applicable controls, including clean install, authentication, restart persistence, migration, context isolation, learner/PHI rejection, accessibility, offline mission completion, genuine Hermes stream and cancellation where configured, source integrity, agent Stop/Kill, backup/restore, reset, removal, and uninstall.

Allowed final states are:

- **Operational** — all criteria passed, including a genuine end-to-end streamed response through the packaged UI;
- **Core operational; AI setup pending** — all offline/core criteria passed, but no live configured backend was available for genuine-stream verification; or
- **Not operational** — one or more core criteria failed or remained Not Run, Blocked, Partial, Unknown, or Unsupported.

Institution-approved education-workspace readiness is reported separately and is never implied by personal application readiness.
