# SHIFT Staff Nurse Life & Practice Mission Control — Hermes Functional Build Kit

**Build-kit ID:** `NAIO-SNQI-SHIFT-FUNCTIONAL-BUILD-KIT-1.0.0`  
**Target product:** `SHIFT — Staff Nurse Life & Practice Mission Control`  
**Target product ID:** `staff-nurse-life-practice-mission-control`  
**Target application version:** `2.0.0`  
**Lane:** `staff_nurse_life_practice`  
**Build-layer dashboard:** `/staff-nurses/dashboard`  
**Canonical source namespace:** `snqi_shift.*`  
**Home:** `My SHIFT Mission Control`

This is the downloadable package to give Hermes so it can build, test, and package a real local Staff Nurse Life & Practice application with the integrated SHIFT quality-contributor layer. It combines an immutable working Nurse AI OS Mission Control v2 baseline, the complete Staff Nurse foundation, the complete SHIFT source corpus, a resolved functional-build contract, implementation contracts, safe synthetic personalization fixtures, acceptance controls, recovery instructions, and an independent verifier.

The lane, URL, home label, `SHIFT-*` catalog IDs, schemas, agents, and permission model are **build-layer decisions**. The immutable program authority remains complete program `NAIO-SNQI-COMPLETE-SHIFT-1.0`, foundation `NAIO-SN-LPEF-1.0`, overlay `NAIO-SNQI-SHIFT-1.0`, and namespace `snqi_shift.*`.

## Honest status

This ZIP is a verified **functional-build kit**, not the already-installed target application. The bundled baseline is a working offline dashboard, while the Staff Nurse and SHIFT sources are program specifications. Hermes must still implement and test the role specialization, durable server-side persistence, authenticated loopback access, genuine streamed AI, consent-controlled memory, evidence handling, bounded agents, institutional-workspace gates, and clean installation before calling the target Operational.

Initial target readiness: **Not operational — build required.**

## Pinned Staff Nurse + SHIFT baseline

- 5 foundation departments and the NURSE Compass.
- 4 role adapters with exactly one active hat for each mission.
- 2 deployment contexts: Private Personal Mode and a **separately provisioned** Institution-Approved Quality Workspace.
- 4 Core launchers and 1 deliberately empty optional launcher.
- 20 optional SHIFT SuperPowers, all installed `Available Inactive`.
- 18 guided SHIFT workflows and 25 reusable templates.
- 40 foundation tests + 120 SHIFT overlay tests + 16 integration checks = **176 canonical compatibility checks**.
- 216 build-layer control tests + 48 cross-cutting packaged scenarios + 176 canonical checks = **440 required execution records**, all initially `Not Run`.
- All external actions, connectors, schedules, sharing, background automation, and agents start off.
- Private, synthetic demonstration, no PHI, session-only memory, Manual/Assist/Preview defaults.

Installing this package **does not provision or authorize** an institutional QI workspace, data access, a project charter, QI-versus-research determination, workflow change, pilot, spread, release, publication, or external sharing.

## Give the ZIP to Hermes

1. Keep the original ZIP unchanged in a private local folder.
2. Extract it. From the extracted package root run:

   ```text
   python3 tools/verify-build-kit.py --package .
   ```

   On Windows use `py` or `python` if needed. To verify the outer archive too:

   ```text
   python3 tools/verify-build-kit.py --package . --zip ../STAFF-Nurse-Life-Practice-SHIFT-Mission-Control-Hermes-Build-Kit-v1.0.0.zip
   ```

3. Start Hermes in a new or verified-isolated implementation workspace.
4. Give Hermes the ZIP and say:

   > Unpack this build kit, open `GIVE-THIS-PACKAGE-TO-HERMES.md`, verify its manifest and checksums, and follow the program exactly. Begin with read-only preflight. Do not install dependencies, edit files, start services, change my Hermes profile, activate an agent or power, or claim an institution-approved quality workspace until you show one Implementation Activation Card and I approve it.

5. Save every checkpoint receipt and the final handoff report.

## Allow enough time

Installation and implementation can take **many minutes and several visible Hermes turns**. Source inspection, dependency installation, database migrations, UI conversion, capability discovery, security and accessibility tests, clean-install verification, and packaging are real work. Nothing continues invisibly after a Hermes turn ends; Hermes must report every live process by identifier.

## Read in this order

1. `GIVE-THIS-PACKAGE-TO-HERMES.md`
2. `implementation/STAFF-Functional-Build-Master-Prompt.md`
3. `implementation/STAFF-Product-Specification.md`
4. `implementation/STAFF-Architecture-and-Data-Model.md`
5. `implementation/STAFF-Personalization-Mapping-Crosswalk.md`
6. `implementation/STAFF-Starter-Workspace-Crosswalk.md`
7. `implementation/STAFF-Governance-EDENA-and-Data-Boundaries.md`
8. `implementation/STAFF-Agent-Team-and-Routing.md`
9. `implementation/STAFF-Capability-and-Badge-Evidence-Model.md`
10. `config/STAFF-Capability-Mastery-Criteria.v1.json`
11. `config/STAFF-Source-Recommendation-Registry.v1.json`
12. the three closed Staff adapter/profile contracts under `schemas/`
13. `implementation/STAFF-Guide-Page-Content.md`
14. `implementation/STAFF-Security-and-Privacy-Checklist.md`
15. `implementation/STAFF-Control-Completeness-Matrix.csv`
16. `implementation/STAFF-Acceptance-and-Test-Ledger.md`
17. `implementation/STAFF-Synthetic-Sample-Mission.md`
18. the immutable material under `source/`

## Non-negotiable boundary

Never enter PHI, identifiable patient/event/coworker details, chart or handoff content, a live-care request, peer-review or incident material, row-, person-, event-, or narrative-level institutional data even when called deidentified, health narratives, employment-dispute details, restricted employer information, credentials, secrets, or financial account data. Health or employment-dispute needs route to the appropriate qualified human or official process without retaining or echoing detail. Institutional QI accepts only an exact separately approved aggregate created outside SHIFT after binding every required receipt. The application must not decide or execute care, diagnosis, treatment, medication, devices, assignment, delegation, scope, competence, staffing, discipline, QI-versus-research status, policy/workflow change, pilot, spread, release, publication, or external action. Current local policy, official systems, chain of command, authorized institutional reviewers, and accountable humans remain authoritative.
