
# Installation and Hermes handoff

## Owner preparation

1. Keep the downloaded ZIP as a read-only recovery copy.
2. Require the trusted `CHECKSUMS.sha256` sidecar obtained through the authenticated publisher channel and verify that it contains the exact SHA-256 digest for `WINGS-Nurse-Practitioner-Complete-AI-OS-Mission-Control-Hermes-Build-Kit-v1.0.0.zip` before extraction. Stop if the sidecar is missing, untrusted, malformed, or mismatched; do not extract the ZIP.
3. Extract into a private local folder that does not synchronize to an unapproved service.
4. Keep the unchanged original ZIP immediately beside the extracted package folder, then run `python3 tools/verify-build-kit.py --package . --zip ../WINGS-Nurse-Practitioner-Complete-AI-OS-Mission-Control-Hermes-Build-Kit-v1.0.0.zip`.
5. Give the entire folder to Hermes; do not paste only selected pages.

## Hermes sequence

Hermes must use a copy-on-write path and show one Activation Card before mutation. The controlled build order is:

1. S0 — verify sources, environment, paths, permissions and rollback.
2. S1 — build and test the durable offline NP foundation.
3. S2 — add the 15-power WINGS overlay inactive and test isolation/removal.
4. S3 — add genuine provider integration, evidence, consent memory and bounded agents.
5. S4 — execute the complete 410-record inventory and package the application.

The process may take several turns. A checkpoint is not completion.

## Backup and rollback

- Preserve the original source ZIP and pre-install snapshot.
- Back up the application database, permitted attachments, configuration, migration state and manifest as one atomic set.
- Test restore into a separate path before relying on it.
- Roll back a failed WINGS overlay to the healthy foundation checkpoint S1.
- Roll back a failed full build to S0.
- WINGS-only removal must not change foundation or unrelated data.
- Full uninstall preserves only the user-approved export and unrelated work.
