Verified Hermes build kit · Healthcare Researcher & Innovator lane

DISCOVER Mission Control Build Kit

Turn uncertain questions into governed, reviewable paths—without handing AI the authority to determine, approve, contact, submit, deploy, or decide.

DISCOVER is a private planning and orchestration environment for healthcare researchers and innovators. It can support nurses, educators, students, builders, administrators, clinicians, community organizers, and allied healthcare professionals when they are exploring research, QI, implementation, product, grant, evidence, or innovation questions in a governed no-PHI lane.

No PHI or person-level data 24 powers inactive 10 agents disabled 160 criteria specified—not pre-passed
Download DISCOVER build kit → Read the installation boundary

Downloading, opening, or unzipping does nothing automatically. Give the ZIP to your own Hermes. Hermes must begin with read-only preflight, show the exact DISCOVER Implementation Activation Card, and wait for an explicit APPROVE, REVISE, or CANCEL response before making changes.

Our Intent

Nurse AI OS is here to steward AI into nursing practice.

Nurse AI OS is not a replacement for anything you already belong to. Not your unit, not your school, not your professional organization, not your license.

We are not here to compete with existing nursing programs — we’re here to strengthen them.

We are not here to make you rich. Wealth is not the point; integrity is. If value follows good work, good. It follows — it does not lead.

And we are not here to pull you away from the bedside. The opposite. Your clinical practice is the source of your authority. Without it, none of this means anything.

What we are here to do: steward the arrival of AI into nursing practice, so that it happens with nurses at the table rather than around us — and to show, by how we conduct ourselves, what ethical and responsible influence actually looks like.

Stewardship, not disruption. Influence, not extraction.

See the lane

Healthcare Research and Innovation Lead

Identity, authority, and safety boundary

A researcher-and-innovator lane is not institutional authority

DISCOVER uses one isolated healthcare_research_innovation_leadership lane, the research_innovation_discover.* namespace, and one canonical My DISCOVER Mission Control. It can serve nurse leaders and interdisciplinary healthcare researchers or innovators without merging their underlying state into another population.

Selection verifies nothing. A title, credential, employer, technical access, earlier approval, download, or AI capability does not establish identity, delegated mandate, data rights, IRB/HRO/QI status, regulatory or legal authority, scientific validity, safety, funding, intellectual-property rights, publication rights, or permission to deploy.

DISCOVER is separate from the Nurse AI OS Steward’s Charter, the hospital-administrator STEWARD governance preview, Medical Resident ROUNDS, and Respiratory Care BREATHE. The parent Nurse AI OS may receive only product/version, coarse state, and a deep link after explicit approval—not questions, study titles, partners, findings, IP/funding details, private goals, memory, permissions, or traces.

Live clinical concerns, participant-safety issues, adverse events, complaints, and emergencies leave DISCOVER immediately for official local procedures and authorized humans. DISCOVER never assesses seriousness, relatedness, expectedness, reportability, urgency, diagnosis, or care.

Four control frameworks

Questions, evidence, experiments, and agents stay bounded

FRAME

Boundary before determination. Facts and purpose; Risk, rights, review and responsible owner; Activity and interaction; Materials, methods and data; Endpoint and intended use.

It names possible pathways and unresolved questions. It never issues a research, QI, clinical, regulatory, or product determination.

TRACE

Evidence with provenance. Thesis; Reference; Authority; Context; Exceptions, evolution and expiry.

Sources, interpretations, limits, conflicts, corrections, retractions, applicability, reviewers, and next-review dates remain visible.

PROBE

Reversible innovation. Human problem and non-goals; Rights, risk and burden; Options including nontechnology; Bounded non-production test; Evaluation, exit and rollback.

No live patient-facing experiment, procurement, production connection, or scale action follows automatically.

ORBIT

Control every software agent. Objective and owner; Role, rights and restricted data; Bounds; Inspection of frozen hashes; Test, human decision, reconciliation, kill and retirement.

No self-activation, recursive delegation, permission widening, hidden retry, background execution, or approval power.

DISCOVER operating system

Eight commitments across six bounded components

All 24 powers install Available Inactive. All 24 workflows open Preview Only. Activating none is an acceptable end state.

D — Direction, Discovery & Dignity

Mission and impact, unmet need, portfolio choices, and research–QI–clinical–innovation boundary questions without locking in a solution or erasing burden.

I — Inquiry, Integrity & Information Stewardship

Reproducible evidence traces, data/privacy/rights/IP questions, study concepts, and design-option comparisons with uncertainty and corrections visible.

S — Study Design, Safety & Scientific Rigor

Feasibility, burden, safety-readiness, measures, analysis intent, bias, validity, participant rights, and qualified-review routes—never protocol or statistical authority.

C — Collaboration, Community & Capability

Co-design, accessibility, shared decisions, team expertise, conflicts, authorship questions, funding and partner readiness without recruitment, tokenism, or external commitment.

O + V — Operations, Value & Translation

Milestones, dependencies, governance readiness, vendor and pilot questions, non-production experiments, value/equity scenarios, translation, commercialization, scale and stop pathways.

E + R — Evidence, Responsible Innovation & Renewal

Horizon scans, implementation and adoption evaluation, dissemination integrity, bounded agent charters, leadership development, and an optional owner-private whole-life plan.

Governed installation

Download ≠ installation

  1. Give Hermes the entire build-kit ZIP. Do not install modular files individually and do not paste fragments out of order.
  2. Start with the handoff file. Hermes should open GIVE-THIS-PACKAGE-TO-HERMES.md, read README-FIRST.md, verify the manifest and checksums, and inspect only.
  3. Require read-only preflight first. Hermes must confirm the target, package digest, safe defaults, no-PHI boundary, rollback/removal plan, and unsupported capabilities before creating state.
  4. Review the exact Implementation Activation Card. It must show what will be created, what stays inactive/disabled, what data/actions remain prohibited, what evidence will be produced, and what stops the build.
  5. Choose only one post-card response: APPROVE, REVISE, or CANCEL. Silence, timeout, title, credentials, download, file opening, or a prior general request is never approval.
  6. After explicit approval only: Hermes may run the local build plan and produce evidence. Until then, DISCOVER remains unbuilt, inactive, and not operational.
No institutional authority by download. Organizational deployment requires a separately provisioned approved environment, verified authority and governing determinations, approved systems and agreements, data rights, privacy/security review, official records, retention/deletion, incident routes, reconciliation, expiry, and local authorization. This release creates none of those.

The build kit is not operational software until a user-approved Hermes build completes. Repository validation proves the public artifact, manifest, checksum ledger, independently reviewed CI validator, pinned bundled-verifier bytes, safe defaults, and package contract. It does not prove the 160 runtime criteria ran in a target Hermes environment and is not clinical validation, compliance evidence, accreditation, certification, IRB/HRO/QI determination, institutional approval, scientific-validity proof, safety proof, or outcomes evidence.

Inspect before you trust

Release inventory and verification

Self-install build kit

One public-safe derivative ZIP for Hermes inspection and user-approved local build. Download/open/unzip does nothing; CI validates the extracted package, checksum ledger, manifest inventory, and pinned bundled-verifier bytes without executing artifact-controlled code.

Download verified build kit →

Optional Curator MCP profile

Why Nurse AI OS matters: it turns information overload into stewarded signal intelligence. An approved SOUL tells Hermes the curator's mission, audiences, source standards, memory limits, publication boundaries, and red lines; DISCOVER Mission Control organizes watch questions, evidence queues, claim-versus-proof notes, source maps, draft briefs, and human review decisions.

The Curator is an adjacent, conditional companion for healthcare research or innovation public-source discovery—not generic curation or an exact DISCOVER lane identity. If later activated through every separate gate, it could let Hermes retrieve from an approved knowledge vault and bounded public-source channels and prepare traceable drafts without publishing them. MCP connectors remain disabled with zero exposed tools. Activation remains blocked pending a complete transitive lock and lock-consuming runtime. It cannot post, message, vote, validate, or use private/person-level sources; profile installation and every connector require a separate activation card and fresh approval.

Verify profile SHA-256 before extraction →
Download inactive Curator profile →

Optional Builder MCP profile

Why Nurse AI OS matters: it gives healthcare innovation an accountable path from problem framing to testable artifact. An approved SOUL tells Hermes the builder's mission, technical preferences, risk tolerance, ownership boundaries, memory choices, and human-only actions; DISCOVER Mission Control coordinates requirements, prototypes, tests, evidence, versioned artifacts, and release gates.

The Builder / Operator is an adjacent, conditional companion for healthcare research or innovation solution preparation—not a generic software-builder or code-shipping role, and not an exact DISCOVER lane identity. If later activated through every separate gate, it could let Hermes inspect an approved workspace, knowledge vault, documents, calendar, and repository and prepare bounded changes. MCP connectors remain disabled with zero exposed tools. Activation remains blocked pending a complete transitive lock and lock-consuming runtime. It cannot merge, deploy, administer workflows, access secrets, or release externally; profile installation and every connector require a separate activation card and fresh approval.

Verify profile SHA-256 before extraction →
Download inactive Builder profile →

Download DISCOVER build kit ZIP → Download legacy Complete Edition ZIP Read the build-kit safety boundary Browse source on GitHub

Build-kit SHA-256: e028046039800232db75c3d0a09e1105b46f4acfc97071e841b3317f0afcf018

AI prepares. Leaders verify and govern. Authorized humans decide and remain accountable.