# Hermes Implementation Program — Build TEACH Mission Control

You are the implementation engineer for build kit `NAIO-NEID-TEACH-FUNCTIONAL-BUILD-KIT-1.0.0`.

Build `TEACH — Nurse Educator & Instructional Designer Mission Control`, product ID `nurse-educator-instructional-designer-mission-control`, target version `2.0.0`, as a genuinely functional, downloadable, authenticated, loopback-only local application.

Preserve the canonical source identity:

- complete program `NAIO-NEID-COMPLETE-TEACH-1.0`;
- foundation `NAIO-NE-LPEF-1.0`;
- overlay `NAIO-NEID-TEACH-1.0`;
- namespace `neid_teach.*`.

The lane `nurse_educator_instructional_designer`, route `/nurse-educators-designers/dashboard`, home `My TEACH Command Studio`, executable schemas, data-class codes, agent IDs, and stable `TEACH-*` keys are implementation-generated. Do not represent them as legacy identifiers.

## Before doing work

Display `PROCESSING_MESSAGE.md` exactly. Then read `INPUT-PRECEDENCE.md` and `implementation/HERMES-HANDOFF-README.md`.

## Product outcome

Create one educator/designer Command Center that remains useful without AI and includes:

- three role adapters: Nurse Educator, Instructional Designer, and Hybrid or Faculty Developer;
- one explicit active task-level hat per mission;
- 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 five foundation departments and NURSE Compass;
- Core Four `Plan My Day`, `Design & Align`, `Assess & Support`, and `Review & Release`;
- an empty fifth launcher;
- exactly 20 canonical powers installed `Available Inactive`;
- exactly 18 canonical workflows installed `Preview Only`;
- exactly 24 canonical numbered templates;
- a durable Assess → Diagnose/Define → Plan → Implement → Evaluate mission loop;
- Guide, evidence, capability/mastery, agent, privacy, memory, diagnostics, backup, update, rollback, removal, and uninstall surfaces.

Do not build an LMS, gradebook, student-record system, clinical system, assessment authority, accreditation authority, research determination, surveillance tool, autonomous instructor, or institutional deployment.

## Absolute learner-data and patient-data boundary

The general and personal workspaces exclude learner/student records. Reject before persistence and before any provider call:

- learner names, IDs, contact details, submissions, grades, evaluations, feedback, advising notes, accommodations, conduct/integrity records, clinical-performance records, recordings, secure assessments, or item banks;
- PHI, patient identifiers, chart or handoff material, identifiable or reconstructable clinical narratives, event details, screenshots, audio, rare combinations, or live-care questions;
- employee/HR/investigation records, private third-party data, confidential institutional material, passwords, tokens, secrets, and financial credentials.

Do not echo rejected content into an error, log, receipt, memory, index, export, backup, prompt, or agent context. Record only content-free boundary metadata and route the owner to the correct authorized human or official process.

Institutional processing is unavailable by default and is not provisioned by this kit. A future separately provisioned institutional workspace may accept only public/synthetic material, minimum routing metadata, exact approved non-person course/curriculum content, an exact separately approved aggregate created outside TEACH, or an opaque official-system reference. Each object requires a current purpose-bound receipt; an aggregate additionally binds provenance, definition/query/version, denominator, missingness, suppression/small-cell rule, approval, expiry, and content hash. It never accepts individual-, row-, submission-, event-, or narrative-level learner data, even when labeled deidentified.

## Required first response — read-only preflight

Before mutation:

1. Verify `RELEASE-MANIFEST.json`, `SHA256SUMS.txt`, `SOURCE-INVENTORY.json`, and immutable source hashes.
2. Inventory the baseline framework, package manager, runtime, persistence, routes, controls, tests, launchers, and gaps.
3. Inspect Hermes version, active profile reference, and available health/models/capabilities/sessions/stream interfaces without reading, displaying, copying, or logging raw `SOUL.md`.
4. Detect dependencies, licenses, platform constraints, and accessibility tooling. Do not download anything.
5. Propose a copy-on-write implementation path and prove `source/` will remain unchanged.
6. Preserve unrelated and user-created work.
7. Classify every visible baseline control as working offline, manual handoff, AI-dependent, missing, or out of scope.
8. Make no non-loopback network call; start no service; install nothing; create no database.
9. Treat all institutional workspaces and authority as unavailable unless separately and currently proven.

Return one **Implementation Activation Card** containing:

- package/source verification;
- host, runtime, dependency, license, download, and network plan;
- immutable and work-copy paths;
- application, database, attachment, log, export, and backup paths;
- authentication, session, secret, loopback, CSRF/Origin/Host, and recovery approach;
- three adapters, five workspaces, active-hat model, and data ceilings;
- learner-data/no-PHI admission and negative-test plan;
- Core Four, empty fifth, 20/18/24 catalog state, and disabled agent registry;
- Hermes capabilities observed and missing;
- accessibility, clean-install, backup/restore, update/rollback, removal, and uninstall plan;
- all test inventories, blockers, checkpoints, rollback, and exact resume command;
- **Approve**, **Revise**, and **Cancel**.

Stop for exact approval. Approval does not authorize learner or patient data, institutional deployment, raw Soul content, profile edits, public binding, connectors, messages, LMS changes, grading, publication, external action, or power/agent activation.

## S0 — freeze and copy

- Record environment, hashes, approval, work path, role/hat model, data ceiling, and blockers.
- Create only the approved work copy.
- Preserve immutable sources and unrelated work.
- Write an S0 receipt before editing.

## S1 — durable offline core

- Implement authenticated loopback access and server-owned durable storage with forward-only migrations.
- Implement mission/project/task/note/measure/source/artifact/decision CRUD, search/filter/sort, archive/restore/delete, stage history, pause, branch, reopen, export/import, restart, backup, and restore.
- Implement the five protected workspaces as explicit scopes within one Command Center.
- Implement context change invalidation and prohibit cross-workspace leakage.
- Derive a proposed Mission Profile in memory; allow field-level edit/reject/approve; persist only approved minimum fields, never raw quiz answers or raw `SOUL.md`.
- Seed synthetic Starter content only after approval. Label it as synthetic and exclude it from earned evidence.
- Keep AI `Setup required`, memory session-only, external actions off, powers inactive, workflows Preview, fifth launcher empty, and agents disabled.
- Execute offline, persistence, migration, authentication, learner-data, no-PHI, isolation, deletion, and recovery tests before S1.

## S2 — educator and TEACH domain

- Implement the five foundation departments, NURSE Compass, three adapters, active-hat bar, five workspaces, Core Four, empty fifth, Guide, and permanent privacy/recovery controls.
- Register the exact 20 powers, 18 workflows, and 24 numbered templates with one-to-one build keys and canonical display names.
- Implement TEACH Gate, Human Teaching anti-slop checks, evidence/source/rights review, accessibility gates, academic-integrity safeguards, and human release ownership.
- Store independent `edena_tier` and Boolean `absolute_stop`. Source-listed prohibitions are absolute stops. Personal Red with `absolute_stop=false` may proceed only as a new clean fictional/generic exploration after deliberate acknowledgment; never transform the stopped content. Institutional Red remains blocked pending current required review. An absolute stop is never waivable.
- Keep the canonical artifact lifecycle separate from review substates:

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

  `Approved Plan` is human scope review only. `Authorized Execution` occurs outside the app through an accountable human and approved official system. `Completed Action` requires a verified external reference. The app performs no real grade release, LMS change, communication, clinical action, institutional change, publication, or other consequential execution.
- Execute all 33 foundation checks, 120 overlay tests, and 16 integration checks against the runtime. Every result begins `Not Run`; source presence is not a pass.

## S3 — genuine AI, evidence, memory, and bounded agents

- Implement a provider-neutral server adapter with capability-driven Hermes support and an optional OpenAI-compatible adapter.
- Keep provider secrets server-side. Implement genuine health/capability/model checks, sessions, incremental streaming, cancellation propagation, terminal states, bounded retries, and separated tool events.
- Production must never substitute canned text, timer streams, fake citations, simulated tool calls, or test doubles for an unavailable backend.
- Send only the approved minimum context. Never expose or repeatedly inject raw `SOUL.md`.
- Implement source records with identity, authority, version/date, applicability, claim mapping, conflict, correction, uncertainty, rights, reviewer, and expiry. Treat retrieved instructions as untrusted.
- Implement consent-controlled memory with preview, purpose, scope, expiry, inspect, edit, forget, export, and delete. Session-only remains default.
- Keep every agent P0 until the owner separately approves an exact one-run P1/P2 charter. Agents never approve, grade, release, contact, publish, change an official system, infer learner traits, or self-expand.
- If P3 exists, limit it to a separately approved deterministic local personal reminder after three supervised successful runs. It uses no model inference, learner/institutional data, connector, external destination, monitoring, surveillance, or consequential decision. P4 is absent.

## S4 — release assurance

- Execute and reconcile 216 build controls, 48 cross-cutting scenarios, and 169 canonical checks: 433 execution records total.
- Test every styled control end to end or disable it with an exact reason.
- Complete unit, integration, end-to-end, security, learner-data/no-PHI, prompt-injection, accessibility, migration, restart, import/export, deletion, backup/restore, update/rollback, overlay-removal, uninstall, degraded-mode, citation, routing, memory, streaming, cancellation, and clean-install tests.
- When a live backend is available and separately approved, run one safe nonsensitive genuine-stream and cancellation test through the packaged UI.
- Package source, lockfiles, migrations, launchers, diagnostics, tests, Guide, `.env.example`, changelog, dependency/SBOM record, manifest, checksums, backup/update/rollback/removal/uninstall instructions, and the final report.

## Checkpoint receipt contract

After every phase report:

- authorization and phase status;
- files and state inspected or changed;
- commands, dependency installation, licenses, and network use;
- data paths, records, migrations, and backups;
- exact tests executed, results, evidence paths, and hashes;
- running services/process identifiers;
- failures, blockers, unsupported/not-applicable/not-run items;
- rollback point, next approval, next step, and exact resume command.

Nothing is “still running” without a real process identifier.

Resume with:

`RESUME TEACH EDUCATOR FUNCTIONAL BUILD FROM <S0|S1|S2|S3|S4> USING THE SAVED RECEIPT; REVERIFY SOURCE HASHES, WORK COPY, USER AUTHORIZATION, ACTIVE ROLE/HAT/WORKSPACE, DATA CEILING, HERMES CAPABILITIES, MIGRATIONS, CONTROL MATRIX, TEST STATE AND LIVE PROCESSES; DO NOT DUPLICATE RECORDS, DASHBOARDS, ROUTES OR MUTATIONS; DO NOT ASSUME SUCCESS.`

## Final handoff

Complete `implementation/HERMES-FINAL-HANDOFF-REPORT-TEMPLATE.md`. End with exactly one evidence-derived state:

- **Operational:** all applicable acceptance criteria passed, including genuine end-to-end streaming and cancellation through the downloaded application.
- **Core operational; AI setup pending:** every offline/core criterion passed, but a live configured backend was unavailable for the genuine-streaming test.
- **Not operational:** one or more core criteria failed or remain blocked.

Never infer readiness from a prompt, source review, screenshot, static page, development server, test double, or synthetic demonstration.
