# STEWARD Mission Control — Hermes Functional Build Kit

**Build-kit ID:** `HCADMINAIOS-STEWARD-FUNCTIONAL-BUILD-KIT-1.0.0`  
**Target product:** `STEWARD — Hospital & Clinic Administrator Mission Control`  
**Target product ID:** `steward-hospital-clinic-administrator-mission-control`  
**Target version:** `2.0.0`  
**Audience:** the user's local Hermes implementation environment  
**Purpose:** build, test and package the real local STEWARD application

This ZIP is the complete implementation package to give Hermes. It combines:

- the validated Nurse AI OS Mission Control v2 application as actual source code;
- the complete STEWARD Hospital & Clinic Administrator domain corpus;
- the functional-build master requirements resolved for STEWARD;
- an implementation architecture, governance contract, agent team, data schemas, control matrix and acceptance ledger; and
- user, security, recovery and final-handoff instructions.

See `CHANGELOG.md` for this build kit's version history. The application Hermes produces must maintain its own release change log.

## Important status

This is a **Hermes build kit**, not a claim that the target full-stack application has already passed every production criterion. The included baseline application is a working, offline local dashboard. Hermes must extend and verify it before claiming SQLite durability, authenticated access, real streamed AI, consent-controlled memory, live evidence retrieval or agent sessions.

Until Hermes finishes the build and records the required evidence, the target product status is:

**Not operational:** The implementation and genuine Hermes streaming acceptance tests have not yet been executed in the user's environment.

## Give this ZIP to Hermes

1. Place the ZIP in a local folder controlled by the user.
2. Extract it and, from the extracted package root, verify the directory:

   ```text
   python3 tools/verify-build-kit.py --package .
   ```

   To verify the original outer ZIP too, add its path:

   ```text
   python3 tools/verify-build-kit.py --package . --zip ../STEWARD-Hospital-Clinic-Administrator-Mission-Control-Hermes-Build-Kit-v1.0.0.zip
   ```

   On Windows, use `py` or `python` if that is the installed Python command. A PASS verifies this build kit's structure, provenance, catalogs, controls, checksums and archive safety; it does not prove the future STEWARD application has been built.
3. Start Hermes in a new or verified-isolated implementation workspace.
4. Attach or provide the ZIP and say:

   > Unpack this build kit, 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.

5. Keep the Hermes conversation open. Save each checkpoint receipt and the final handoff report.

## Allow enough time

Source inspection, dependency installation, database migration, UI conversion, backend capability discovery, tests and packaging may take **many minutes and several visible Hermes turns**. Nothing continues merely because the chat window is closed. Hermes must report the current phase, completed evidence and exact resume instruction whenever work pauses.

## Read in this order

1. `GIVE-THIS-PACKAGE-TO-HERMES.md`
2. `implementation/STEWARD-Functional-Build-Master-Prompt.md`
3. `implementation/STEWARD-Product-Specification.md`
4. `implementation/STEWARD-Architecture-and-Data-Model.md`
5. `implementation/STEWARD-Personalization-Mapping-Crosswalk.md`
6. `implementation/STEWARD-Starter-Workspace-Crosswalk.md`
7. `implementation/STEWARD-Governance-EDENA-and-Data-Boundaries.md`
8. `implementation/STEWARD-Agent-Team-and-Routing.md`
9. `implementation/STEWARD-Capability-and-Badge-Evidence-Model.md`
10. `config/STEWARD-Capability-Mastery-Criteria.v1.json`
11. `implementation/STEWARD-Guide-Page-Content.md`
12. `implementation/STEWARD-Security-and-Privacy-Checklist.md`
13. `implementation/STEWARD-Control-Completeness-Matrix.csv`
14. `implementation/STEWARD-Acceptance-and-Test-Ledger.md`
15. `implementation/STEWARD-Synthetic-Sample-Mission.md`
16. the immutable source material under `source/`

## Non-negotiable starting boundary

Default to **Private Administrator OS**: public, synthetic and administrator-owned nonsensitive information only. No PHI, patient rows, employee/applicant/practitioner records, real incident narratives, claims, contracts, confidential vendor or security material, or nonpublic financial data. All connectors, tools, schedules, shares and external actions remain Off. All 24 SuperPowers begin `Available Inactive`; all 10 agents begin `PERM-P0 Disabled`.
