---
title: "NP Complete AI OS with NP Wings — One-File Setup Guide"
version: "1.0"
date: "2026-07-14"
status: "Implementation-ready"
program_id: "NAIO-NP-COMPLETE-WINGS-1.0"
default_mode: "Private, no-PHI, preview-first, human-controlled"
---

# NP Complete AI OS with NP Wings

## One-File Setup Guide

**The simple answer:** The Nurse Practitioner foundation and NP Wings are now merged into one Hermes program. The user gives Hermes one Markdown file, uses one installation prompt, and approves one combined setup card.

> **Please allow time for setup.** This is a substantial installation. It builds and verifies a complete NP operating foundation plus fifteen advanced-practice powers. It may take considerably longer than a normal prompt and may require several Hermes turns. That is normal. Hermes should show progress after every phase and provide an exact resume command if the setup must pause.

## The one file to install

`NP-Complete-AI-OS-with-Wings-Hermes-Program.md`

This file contains:

- the complete Nurse Practitioner Life, Practice & Purpose foundation;
- the NP Empowerment Compact, Trust Shield, no-PHI boundary, and Practice Boundary Check;
- the base Command Center and Core Four;
- the complete NP Wings installer, Authority Shield, fifteen powers, workflows, templates, manifest, and tests;
- one guided orchestration layer that installs everything in the correct internal order;
- progress checkpoints, safe resume behavior, rollback, and a combined activation report.

You do not need to install the former NP program and NP Wings package separately.

---

# Quick setup

## 1. Open a private workspace

Use one authenticated, private workspace owned by the nurse practitioner. Do not use a shared account or a workspace containing patient information.

## 2. Give Hermes the complete program file

Upload or attach the entire `NP-Complete-AI-OS-with-Wings-Hermes-Program.md` file. Do not copy only part of it, split it into sections, or separately install its embedded components.

## 3. Use the single installation prompt

> Install NP Complete AI OS with NP Wings v1.0 from this entire file in Guided Complete Setup mode. Treat the Complete Edition orchestration as the controlling installation sequence and the embedded component sources as its governing runtime content. Complete the read-only safety preflight, ask the minimum setup questions one at a time, and present one combined activation card. Wait for my approval before applying changes. Then install the NP foundation first, run its critical tests, add NP Wings as an inactive overlay, and run the Wings tests. Preserve existing data, dashboards, safeguards, permissions, and unrelated work. Do not enable connectors, external actions, new memory categories, or background automation. Use synthetic, public, fictional, or low-sensitivity information for testing. This is a substantial installation and may take several turns: show a progress receipt after every phase, never rush or silently skip a check, and if you reach a limit stop at a safe checkpoint with the exact command to resume.

## 4. Approve one combined setup card

Hermes asks the minimum questions one at a time and then shows one **NP Complete Edition Activation Card**. Review the user, broad professional context, 90-day outcomes, protected-life outcome, privacy, memory, permissions, connectors, automation, official verification routes, rollback, and proposed dashboard state.

Choose **Edit**, **Foundation only**, **Keep installed components inactive and make no changes**, or **Cancel** if anything is not right. Installation approval does not activate an optional Wing.

## 5. Wait for the final activation report

Do not treat a long response, a dashboard preview, or a progress message as completion. Setup is finished only when Hermes provides the **Complete Edition Activation Report** and every critical gate has passed.

---

# What happens internally

The user manages one setup. Hermes still protects the correct dependency order:

| Phase | Hermes performs | Safe checkpoint |
|---|---|---|
| 0 | Read-only identity, privacy, permission, version, dashboard, and compatibility inventory | `S0` — verified pre-install state |
| 1 | Minimum questions and one exact-scope Complete Edition Activation Card | Awaiting NP approval |
| 2 | Create, bind, or repair the NP foundation; run its critical tests | `S1` — healthy foundation |
| 3 | Add NP Wings as an overlay; keep all optional Wings inactive | `S2` — healthy Complete Edition |
| 4 | Run 63 foundation tests, 82 Wings tests, and integration checks | Passed or Blocked |
| 5 | Present the final report, first safe use, rollback, and review dates | Complete |

Hermes must create one dashboard, not two. The foundation owns the **My NP Life, Practice & Purpose Command Center**. NP Wings adds its Library, Flight Status, and an optional Next Horizon view to that same Command Center.

If a compatible component is already healthy, Hermes should verify and bind to it rather than reinstall or duplicate it.

---

# The long-install experience

## What is normal

- Several Hermes turns may be needed.
- Hermes may pause for the activation-card approval.
- Acceptance testing may take longer than the visible dashboard creation.
- A platform response limit may require a safe checkpoint and resume.
- The foundation may complete before NP Wings begins.

## What is not normal

- No progress status for an extended sequence
- Reporting Complete before the final activation report
- Silently skipping tests because setup is taking too long
- Creating a second dashboard or duplicate records
- Enabling a connector, external action, memory category, or automation to speed installation
- Continuing in the background after the session ends

## Safe resume prompt

If setup pauses, use the checkpoint receipt Hermes provides and say:

> Resume NP Complete Edition installation from the last approved checkpoint. Revalidate identity, privacy, permissions, versions, current dashboard state, and all critical controls before continuing. Do not repeat completed mutations, assume a prior result, enable a connector, save new memory, or skip a failed or unknown test. Show the refreshed progress ledger and continue with the next incomplete phase only.

If Hermes cannot identify the last verified checkpoint, choose **Pause All** and request a read-only inventory before continuing.

---

# Safety before setup

Confirm all of the following:

- One authenticated NP owns a private workspace.
- No patient information or patient-linked narrative is present.
- Clinical, prescribing, EHR, payer, credentialing, employer, messaging, and business connectors are off.
- External actions and background automation are off.
- Privacy & Permissions, Activity History, and Pause All are visible.
- Memory can be inspected, corrected, restricted, exported, deleted, and used session-only.
- Personal, employer, academic, business, and community contexts can remain separate.
- The Markdown dashboard can operate as fallback.
- Synthetic, public, fictional, or low-sensitivity information is available for testing.
- A pre-install snapshot or change manifest and rollback are available.

If a critical control is unavailable, installation is **Blocked**. Hermes must show a remediation list and must not imitate the missing control.

## Never provide

- Patient names, images, recordings, chart text, results, prescriptions, messages, claims, or re-identifiable clinical narratives
- Patient-specific assessment, diagnosis, treatment, triage, dosing, prescribing, orders, documentation, coding, billing, or prior-authorization content
- Passwords, authentication tokens, private keys, recovery codes, signature images, or controlled-substance credentials
- Full sensitive contracts, peer-review material, personnel information, learner records, or unnecessary private financial details

Removing a name does not automatically make a clinical narrative safe to use.

---

# What the Complete Edition gives the NP

## The foundation

- NP Empowerment Compact and Trust Shield
- No-PHI personal workspace boundary
- Seven-gate Practice Boundary Check
- Professional and whole-life Command Center
- Credential, source, goal, role-load, learning, evidence, conversation, project, and whole-life records
- Full, Standard, Minimum, and Re-entry plan modes
- Privacy, memory, permission, pause, reset, export, deletion, and rollback controls

## The Core Four

1. **Plan My Whole Day**
2. **Think & Verify**
3. **Credential Radar**
4. **Make This Human**

## NP Wings

- **W — Work within verified authority**
- **I — Influence care, teams, and systems**
- **N — Navigate credentials, roles, and career**
- **G — Grow scholarship, innovation, and impact**
- **S — Sustain person, purpose, and future**

The fifteen optional powers remain inactive after installation. The NP chooses whether and when to preview one.

---

# Verify completion

The final report should confirm:

- `NAIO-NP-COMPLETE-WINGS-1.0` is installed.
- `NAIO-NP-LPPEF-1.0` is the active foundation.
- `NAIO-NP-WINGS-1.0` is installed as an inactive overlay.
- One Command Center exists.
- The Core Four and permanent controls are visible.
- Base records and unrelated work were preserved.
- No duplicate foundation records were created.
- No connector, external action, new memory category, or background automation was enabled.
- All 63 foundation tests and 82 Wings tests ran.
- Every critical test and Complete Edition integration check passed.
- `S0`, `S1`, and `S2` rollback behavior is documented.
- Every optional Wing remains inactive.

If any critical result is Failed, Partial, Unknown, or Awaiting verification, the Complete Edition must not be labeled active.

---

# First safe use

After the activation report, say:

> Show my current season, capacity, Core Four, permanent controls, Wings status, permissions, sources needing verification, and one safe next step. Keep external actions off and do not save anything new without asking me.

To preview the first Wing:

> Open my Wings Library and recommend one Wing based on my 90-day aspiration, greatest pain point, current capacity, and protected-life commitment. Show the full activation card and one synthetic preview. Do not save new information or perform an external action. Wait for my approval.

Activate no more than one new Wing during the first week. Complete at least three supervised successful runs before considering greater automation.

---

# Pause, reset, and remove

## Pause immediately

> Pause all NP Complete Edition workflows now. Do not delete anything. Stop triggers and external actions and show every pending, attempted, completed, failed, partial, or unknown action.

## Reset safely

> Reset NP Complete Edition to safe defaults: connectors off, external actions off, Manual/Assist/Preview only, Core Four visible, and all optional Wings inactive. Preview the complete change manifest before applying it.

## Remove NP Wings but keep the foundation

> Preview removal of only `np_wings.*` records, views, launchers, permissions, and pending runs. Preserve NP-LPPEF, its safeguards, Core Four, base records, and unrelated data. Offer an approved export before deletion and provide a completion receipt.

## Remove the Complete Edition

> Preview restoration of the verified pre-install state `S0`. Preserve unrelated data and offer an approved export of permitted NP information before deletion. Show exactly what will be removed, retained, or could not be restored, and wait for my approval.

---

# If something goes wrong

| Situation | Safe response |
|---|---|
| Setup seems slow | Check the progress ledger. A long setup is expected; completion still requires the final report. |
| Hermes reaches a limit | Use the checkpoint receipt and exact resume prompt. Revalidate before continuing. |
| Base is missing or incompatible | Keep Wings inactive. Install or repair the foundation; never force migration. |
| Duplicate dashboard or records appear | Pause All, restore the last safe checkpoint, and rerun in bind-if-present mode. |
| A critical test fails | Mark activation Blocked, correct the cause, and retest. Never waive it. |
| A connector or external action appears | Pause All, revoke access, inspect activity receipts, and reset safely. |
| Patient information was entered | Stop without repeating it, prevent retention, use deletion controls, and return to the approved clinical environment and organizational process. |
| Dashboard feels overwhelming | Return to the Core Four and keep every optional Wing inactive. |
| Authority is uncertain | Mark it Unverified and use the appropriate official source or qualified human. |

## Final principle

> One file makes setup easier. It does not make safety optional. The NP's license leads, professional judgment remains human, patient information stays protected, and every advanced power remains under the NP's control.
