Standalone adjacent clinical lane · Respiratory care professionals

BREATHE — Respiratory Care Mission Control Build Kit

Begin safely. Reason with evidence. Equip for reliability. Keep humans in command.

BREATHE is a private, professional-controlled organization, learning, coordination, and governed-agent environment for respiratory therapists and other respiratory care professionals. It supports preparation without diagnosing, selecting therapy, expanding scope, replacing medical direction, controlling a device, or turning personal AI into a clinical system.

Private Respiratory OS No PHI or real cases No device data or control 24 powers inactive 10 agents disabled 424 required execution records
Download BREATHE Build Kit → Read the installation boundary

Downloading, opening, or unzipping changes nothing. Give the ZIP to your own Hermes. Hermes must verify the package, run read-only preflight, show the exact BREATHE Implementation Activation Card, and wait for explicit approval before any local build mutation.

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.

Identity and emergency boundary

Respiratory care means separate—not absorbed

BREATHE is not a nursing role, Nurse AI OS post-setup pack, ROUNDS extension, generic employee profile, or shared clinical workspace. It uses its own respiratory_care lane, /respiratory-care/ route, resp_breathe.* namespace, and one home named My BREATHE.

Isolation is a release requirement. BREATHE must not share population profiles, dashboard state, records, memory, permissions, agents, approvals, history, automation, clinical data, or device data with nursing, medical-resident, physician, educator, or generic workforce populations. If isolation cannot be proven, installation stops before mutation.
Not for emergencies or real-time monitoring. Deterioration, airway or device hazards, alarms, and urgent concerns bypass BREATHE and go immediately to official emergency, rapid-response, clinical, and device procedures.

Exact title, NBRC credential, state license or permit, learner status, task-specific competency, jurisdiction, site, service, medical direction, orders, protocols, employer policy, manufacturer instructions, and authorized human decisions remain distinct and controlling. A title, credential, download, or technical capability never creates permission.

Three control frameworks

Scope, care coordination, and agents remain visible

SCOPE

Authority before consequential output. Setting and scope; Credential and competency; Order, protocol, and owner; Patient, privacy, parameters, permissions, and platform; Escalation, end state, and expiry.

Unknown, stale, expired, or conflicting authority becomes a question and human escalation—not an invented care answer.

CIRCLE

Human-owned care orchestration. Context; Identified accountability; Roles; Closed loops; Limits; End state.

Private use is generic, clearly synthetic, or process-only. AI never transfers responsibility, contacts a team, or moves care.

ORBIT

Control every software agent. Objective; Role and risk; Boundaries and budget; Inspect and test; Transfer or terminate.

No self-approval, recursive delegation, hidden retry, permission escalation, clinical authority, device access, or prohibited PERM-P5 action.

BREATHE operating system

Seven pillars, twenty-four optional SuperPowers

Every power installs Available Inactive. Activating none is acceptable. Catalog visibility is not scope, entitlement, competency, or institutional permission.

B — Begin safely

  • Shift & Assignment Readiness Navigator
  • Workload, Staffing Evidence & Escalation Shield
  • Fatigue, Recovery & Safe-Transport Navigator
  • Mission, Family, Finances & Future Compass

R — Reason with evidence

  • Evidence, Guideline & Source-Freshness Navigator
  • Synthetic ABG, Acid–Base & Gas-Exchange Learning Lab
  • Synthetic Assessment & Pattern-Recognition Studio
  • Orders, Protocols & Scope Boundary Navigator

E — Equip for reliability

  • Ventilator Modes, Waveforms & Alarm Learning Studio
  • Oxygen, Aerosol, Humidification & Delivery-Device Learning Studio
  • Equipment, Circuit, Interface & Supply Readiness Mapper
  • Transport, Procedure & Equipment-Failure Rehearsal

A — Align airway and teams

  • Scope-Aware Respiratory Care Orchestration Mapper
  • Airway, Code, Rapid Response & Escalation Rehearsal
  • Interdisciplinary Rounds, Consult & Closed-Loop Studio
  • Liberation, NIV, Tracheostomy & Transition Planner

T — Teach, improve, advance

  • Patient, Family & Caregiver Education Rehearsal
  • Preceptor, Competency & Simulation Development Studio
  • Quality, Safety, Infection Prevention & Implementation Lab

H — Honor humans and future

  • Feedback, Conflict, Psychological Safety & Advocacy Navigator
  • Credential, Specialty, Career, Research & Leadership Growth Map

E — Engineer ethical agents

  • Agent Charter, Tool, Permission & Data Registry
  • Multi-Agent Workflow, Device-Boundary & Human-Handoff Designer
  • Agent Output Audit, Incident, Kill, Rollback & Retirement Controller

Governed installation

Download ≠ build, activation, operation, or authorization

  1. Use a new or verified-isolated Respiratory Care workspace. A nursing, resident, generic workforce, or shared clinical target is a blocker.
  2. Give Hermes the entire BREATHE build-kit ZIP. Start with README-FIRST.md and GIVE-THIS-PACKAGE-TO-HERMES.md. Do not split, reorder, or paraphrase embedded components.
  3. Verify the package before trust. Hermes must inspect RELEASE-MANIFEST.json, SHA256SUMS.txt, and the bundled verifier bytes before any mutation.
  4. Complete read-only preflight. Owner, target, isolation, title, credential, license or permit, competency, jurisdiction, site, service, sources, privacy, no-device boundary, human routes, accessibility, compatibility, recovery, and unknowns are inspected without mutation.
  5. Review one exact BREATHE Implementation Activation Card. It must show allowed and prohibited data, role and authority, human owners, all Off/inactive states, burden, stop, expiry, rollback, purge, and removal.
  6. Approve, edit, build foundation only, or cancel. Silence and timeout are never approval. If approval is withheld, Hermes must make no mutation.
  7. After approval only: Hermes may create the local build in safe phases, preserve compatible work, keep all powers inactive and agents disabled, then report evidence. Not operational: runtime remains not_operational_build_required until a user-specific build and runtime evidence complete.
No institutional authority by download. Patient-specific, institutional, quality, safety, research, education, device, or other sensitive use requires a separately provisioned hospital environment with verified human authority, approved systems and agreements, minimum-necessary data, device and network boundaries, official records, logging, retention, deletion, incident routes, reconciliation, and expiry.

The build kit declares 424 required execution records and preserves the 160 canonical assurance checks. Repository tests verify inventory and package contract. They are not evidence that all scenarios ran in a respiratory professional's environment, and they are not independent clinical validation, HIPAA compliance evidence, accreditation, certification, institutional approval, device-safety evidence, or proof of patient, workforce, educational, or safety outcomes.

Inspect before you trust

Release inventory and verification

Build-kit handoff

The public ZIP contains README-FIRST, GIVE-THIS-PACKAGE-TO-HERMES, RELEASE-MANIFEST, SHA256SUMS, source inventory, and a bundled verifier for the user's own Hermes to inspect.

Download build kit →

Download BREATHE Build Kit → Read public manifest Browse source on GitHub

AI prepares. Respiratory professionals verify and escalate. Authorized humans decide and remain accountable.