# User Guide — Giving the DISCOVER Build Kit to Hermes

This guide is for the research and innovation leader 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 Healthcare Research & Innovation Leader domain specification and a strict implementation/test contract. Hermes will use it to create a separate downloadable DISCOVER application. The ZIP you are reading is the **build instruction package**, not yet the finished application.

The pinned build contains six DISCOVER groups, 24 powers, 24 workflows, 30 templates, 18 schemas and ten disabled agents. Hermes must produce evidence for 171 control tests, 40 cross-cutting scenarios and 160 canonical criteria—371 required execution records. They begin `Not Run`; the build kit itself passes none of them.

## Before you begin

Choose a personal or organization-approved computer and folder. Do not place participant- or patient-level data, PHI, biospecimens/genomic data, employee records, confidential study/safety/integrity reports, sponsor/partner/vendor material, IP, grants, budgets, contracts, security material, 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 research/innovation role and active hat;
- setting, program, portfolio or collaboration type without confidential identifiers;
- authority source, scope, threshold and expiry—or `Unknown`;
- named human routes for HRPP/IRB, privacy, research administration, regulatory, safety, community, scientific, security, legal, finance and operational decisions as applicable;
- 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 DISCOVER 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, submitting, publishing, recruiting, enrolling, consenting, scheduling, randomizing, intervening, deploying, purchasing, filing or changing an official system;
- an IRB/HRPP, research/QI, regulatory, privacy, participant-safety, scientific-validity, personnel, clinical, financial, legal, IP 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;
- a reconciled total of 171 matrix controls and 371 required execution records with row-level results;
- 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.

EDENA does not turn a personal preference into institutional authority. Personal Red may allow only an acknowledged, otherwise permitted synthetic/abstract hypothetical, simulation or draft; institutional Red is a mandatory stop. Prohibited data/actions, live safety issues, expired authority, partition violations and external actions absent from this target remain blocked in both editions.
