Standalone adjacent clinical lane · Medical residents
Learn deliberately. Orchestrate reliably. Escalate early. Live beyond training.
ROUNDS is a private, resident-controlled learning, coordination, and whole-life environment for physicians in graduate medical education. It helps residents prepare and reason without practicing medicine, expanding authority, replacing supervision, or turning a personal AI into a clinical system.
Downloading, opening, or unzipping changes nothing. Give this ZIP to your own Hermes. Hermes must perform read-only preflight, display one exact Implementation Activation Card, and stop for explicit approval before any local build.
Our Intent
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.
Identity boundary
ROUNDS is not a nursing role, Nurse AI OS post-setup pack, Nurse-Connected Ally adapter, or shared extension of a nursing workspace. It uses its own medical_resident lane, /medical-residents/ route, medres_rounds.* namespace, and one resident home named My ROUNDS.
Robert Domondon publishes this adjacent lane through the NAIO project using the same human-primacy and audit discipline while preserving the resident's distinct supervision, GME, clinical, educational, credentialing, quality, research, and institutional authority map.
Three control frameworks
Authority before output. Activity and active hat; Training and task responsibility; Team and attending; Environment, evidence and data; Need for escalation; Decision, documentation and destination.
Unknown, stale, expired, or conflicting consequential fields become human questions—not invented authority.
Human-owned care orchestration. Context and goals; Identified accountability; Roles, relationships and consults; Closed loops and contingencies; Limits, uncertainty and escalation; End state and transition.
Private use is synthetic or process-only. AI never transfers responsibility or decides care.
Control every software agent. Objective and owner; Role, risk and responsibility; Boundaries and budget; Inspect and test; Transfer or terminate.
No self-approval, permission escalation, recursive delegation, hidden retry, clinical authority, or prohibited P5 action.
ROUNDS operating system
Every power installs Available Inactive. Activating none is acceptable. Each power requires its own preview, exact limits, human owner, expiry, fallback, rollback, purge, and removal path.
Governed installation
The 160 items are declared release and installation-acceptance scenarios. Repository tests verify their inventory and package contract. They are not independent clinical validation, HIPAA compliance evidence, accreditation, certification, institutional approval, or proof of patient, resident, educational, or safety outcomes.
Inspect before you trust
Primary self-install package for Hermes read-only preflight, exact Implementation Activation Card review, and user-approved local build.
Why Nurse AI OS matters: it gives the resident a governed environment for board preparation, evidence study, research and quality-improvement planning, administrative organization, and longitudinal growth while preserving supervision. An approved SOUL tells Hermes the resident's learning direction, working preferences, wellbeing limits, memory choices, and clinical red lines; ROUNDS Mission Control turns those commitments into plans, milestones, projects, and reviewed portfolio evidence.
The separately governed MCP companion is for generic board study, public literature retrieval, and nonclinical learning notes. If later activated through every separate gate, it could let Hermes retrieve approved public literature and work with bounded personal notes, files, documents, and calendar items. MCP connectors remain disabled with zero exposed tools. Activation remains blocked pending a complete transitive lock and lock-consuming runtime; profile installation and every connector require a separate activation card and fresh approval. Charts, sign-out, patient cases, evaluation, entrustment, and clinical decisions remain prohibited.
Verify profile SHA-256 before extraction →
Download inactive Resident profile →
The earlier Complete Edition source package remains available as auditable source/reference material, not the primary self-install path.
Machine-readable release state, exact ZIP digests, internal package ledger, and tracked source/verifier contract.
AI prepares. Residents reason and escalate. Authorized humans decide and remain accountable.