
# Read Me First — instruction for Hermes

Availability boundary: this build kit is available only in the United States. If the target user or intended use is outside the United States, stop before build mutation and route to a separately governed local-jurisdiction review. This package confers no licensure, clinical authority, or institutional authorization.

Give Hermes the complete extracted directory and paste this instruction:

> Build `NP WINGS — Nurse Practitioner Life, Practice & Purpose Mission Control` from this entire package. Begin by displaying `PROCESSING_MESSAGE.md` exactly. Verify `RELEASE-MANIFEST.json`, `SHA256SUMS.txt`, `SOURCE-INVENTORY.json` and the immutable source bytes. Read `INPUT-PRECEDENCE.md`, `implementation/NP-Functional-Build-Master-Prompt.md`, and `implementation/HERMES-HANDOFF-README.md`. Perform only the read-only preflight first. Return one Implementation Activation Card with exact paths, dependencies, network/download plan, privacy and authority boundaries, test plan, rollback and Approve/Revise/Cancel choices. Stop for my exact approval before mutation. Preserve unrelated work. Do not use patient information, clinical-system credentials, or restricted institutional data. Keep connectors, external actions, new memory, schedules, tools, agents and background automation off. Build the foundation first, then add WINGS as an inactive overlay. Execute and reconcile all 410 records. Use an evidence-based readiness state; never infer completion from this prompt, a static page, a screenshot or a mocked response.

The installation may take several minutes or multiple Hermes turns. Keep checkpoint receipts and use the resume instruction supplied by Hermes if a session ends.
