# SHIFT Staff Nurse Life & Practice Mission Control — Baseline Gap Report

## Decision

The canonical Staff Nurse Life & Practice foundation and the integrated SHIFT corpus are approved as the **domain, staff-nurse safety, whole-life, quality-improvement, workflow, user-language and compatibility-test authority**:

- complete program: `NAIO-SNQI-COMPLETE-SHIFT-1.0`;
- foundation: `NAIO-SN-LPEF-1.0`;
- overlay: `NAIO-SNQI-SHIFT-1.0`;
- canonical overlay namespace: `snqi_shift.*`.

The validated DISCOVER Mission Control application may be used only as a structural engineering reference for a real local application. Neither the Markdown programs, Word guides, static dashboard preview nor DISCOVER baseline is the completed Staff Nurse product.

Until Hermes builds the target, executes the target ledger and all critical gates pass, the required statement is:

> **Not operational:** One or more core acceptance criteria failed or has not been run; blockers are documented in the acceptance ledger.

Do not describe a rendered packet, a reskinned static page, generated dashboard image, untested codebase or configured prompt as installed, operational, secure, compliant, institutionally approved or Hermes-connected.

## Source authority and target identity

### Canonical domain corpus

- Complete program ID: `NAIO-SNQI-COMPLETE-SHIFT-1.0`
- Foundation ID: `NAIO-SN-LPEF-1.0`
- Overlay ID: `NAIO-SNQI-SHIFT-1.0`
- Namespace: `snqi_shift.*`
- Role adapters: Direct-Care Staff Nurse; Unit Champion, Preceptor or Shared-Governance Member; Chartered Staff-Nurse QI Project Lead; Hybrid or Multiple-Employer
- Deployment contexts: Private Personal Mode; separately provisioned Institution-Approved Quality Workspace
- Five foundation departments and the NURSE Compass
- Core Four launchers; fifth launcher deliberately empty
- Twenty optional SHIFT powers, all inactive after installation
- Eighteen SHIFT workflows and twenty-five reusable templates
- Compatibility suite: 40 foundation tests + 120 SHIFT overlay tests + 16 integration checks = **176 canonical checks**
- Default: private, synthetic demonstration, no PHI or institutional data, session-only memory, connectors and sharing off, Manual/Assist/Preview only

### Build-layer implementation decisions

These identifiers organize the new application and do not rewrite the canonical corpus:

- Product: `SHIFT — Staff Nurse Life & Practice Mission Control`
- Product ID: `staff-nurse-life-practice-mission-control`
- Population lane: `staff_nurse_life_practice`
- Canonical dashboard route: `/staff-nurses/dashboard`
- Home label: `My SHIFT Mission Control`
- Data/config namespace: `snqi_shift.*`
- Target application version: `2.0.0`

The product ID, lane, route, home label, stable catalog IDs, schemas, agents and permission vocabulary are build-layer decisions because the legacy corpus did not define executable equivalents. Stable catalog keys may use `SHIFT-PWR-01…20`, `SHIFT-WF-01…18` and `SHIFT-TPL-01…25` while preserving the exact canonical display titles and order.

### Structural reference

The DISCOVER functional baseline contributes reusable engineering patterns only: loopback-first server, authenticated same-origin UI, SQLite repositories and migrations, offline core, provider-neutral AI backend, genuine stream/cancel protocol, consent-controlled memory, evidence/citation integrity, multi-workspace isolation, control completeness and evidence-led readiness. DISCOVER-specific roles, routes, research powers, schemas, agents and content are not Staff Nurse content.

No completed Discover Packet, Soul Quiz, employer authorization, quality charter, QI/research determination, data permission or clinical authority is assumed. Synthetic examples never establish identity, employment, scope, competence, authority, approval, project status or outcomes.

## What the canonical corpus already does well

### Whole-person staff-nurse foundation

- Coordinates shift pattern, commute, sleep opportunity, recovery, meals, family, caregiving, health appointments, learning, credentials, career, finances, relationships, community and purpose.
- Protects the life beyond the shift and rejects plans that depend on chronic fatigue, skipped recovery or unpaid hidden labor.
- Supports new graduates, experienced nurses, day/night/rotating staff, float/per-diem/travel nurses, caregivers, disabled or neurodivergent nurses, multilingual or internationally educated nurses and people returning after leave.
- Keeps private life data outside employer and quality analytics.

### Clinical, privacy and human-authority boundaries

- Prohibits PHI, identifiable patient/event narratives, charts, handoffs, screenshots, patient lists, exact room/time combinations and shadow clinical systems.
- Refuses live triage, diagnosis, treatment, medication, device, alarm, documentation, assignment, delegation, competence and fitness decisions.
- Routes actual care, immediate safety, workplace violence and crisis concerns to the approved human and emergency chain without requesting more clinical detail.
- Separates personal, employer, project and institutional contexts; least privilege wins.

### Frontline quality stewardship

- Gives staff nurses a systems-learning and improvement lane without borrowing management, clinical, data, research, release or policy authority.
- Requires a separately provisioned institutional workspace, sponsor, charter, decision rights, QI/research human determination, data-steward receipt, approved definitions, small-cell rules, protected capacity and release owner before real QI work advances.
- Uses process maps, PDSA, measure families, provenance, equity, accessibility, balancing measures, burden and honest sustain/revise/pause/remove decisions.
- Prohibits surveillance, ranking, blame, discipline, retaliation, invented causality and inflated improvement claims.

### Governed capability

- Applies EDENA and the SHIFT Gate before consequential work.
- Installs all twenty powers inactive and requires synthetic Preview plus exact approval.
- Defines Manual, Assist, Preview, Supervised run and tightly bounded automation states.
- Provides recovery controls, exact resume, checkpoints S0/S1/S2 and 176 detailed compatibility checks.

These are specifications. Their presence in source files is not evidence that runtime enforcement works.

## Functional implementation gaps

### 1. Real offline application core

**Present:** Markdown instructions, cards and dashboard views.  
**Missing:** authenticated local UI/API, durable mission/project/goal/task/note/source/artifact records, search/filter/sort, archive/restore/delete, history and transactional relationships.  
**Required:** useful shift-life planning, learning, communication rehearsal, career planning and synthetic quality preparation with AI and network disabled.

### 2. SQLite source of truth and migrations

**Present:** prose record definitions.  
**Missing:** schema, foreign keys, transactions, forward-only migrations, migration checksums, backup-before-migration, rollback, stable data path and integrity checks.  
**Required:** server-owned SQLite; browser storage contains only non-secret ephemeral preferences.

### 3. Authentication, sessions and secret boundaries

**Present:** an assumed private authenticated Hermes workspace.  
**Missing:** local credential setup, memory-hard verifier, rotating session, expiry/revocation, CSRF, Origin/Host checks, rate/size limits and server-only provider credentials.  
**Required:** no default credential; no secret in client code, browser storage, URL, log, export, diagnostics, evidence or package.

### 4. Active-role, employer and context isolation

**Present:** four role adapters, task-level hats and two deployment contexts.  
**Missing:** repository-enforced active owner/role/hat/employer/context/project scopes and invalidation rules.  
**Required:** every request and record binds one active context; changing role, hat, employer, project, workspace, determination, data, measure or audience invalidates incompatible authority and approvals.

### 5. Private-versus-institutional physical and logical separation

**Present:** a strong conceptual boundary.  
**Missing:** separate storage roots/databases or comparably strong isolation, separate credentials/session scope, export allowlists and no-transfer enforcement.  
**Required:** private schedule, readiness, recovery, health, relationship, financial, mission and abstract screened reflection records never enter institutional search, AI context, agents, QI measures, analytics, exports or institutional backups. Owner-controlled private backups may include only the isolated private store after exact preview and must never cross contexts.

### 6. No-PHI and live-care admission guard

**Present:** refusal language and Trust Shield.  
**Missing:** server-side pre-persistence and pre-provider classifiers, quarantine-free rejection, zero-body boundary receipts and negative tests across imports, attachments, logs, exports, memory and AI.  
**Required:** reject before persistence or forwarding; do not echo prohibited content.

### 7. Core Four and twenty-power lifecycle

**Present:** launcher names, power content and state machine.  
**Missing:** executable launchers, frozen definitions, state records, exact activation previews, approval hashes, expiry, pause/remove/reset and three-supervised-run evidence.  
**Required:** all powers install inactive; optional fifth remains empty until separately approved; no definition grants authority.

### 8. Five-stage mission and improvement loop

**Present:** NURSE Compass, PDSA and review cadence.  
**Missing:** durable Assess–Diagnose/Define–Plan–Implement–Evaluate cycles, stage history, branching/reopen, invalidation and measures.  
**Required:** implementation means local drafts, rehearsal, tasks and human-owned handoffs; the app never executes clinical, institutional or external change. Use the exact lifecycle `Exploration → Simulation → Recommendation → Draft Artifact → Approved Plan → Authorized Execution → Completed Action → Evaluated Outcome`: Approved Plan is human scope review only, Authorized Execution is external human/official-system only with no app action, and Completed Action requires a verified external reference.

EDENA requires independent `edena_tier` and `absolute_stop`. Personal Red may continue only as a new clean fictional/generic exploration after deliberate acknowledgment when `absolute_stop=false`; Institutional Red blocks operational progression until required review/authorization; every absolute stop hard-blocks everywhere.

### 9. Quality-project governance runtime

**Present:** detailed readiness and bind requirements.  
**Missing:** enforceable project gate, signed/hashed receipts, expiry, change detection and repository guards.  
**Required:** real project work stays blocked until current sponsor, charter, decision-rights, human determination, data, clinical/operational change, privacy, release and capacity receipts are bound.

### 10. QI-versus-research determination boundary

**Present:** AI is prohibited from deciding.  
**Missing:** human-determination request workflow, receipt schema, status/conditions/expiry and material-change triggers.  
**Required:** AI prepares questions only; missing, expired or changed determination blocks data use, pilot, spread and dissemination beyond generic planning.

### 11. Data provenance, measures and small-cell enforcement

**Present:** required definitions and templates.  
**Missing:** data-use receipts, field dictionaries, operational-definition versions, suppression rules, lineage, approved-purpose enforcement and export validation.  
**Required:** institutional QI accepts only public/synthetic framing or an exact separately approved aggregate created outside SHIFT, bound by content hash, query/definition/version, provenance, suppression/small-cell rule, access, retention/deletion, approval and expiry. Reject row-, person-, event-, and narrative-level information even when called deidentified. Minimum-necessary business contact metadata is routing-only and never measure data.

### 12. Evidence, policies and citations

**Present:** source watch and version-verification expectations.  
**Missing:** source registry, retrieval adapter, freshness/correction state, claim-source links, citation validator, applicability notes, reproducible queries and injection quarantine.  
**Required:** no fabricated source, no silent resolution of conflicts and no general guidance represented as current local policy.

### 13. Real AI backend and Hermes adapter

**Present:** prompts addressed to Hermes.  
**Missing:** authenticated capability discovery, normalized provider interface, model/session operations, errors, usage and current setup state.  
**Required:** same-origin server proxy and honest `Setup required`, `Offline`, `Authentication failed` or `Limited capabilities` states.

### 14. Genuine streaming, cancellation and retry safety

**Present:** none.  
**Missing:** provider-originated deltas, typed events, Stop propagation, reconnect/resume, terminal state and duplicate prevention.  
**Required:** no canned output, timer stream, fake tool event or simulated connection; a slow real-stream cancellation test is mandatory.

### 15. Governed agents and automation

**Present:** preview-first automation ceiling.  
**Missing:** frozen agent registry, route preview, charters, exact one-run authorization, allowlists, resource limits, Pause/Kill and reconciliation.  
**Required:** all agents P0/disabled; P1/P2 are exact one-run draft/read-only ceilings; P3 is only a separately approved deterministic local personal reminder after three supervised successful runs with no model inference, institutional/QI data, connector, external destination, monitoring, staffing/surveillance input or quality decision; P4 is absent. No clinical, event, staffing, surveillance, personnel, quality-change, message, release or official-system action; no background work, self-expansion, recursion or silent retry.

### 16. Consent-controlled memory

**Present:** Green/Yellow/Orange/Red memory guidance and session-only default.  
**Missing:** Preview/Remember/Edit/Forget/Delete/Export, purpose/scope/consent/expiry, context filters and provider-memory truthfulness.  
**Required:** PHI, event detail, restricted employer/QI material, health narrative, employment-dispute detail, secrets, credentials and unsupported authority inferences never persist or enter memory, indexing, exports, badge/QI evidence, or agents. Stop without echoing and route health or employment disputes to the appropriate qualified human or official process.

### 17. Personalization provenance

**Present:** activation questions and life/practice direction.  
**Missing:** versioned Mission Profile, field source, inference/uncertainty, approve/reject/edit, history and deletion receipt.  
**Required:** only user-approved derived fields influence recommendations; role, employer, authority and institutional permissions remain unverified until established by current human receipts.

### 18. Capability and badge evidence

**Present:** portfolio and growth evidence expectations.  
**Missing:** criteria versioning, evidence eligibility, reviewer, correction/expiry/revocation and non-credential controls.  
**Required:** badges reflect reviewed work and stewardship; never licensure, certification, continuing-education credit, competence, fitness, employment status or institutional authorization.

### 19. Capacity, fatigue, recovery and human support

**Present:** strong workload and whole-life protections.  
**Missing:** explicit capacity modes, burden budgets, Minimum Mode, re-entry workflow, local support map and measurable net-burden review.  
**Required:** overload simplifies; unsafe transport concern routes to humans; no diagnosis of fatigue, burnout, moral distress, impairment or health status.

### 20. Backup, update, rollback, deletion and uninstall

**Present:** recovery commands in prose.  
**Missing:** consistent backup, optional encryption, manifest/checksum validation, temporary restore, atomic swap, pre-update backup, rollback and path-verified deletion.  
**Required:** distinguish app files, private data, institutional project data and provider/external artifacts; never overclaim remote deletion.

### 21. Reproducible packaging and platform proof

**Present:** downloadable document bundle.  
**Missing:** declared runtime, locked dependencies, SBOM, reproducible build/install, secret scan, safe archive checks and clean-machine platform evidence.  
**Required:** an OS is Supported only after the exact packaged artifact passes its complete suite; otherwise label Targeted.

### 22. Complete controls and diagnostics

**Present:** permanent control list.  
**Missing:** actual behavior and evidence for every button/route/API plus database, Hermes, model, stream, session, memory, agent, evidence, project-bind and data-boundary diagnostics.  
**Required:** no enabled dead button, decorative launch, fake progress or capability inferred from configuration alone.

## Domain-specific blockers

Any of these forces **Not operational**:

- PHI, patient/event narrative, chart, handoff, screenshot, room/time detail or live-care request persists, logs, exports or reaches AI;
- private-life information crosses into an employer, QI, project, agent, measure, export, analytics or shared workspace;
- one employer/project can retrieve another employer/project's data;
- the app creates a shadow chart, handoff, event file, clinical task list, staffing system, employee record, surveillance system or manager dashboard;
- the system determines care, medication/device action, assignment, delegation, competence, fitness, reportability, fault, discipline, legal rights, compliance or QI-versus-research status;
- title, committee membership, technical access, uploaded file or role label is treated as authority;
- a project advances without current sponsor, charter, decision rights, human determination, data receipt, operational/clinical owners, release owner and protected capacity;
- small cells, quasi-identifiers or linkable combinations create reidentification risk;
- an individual is ranked, scored, profiled, predicted, monitored or targeted for performance, staffing, discipline, compensation or retaliation;
- evidence, citation, measure, result, authorship, credential, hours, contribution, causality, special cause, improvement or impact is fabricated or overstated;
- an agent or power self-activates, widens context, retries silently, runs after Pause/Kill or takes an external action;
- the app performs an official message, report, pilot, policy/workflow change, publication, presentation, connection, external transfer, spread or automation under any condition; these actions remain external human/official-system work and SHIFT records only a verified external reference;
- starter/synthetic content counts as a real project, outcome, portfolio proof or badge evidence;
- a badge implies competence, certification, licensure, credit, authority or institutional approval;
- fake AI, source, tool, progress, connection or completion state appears; or
- readiness is asserted without executed target evidence and all 176 canonical checks.

## Implementation sequence

1. **S0 — Read-only preflight:** verify source hashes, target identity/routes, host, existing Hermes profile, dependencies, permissions, active context boundaries and recovery state; present one Implementation Activation Card before mutation.
2. **S1 — Secure private offline foundation:** loopback server, auth, private SQLite store, migrations, Core Four, five-stage missions, life/practice CRUD, onboarding, synthetic starters, Guide and backup/restore.
3. **S2 — SHIFT domain runtime:** role/hat/employer context, twenty inactive powers, eighteen workflows, twenty-five templates, NURSE Compass, capacity shield, evidence, capability and portfolio systems.
4. **S3 — Optional institution-approved QI lane:** create only after separate approval; provision isolated store/workspace; require bind and authority receipts; transfer zero private records.
5. **S4 — Governed intelligence:** real Hermes backend, genuine stream/cancel, source/citation integrity, consent memory, P0 agents, exact-run controls and diagnostics.
6. **S5 — Release proof:** accessibility, negative safety/security tests, control matrix, full-stack scenarios, all 176 canonical checks, clean-machine OS tests, reproducible package and final handoff.

This build kit completes none of those runtime gates. Every matrix control and ledger test starts **Not Run** until Hermes builds and executes the packaged target.
