After your SOUL files and Hermes setup

Your role pack comes next—not first.

Choose the English-language folder that fits one current role or relationship to nursing. If you occupy several roles, map them as separate contexts first in the browser-local Switchboard preview. Downloading either a package or using the preview changes no Hermes profile.

No PHI. No automatic installation. No role verification by download. No connectors, cron jobs, memory, or external actions are enabled.

Our Intent

Nurse AI OS is here to steward AI into nursing practice.

Nurse AI OS is not a replacement for anything you already belong to. Not your unit, not your school, not your professional organization, not your license.

We are not here to compete with existing nursing programs — we’re here to strengthen them.

We are not here to make you rich. Wealth is not the point; integrity is. If value follows good work, good. It follows — it does not lead.

And we are not here to pull you away from the bedside. The opposite. Your clinical practice is the source of your authority. Without it, none of this means anything.

What we are here to do: steward the arrival of AI into nursing practice, so that it happens with nurses at the table rather than around us — and to show, by how we conduct ourselves, what ethical and responsible influence actually looks like.

Stewardship, not disruption. Influence, not extraction.

What your Hermes receives

SOUL, Mission Control, and MCP do three different jobs

Your approved SOUL tells Hermes who it serves: your mission, role constellation, working preferences, learning direction, memory choices, governance boundaries, and decisions that must remain yours. It personalizes assistance; it does not verify credentials or grant authority.

Your role Mission Control turns intention into governed work: priorities, projects, learning plans, reusable workflows, approval queues, evidence, and measurable progress organized for one bounded role context.

An optional MCP companion defines what Hermes may eventually reach: selected files, knowledge sources, calendars, documents, or other tools under least privilege. The published companions are inspection-only candidates: every server remains blocked, disabled, and tool-denied until its own supply-chain, privacy, scope, credential, rollback, and human-approval gates are complete.

Giving files to Hermes is not activation. Hermes must inspect the SOUL, role build kit, and MCP companion as separate governed layers. Downloading or handing over a ZIP does not import a SOUL, build Mission Control, install a profile, authenticate, connect, remember, schedule, send, publish, or act.

The safe order

Finish the foundation before adding the role overlay

Complete your SOUL files

Review the values, boundaries, spheres, voice, and goals that Nurse AI OS should respect.

Complete Hermes setup

Establish your private workspace, no-PHI boundary, approvals, and safe recovery path.

Map context, then choose one pack

A nurse may hold several roles. Use a separate Switchboard dashboard for each context or assignment, then treat any package installation as its own governed decision.

Download and inspect

For a self-install build kit, give Hermes the complete ZIP and open README-FIRST.md. For another role package, open 00-READ-FIRST.md. Downloading, opening, or unzipping does not install anything.

Request review or preflight first

Lane 05 requires review before changes. Self-install lanes 01, 02, 03, 04, and 06 require package verification, read-only preflight, and the lane's exact Implementation Activation Card.

Humans approve changes

Approve, revise, defer, or reject the exact proposed scope. Role selection never creates authority.

One person, several legitimate roles

Use the Switchboard before combining hats

The browser-local architecture preview supports separate dashboards for facilities, departments, schools, committees, shifts, assignments, personal learning, and community work. It also includes draft role entries for Nurse Informaticist, Medico-Legal / Legal Nurse Consultant, Nurse AI Agent Orchestrator, and Nurse Community Organizer-Developer—plus additive DISCOVER, FUTURE, BUILD, GOVERN, ORGANIZE, and ORCHESTRATE capabilities.

Preview only: it does not install, merge, activate, or authorize any role package. Role selection does not verify licensure, certification, enrollment, employment, appointment, assignment, community mandate, or institutional permission.

Open the Switchboard preview →

Six English post-setup lanes

Download the package for your role

Review-first lane 05 contains a role-specific Hermes program and guide, reference-only SuperPowers documents, a machine-readable manifest, review instructions, and checksums. Lane 01 publishes the Nursing Student and Assistant FUTURE self-install build kit with 136 canonical compatibility checks and 349 required execution records. Lane 02 publishes the Staff Nurse and Quality Contributor SHIFT self-install build kit with 176 canonical compatibility checks. Lane 03 publishes the Nurse Leader and Manager LEAD self-install build kit with 113 canonical checks. Lane 04 publishes the Nurse Educator and Instructional Designer TEACH self-install build kit with 169 canonical checks and 433 required execution records. Lane 06 publishes the USA-only NP WINGS self-install build kit with 146 canonical checks and 410 required execution records.

01 · Nursing Student & Nursing Assistant Hermes Build Kit

Nursing Student & Nursing Assistant Complete AI OS with FUTURE SuperPowers

For a nursing student, nursing assistant, or Bridge learner who wants one governed learning-and-life foundation, one FUTURE Command Center, and eighteen optional SuperPowers—without replacing faculty, preceptors, supervising nurses, supervisors, verified role boundaries, academic rules, or the learner's own judgment.

Before you build: downloading, selecting, opening, or unzipping changes nothing. This is a transparent self-install Hermes build kit—not an installed or operational application. Give Hermes the complete ZIP. Hermes must verify the manifest, checksums, source provenance, local environment, existing work, data boundaries, and rollback plan in read-only preflight; then show one exact Implementation Activation Card with APPROVE, REVISE, and CANCEL. Without approval of that exact card, Hermes must make no installation mutation.

Substantial local build: after approval, Hermes creates a copy-on-write implementation workspace, preserves the immutable source and compatible work, establishes the learner foundation first, and adds the FUTURE specialization. The target contract contains 24 foundation, 96 FUTURE overlay, and 16 integration checks—136 canonical compatibility checks—plus 169 control tests and 44 cross-cutting scenarios, for 349 required execution records. Every written result begins Not Run; source presence is not proof it passed.

Three protected pathways: Nursing Student, Nursing Assistant, or Bridge. Bridge keeps academic and employment contexts separate. Pathway selection does not verify enrollment, certification, employment, scope, delegation, supervision, competence, or institutional permission. A nursing-assistant title never creates independent nursing or clinical decision authority.

Several visible Hermes turns may be normal. Every phase requires a checkpoint receipt and any continuing process requires a real identifier. All eighteen optional FUTURE SuperPowers remain Available Inactive; all ten suggested agents remain PERM-P0 Disabled; workflows remain Preview Only; connectors, shared access, external actions, schedules, new persistent memory categories, and background automation stay off. A private build does not authorize school, clinical-site, employer, community, or organizational deployment.

Release integrity: the kit is deterministically rebuilt from the complete tracked public-safe source tree and verified against both the package directory and outer ZIP. SHA-256: b95b413fc25f990f3505fcf7af81c2c483a62da2150f4f77b371ff847b173e76.

Why Nurse AI OS matters here: it helps the learner build disciplined AI habits before clinical authority is at stake. The approved SOUL gives Hermes learning preferences, goals, academic-integrity rules, memory choices, and red lines. FUTURE Mission Control turns those commitments into study plans, concept practice, simulation preparation, milestones, and portfolio evidence.

Optional MCP companion: the Study Coach profile is a separate artifact for the Nursing Student pathway only—not automatically Nursing Assistant or Bridge. If later activated through every separate gate, it could let Hermes work with approved personal learning notes, bounded files, calendar, documents, and drive content instead of repeated copy-and-paste. MCP connectors remain disabled with zero tools; activation remains blocked pending a complete transitive lock and lock-consuming runtime; profile installation and every connector require a separate activation card and fresh approval. Verify SHA-256 before extraction →

ZIP · exactly 6,520,918 bytes (approximately 6.52 MB) · English · self-install Hermes build kit · not operational—local build required

Download FUTURE Build Kit → Download inactive Study Coach profile →

02 · Staff Nurse & Quality Contributor Hermes Build Kit

Staff Nurse & Quality Contributor Complete AI OS with SHIFT SuperPowers

For a Direct-Care Staff Nurse, Unit Champion, Preceptor, Shared-Governance Member, chartered Staff-Nurse QI Project Lead, or multi-employer nurse who wants governed life, practice, communication, learning, career, and quality-preparation support—without turning a private workspace into an EHR, event-report system, peer-review repository, quality-data platform, clinical authority, staffing system, personnel system, surveillance tool, or institutional deployment.

Before you install: downloading, selecting, opening, and unzipping change nothing. This is a self-install Hermes build kit, not the already-installed application. Installation begins only after you give Hermes the ZIP, complete the read-only preflight, review the exact Implementation Activation Card, and explicitly approve that exact card. Without that approval, Hermes must make no installation changes.

Substantial build: after approval, Hermes must verify the manifest and checksums, create an implementation work copy, install dependencies only after approval, build the Staff Nurse foundation first, bind the SHIFT overlay, and validate the Trust Shield, SHIFT Core, Command Center views, 18 workflows, 25 templates, 10 disabled agents, and twenty optional SuperPowers as an inactive overlay. The internal contract preserves the canonical 40 foundation checks, 120 SHIFT overlay checks, and 16 integration checks—176 canonical checks, with 264 explicit target rows and 440 required execution records. Compatible work must be preserved and all twenty optional SHIFT SuperPowers remain inactive.

Four authority adapters: Direct-Care Staff Nurse; Unit Champion, Preceptor, or Shared-Governance Member; Chartered Staff-Nurse QI Project Lead; or Hybrid / Multiple-Employer. Selection verifies no identity, employment, licensure, competence, assignment, delegation, supervision, quality appointment, sponsor authority, institutional access, or data permission. Access is not authority; switching contexts triggers new authority and data checks.

Private Personal Mode is the default. Initial readiness is not operational—build required. Real organizational quality work requires a separately provisioned Institution-Approved Quality Workspace, current human QI/EBP/evaluation/research determination, sponsor, charter, data-steward receipt, aggregate or properly deidentified data, small-cell controls, named change and release owners, and auditability. Nothing continues in the background; connectors, shared access, external actions, new memory categories, release, cron, and automation stay off.

ZIP · approximately 6.91 MB · English · self-install Hermes build kit · download does not install

Download Staff Nurse SHIFT Build Kit →

03 · Nurse Leader & Manager Hermes Build Kit

Nurse Leader Complete AI OS with LEAD SuperPowers

For nurse managers and leaders who want one governed leadership foundation, one Command Center, and sixteen optional LEAD SuperPowers—without turning a private leadership workspace into an HR, clinical, surveillance, staffing, or enterprise decision system.

Before you build: downloading, selecting, opening, or unzipping changes nothing. This is a transparent self-install Hermes build kit—not an installed or operational application. Give Hermes the complete ZIP. Hermes must verify the manifest, checksums, source provenance, local environment, existing work, data boundaries, and rollback plan in read-only preflight; then show one exact Implementation Activation Card with APPROVE, REVISE, and CANCEL. Without approval of that exact card, Hermes must make no installation mutation.

Substantial local build: after approval, Hermes creates a separate work copy, preserves the immutable source and compatible work, establishes the Nurse Leader foundation first, adds the nl_lead.* overlay to one Command Center, and executes 21 foundation, 80 LEAD, and 12 integration checks—113 canonical checks in total. Written checks begin Not Run; source presence is not proof they passed. No application route is preassigned; any local route must appear on the approved card and pass a collision check.

Several visible Hermes turns may be normal. Every phase requires a checkpoint receipt and any continuing process requires a real identifier. All sixteen optional LEAD SuperPowers remain Available Inactive; agents remain PERM-P0 Disabled; connectors, shared access, external actions, schedules, new persistent memory categories, organizational-system access, and background automation stay off. A private build does not authorize organizational deployment.

Release integrity: the kit is deterministically built from the exact tracked LEAD source and verified against both the package directory and outer ZIP. SHA-256: 78293c6eaef4fa277f4afecf14eeb87b90f3385ba71be3189faaca2466c90974.

Why Nurse AI OS matters here: it gives nurse leaders a governed thinking and follow-through environment—not a shadow HR or clinical system. The approved SOUL gives Hermes the leader's commitments, communication style, workload limits, memory choices, stewardship priorities, and human-only decisions. LEAD Mission Control converts those commitments into briefs, meetings, action tracking, policy learning, charters, education plans, and synthetic or aggregate improvement work.

Optional MCP companion: the Manager / Lead profile is a separate artifact only when the user is actually operating as a nurse leader or manager; selection does not establish authority. If later activated through every separate gate, it could let Hermes retrieve approved leadership files and prepare document, calendar, or spreadsheet drafts without accessing workforce records or taking organizational action. MCP connectors remain disabled with zero tools; activation remains blocked pending a complete transitive lock and lock-consuming runtime; profile installation and every connector require a separate activation card and fresh approval. Verify SHA-256 before extraction →

ZIP · exactly 494,164 bytes (approximately 0.49 MB) · English · self-install Hermes build kit · not operational—local build required

Download LEAD Build Kit → Download inactive Manager / Lead profile →

04 · Nurse Educator & Instructional Designer Hermes Build Kit

Nurse Educator & Instructional Designer Complete AI OS with TEACH SuperPowers

For a Nurse Educator, Instructional Designer, or Hybrid / Faculty Developer who wants one governed educator foundation, one TEACH Command Studio, and twenty optional SuperPowers—without turning a private workspace into an autonomous instructor, grader, clinical authority, student-record system, surveillance tool, accreditation authority, personnel system, or institutional deployment.

Before you build: downloading, selecting, opening, and unzipping change nothing. This is a self-install Hermes build kit. Build begins only after you give this ZIP to your own Hermes, Hermes completes read-only preflight, shows the exact TEACH Implementation Activation Card, and you explicitly approve that exact card. Without that approval, Hermes must make no installation changes.

Substantial build: after approval, Hermes must verify the manifest and checksums, create an implementation work copy, install dependencies only after approval, build the Nurse Educator foundation first, bind the TEACH overlay, and validate the Trust Shield, TEACH Core, Command Studio, 18 workflows, 24 templates, 10 disabled agents, and twenty optional SuperPowers as an inactive overlay. The internal contract preserves 33 foundation checks, 120 TEACH overlay checks, and 16 integration checks—169 canonical checks, with 264 explicit target rows and 433 required execution records. Compatible work must be preserved and all twenty optional TEACH SuperPowers remain inactive.

Three authority adapters: Nurse Educator, Instructional Designer, or Hybrid / Faculty Developer. Selecting one does not verify employment, faculty status, teaching, design, grading, clinical, accommodation, academic-integrity, curriculum, accreditation, research, release, or institutional authority. Access is not authority; changing hats triggers a new authority check.

Several Hermes turns may be normal. Initial readiness is not operational—build required. Nothing continues in the background. Hermes must issue receipts and stop only at S0, S1, or S2. No PHI, student records, restricted employee records, secure assessments, learner surveillance, hidden ranking, AI-detection findings, connectors, shared access, external actions, new memory categories, or background automation. Private-workspace approval does not authorize LMS, classroom, clinical-site, program, employer, accreditation, research, multi-user, or institutional deployment.

Release integrity: the governed archive is verified as data by the tracked repository validator; CI does not execute bundled code. SHA-256: 39d7a83a79b6137d50b6b5da639cd44d0427e4e06e30fc9d7f3b19805b4080f3.

ZIP · exactly 6,820,684 bytes (approximately 6.82 MB) · English · self-install Hermes build kit · not operational—local build required

Download Educator & Designer TEACH Build Kit →

05 · Nurse-Connected Ally

For “Other” users who support nurses

For a non-nurse family member, collaborator, technologist, advocate, educator, entrepreneur, or community partner who wants to support nurse-led work without claiming nursing or institutional authority.

ZIP · approximately 0.50 MB · post-setup only

Download Nurse-Connected Ally Pack →

06 · Nurse Practitioner USA only

NP Complete AI OS with NP Wings

For a U.S. nurse practitioner or transitioning NP who wants one governed professional-and-whole-life foundation plus fifteen optional advanced-practice Wings—without turning a private workspace into an EHR, prescribing system, diagnostic engine, billing tool, legal record, surveillance system, or institutionally authorized clinical platform.

Before you build: downloading, opening, selecting, or unzipping changes nothing. Give this ZIP to your own Hermes. Hermes must verify the package, complete read-only preflight, show the exact WINGS Implementation Activation Card, and wait for explicit approval. Without that approval, Hermes must make no mutation.

Substantial build: after approval, Hermes establishes or binds the NP foundation first, adds NP Wings only after the foundation gate passes, validates 63 foundation checks, 82 Wings checks, and 1 complete integration check, and preserves compatible work. The WINGS build kit declares 410 required execution records; all fifteen optional Wings remain inactive.

Several Hermes turns may be normal. Hermes must display progress after every phase, pause only at safe checkpoints, and provide the exact resume command if interrupted. Agents remain disabled/P0; connectors, sharing, schedules, external actions, new memory categories, and background automation stay off. Readiness is not operational—build required and private-workspace approval does not authorize clinical, organizational, billing, legal, prescribing, credentialing, or institutional use.

Why Nurse AI OS matters here: it gives the NP a governed professional-development environment for evidence fluency, preparation, career growth, and sustainable practice without becoming a clinical decision system. The approved SOUL gives Hermes the NP's mission, learning goals, communication preferences, wellbeing limits, memory choices, and clinical red lines. WINGS Mission Control coordinates public-literature study, professional planning, nonclinical projects, and portfolio evidence.

Optional MCP companion: the Clinician NP profile is a separate artifact for a United States NP context and generic public-literature study or nonclinical learning notes; selection does not verify licensure, certification, privileges, or authority. If later activated through every separate gate, it could let Hermes retrieve approved public literature and work with bounded personal notes, files, documents, and calendar items. MCP connectors remain disabled with zero tools; activation remains blocked pending a complete transitive lock and lock-consuming runtime; profile installation and every connector require a separate activation card and fresh approval. It cannot process patient cases or narratives, charts, diagnosis, treatment, or prescribing. Verify SHA-256 before extraction →

ZIP · approximately 7.70 MB · English · United States only · self-install Hermes build kit · download does not install

Download Nurse Practitioner WINGS Build Kit → Download inactive Clinician NP profile →

What happens after a self-install build-kit download?

  1. Keep the original ZIP unchanged in a private local folder.
  2. Start Hermes in a new or verified-isolated workspace and give it the complete ZIP.
  3. Hermes performs read-only package, environment, authority, data-boundary, compatibility, and rollback checks. It installs nothing during this preflight.
  4. Hermes presents one exact Implementation Activation Card. You choose Approve, Revise, or Cancel.
  5. If you cancel or withhold approval, Hermes makes no installation mutation. If you approve, Hermes performs only the written scope in visible phases and gives you a receipt after each phase.
  6. The final handoff states Operational, Core operational; AI setup pending, or Not operational from actual target-environment evidence—not from a prompt, mockup, or written test list.

Never place PHI, patient-linked narratives, identifiable workforce records, personnel files, restricted organizational material, credentials, or secrets in the package or implementation conversation.

A role choice is personalization—not verification. These downloads do not prove nursing licensure, nursing-assistant certification, NP certification, population focus, prescriptive authority, privileges, enrollment, employment, instructional-design assignment, teaching or grading authority, scope, delegation, supervision, competence, faculty status, managerial authority, accreditation authority, institutional approval, or permission to access patient, student, employee, or personnel information.

For review-first lane 05

Ask Nurse AI OS to review before changing anything

Review this post-setup role pack for my selected role. Do not install, activate, schedule, connect, or change my Hermes profile yet. First show me: (1) the files you found; (2) proposed skills, workflows, memory, permissions, and external actions; (3) EDENA risk tiers and autonomy ceilings; (4) no-PHI and role-authority checks; (5) conflicts with my SOUL files or current Hermes setup; and (6) the rollback/removal plan. Wait for my explicit approval before applying any change.

After the review, you may approve the whole plan, approve only selected changes, revise it, defer it, or reject it.

Self-install build-kit lanes 01, 02, 03, 04, and 06: do not use the generic prompt above. Give Hermes the complete ZIP and require it to open GIVE-THIS-PACKAGE-TO-HERMES.md, perform read-only preflight, and show the lane's exact Implementation Activation Card before any mutation.

Integrity and stewardship

Inspect before you trust

Download manifest

Role, stage, file size, installation status, and SHA-256 for every ZIP.

Open manifest →

Checksum ledger

Use the SHA-256 ledger to verify that a downloaded ZIP has not changed.

Open checksums →

Browse tracked source

Tracked role-package source and build-kit metadata can be reviewed on GitHub. Governed build-kit ZIPs are checksum-pinned in the manifest and can be inspected locally before any activation decision; not every wrapper file is reproduced as tracked repository source.

Browse tracked package source on GitHub →

Boundary: No PHI. No patient-specific clinical decisions. Downloading never installs. Connectors, external actions, new memory categories, and background automation remain off unless a separate governed process explicitly authorizes them. Agents propose; authorized humans decide and act.