# User Guide — Giving the STEWARD Build Kit to Hermes

This guide is for the administrator or Nurse AI OS owner commissioning the build. It does not require programming knowledge.

## What this package does

The build kit gives Hermes the real source baseline, the complete administrator-domain specification and a strict implementation/test contract. Hermes will use it to create a separate downloadable STEWARD application. The ZIP you are reading is the **build instruction package**, not yet the finished administrator application.

## Before you begin

Choose a personal or organization-approved computer and folder. Do not place PHI, patient records, employee/applicant/practitioner records, real incident details, claims, contracts, confidential vendor/security material, nonpublic finance data, passwords, keys or tokens inside this build kit or the Hermes conversation.

Have these nonsensitive answers ready, or use `Unknown`:

- your preferred display name;
- exact administrator title;
- hospital, clinic, service, network, practice or setting;
- legal entity and site when safe to state;
- the active administrative or clinical hat for this setup;
- documented decision rights, threshold, source and expiry;
- named human routes for clinical, workforce, finance, legal, privacy, security, quality and executive decisions;
- the role/setting dashboards you want;
- three current priorities and one 90-day outcome;
- working, learning and communication preferences;
- accessibility needs;
- information Hermes may remember and must not remember; and
- whether you want only offline Mission Control first or also a live Hermes connection.

Do not gather sensitive records to answer these questions.

## Start the build

1. Save the complete ZIP locally and unzip it.
2. From the extracted package root, run `python3 tools/verify-build-kit.py --package .`. To verify the original archive too, add `--zip <path-to-the-versioned-zip>`. On Windows, the command may be `py` or `python`. Stop if the verifier reports FAIL.
3. Read `README-FIRST.md` and `BUILD-STATUS.md`.
4. Start Hermes in a new or verified-isolated implementation workspace.
5. Give Hermes the complete ZIP or extracted folder.
6. Paste:

   > Open `GIVE-THIS-PACKAGE-TO-HERMES.md`, verify the release manifest and checksums, and follow the program exactly. Begin with read-only preflight. Do not install dependencies, edit source, start a service or change my Hermes profile until you show the Implementation Activation Card and I approve it.

7. Review the Activation Card. Confirm the proposed app/data/backup locations, dependencies, role lanes, security model, test plan and live Hermes scope.
8. Choose `APPROVE`, `REVISE` or `CANCEL`.

## Expect several visible phases

The build may take many minutes and several turns:

- S0 freezes sources and creates a safe work copy.
- S1 builds the durable offline core.
- S2 implements STEWARD workflows and governance.
- S3 connects genuine AI, sessions, memory and evidence when available.
- S4 tests, packages and produces the final handoff.

Nothing is complete merely because a turn ended. Save each receipt. If interrupted, paste the resume command from `GIVE-THIS-PACKAGE-TO-HERMES.md` with the last checkpoint.

## Approval boundaries

Approving the build plan does not approve:

- PHI or restricted data;
- public or network deployment;
- an external connector;
- sending, publishing, scheduling, purchasing or changing an official system;
- a personnel, clinical, financial, legal, compliance, accreditation or security decision;
- changes to `SOUL.md`;
- persistent memory beyond the fields you separately approve; or
- agent permission above `PERM-P0 Disabled`.

Hermes must ask separately before consequential environment changes or live-backend testing.

## What to receive at the end

Do not accept screenshots or a hosted demo as the final product. Request:

- the finished versioned application ZIP and SHA-256 checksum;
- exact macOS/Windows/Linux results actually tested;
- application, data and backup locations;
- normal start, stop, health, backup, restore and test commands;
- environment-variable names without their values;
- control-completeness matrix showing zero unresolved visible mocks;
- offline, security, accessibility and clean-install results;
- real Hermes stream/cancel result or an explicit AI-setup blocker;
- remaining production blockers; and
- one exact readiness statement from the master contract.

`Operational` is allowed only after a genuine end-to-end streamed response passes through the packaged application. A useful offline app may truthfully be `Core operational; AI setup pending` when all offline/core criteria pass but no live backend was available.
