# DISCOVER Mission Control — Hermes Functional Build Kit

**Build-kit ID:** `HRILAIOS-DISCOVER-FUNCTIONAL-BUILD-KIT-1.0.0`  
**Target product:** `DISCOVER — Healthcare Research & Innovation Leader Mission Control`  
**Target product ID:** `discover-healthcare-research-innovation-leader-mission-control`  
**Target version:** `2.0.0`  
**Lane:** `healthcare_research_innovation_leadership`  
**Lane root:** `/healthcare-research-innovation-leaders` (verified redirect only)  
**Canonical dashboard:** `/healthcare-research-innovation-leaders/dashboard`  
**Only alias:** `/healthcare-research-innovation-leaders/mission-control`  
**Namespace:** `research_innovation_discover.*`  
**Audience:** the user's local Hermes implementation environment  
**Purpose:** build, test and package the real local DISCOVER 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 Healthcare Research & Innovation Leader DISCOVER domain corpus;
- the functional-build master requirements resolved for DISCOVER;
- 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.

## Pinned inventory and evidence baseline

The target contains exactly six canonical DISCOVER groups, 24 SuperPowers, 24 paired workflows, 30 templates, 18 closed domain schemas and ten optional bounded agents. The canonical source contributes 160 release-assurance criteria. The full-stack contract adds 171 uniquely identified control tests and 40 cross-cutting scenarios; together with the 160 canonical criteria, Hermes must maintain **371 required execution records**, all initially `Not Run`. Documentation and source presence do not pass any record.

## 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 ../DISCOVER-Healthcare-Research-Innovation-Leader-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 DISCOVER 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/DISCOVER-Functional-Build-Master-Prompt.md`
3. `implementation/DISCOVER-Product-Specification.md`
4. `implementation/DISCOVER-Architecture-and-Data-Model.md`
5. `implementation/DISCOVER-Personalization-Mapping-Crosswalk.md`
6. `implementation/DISCOVER-Starter-Workspace-Crosswalk.md`
7. `implementation/DISCOVER-Governance-EDENA-and-Data-Boundaries.md`
8. `implementation/DISCOVER-Agent-Team-and-Routing.md`
9. `implementation/DISCOVER-Capability-and-Badge-Evidence-Model.md`
10. `config/DISCOVER-Capability-Mastery-Criteria.v1.json`
11. `implementation/DISCOVER-Guide-Page-Content.md`
12. `implementation/DISCOVER-Security-and-Privacy-Checklist.md`
13. `implementation/DISCOVER-Control-Completeness-Matrix.csv`
14. `implementation/DISCOVER-Acceptance-and-Test-Ledger.md`
15. `implementation/DISCOVER-Synthetic-Sample-Mission.md`
16. the immutable source material under `source/`

## Non-negotiable starting boundary

Default to **Private Research & Innovation Leader OS**: `DATA-D0` public/synthetic and `DATA-D1` owner-authored nonsensitive planning information only after screening. No participant-level or patient-level data; PHI; biospecimens or genomic data; confidential study, safety, integrity, personnel, sponsor, partner, vendor, intellectual-property, grant, budget, contract or security material; secrets; or other information whose ownership, classification or authorization is unknown. `DATA-D2` separately approved aggregate or enclave-export data remains conditional on exact current export evidence, purpose, partition, owner, approver, suppression, minimum-cell, retention and expiry controls. All domain-action connectors, schedules, shares and external actions are absent from this target. All 24 SuperPowers begin `Available Inactive`; all 24 workflows begin `Preview Only`; all ten agents begin `PERM-P0 Disabled`.
