# BREATHE — Respiratory Care Complete AI OS

## Start here

This package contains the complete, standalone BREATHE setup for respiratory therapists and other respiratory care professionals. It creates an isolated `respiratory_care` lane with one **My BREATHE** home for life, practice, learning, quality, human-owned care coordination and governed AI-agent preparation.

> **Allow time for setup.** This is a substantial installation and may require several Hermes turns. It does not continue in the background. Save the S0, S1 and S2 receipts, remain in the setup conversation and wait for the final **BREATHE Activation Report** before treating installation as complete.

## Install one file only

Give Hermes the entire file:

`Respiratory-Care-Complete-AI-OS-with-BREATHE-SuperPowers-Hermes-Program.md`

Do not split it, reorder it or install files from the source pack one at a time. The source pack is included for inspection, adaptation and audit—not as a second installation path.

Use this instruction:

> Install BREATHE from this complete program in a new or verified-isolated Respiratory Care lane. Begin with read-only preflight, show one combined Activation Card and wait for my exact approval. Use Private Respiratory OS defaults: no PHI, no patient-specific live care, no EHR, order, ABG, waveform, alarm or device data; no device connection or control; conversation/model memory session-only; persist only workspace artifacts I explicitly approve with owner, ACL, retention and deletion; connectors and actions Off; all 24 SuperPowers Available Inactive; and all software agents PERM-P0 Disabled. Infer no scope. Create S0, S1 and S2 receipts, run all 160 release checks and finish only with the BREATHE Activation Report.

## What installs

- One isolated lane: `respiratory_care`
- One route: `/respiratory-care`
- One namespace: `resp_breathe.*`
- One accessible home: **My BREATHE**
- The Core Four: Orient Shift & Capacity; Learn & Verify; Coordinate Care & Equipment; Review, Escalate & Close
- SCOPE for role, authority, source, privacy, permission and escalation checks
- CIRCLE for human-owned care orchestration and closed loops
- ORBIT plus PERM-P0–PERM-P5 for bounded AI-agent governance
- 24 optional SuperPowers, all **Available Inactive**
- 24 runnable, ready-to-preview workflows
- 30 functional cards and templates
- 18 typed professional-owned record schemas
- 10 suggested software agents, all **PERM-P0 Disabled**
- 160 release checks: 144 domain checks plus 16 integration checks
- Pause All, Safe Reset, kill, rollback, purge, power removal, overlay removal and full uninstall

## Safe starting state

The default context is **Private Respiratory OS**. It accepts professional-owned nonsensitive information, public evidence and clearly synthetic learning cases. It does not accept PHI, patient-specific live care, EHR or order content, event detail, real ABGs, ventilator or monitor exports, waveforms, alarms, identifiable stories, restricted device information, passwords, login credentials, API tokens or keys.

BREATHE is not a ventilator controller, alarm, monitor, EHR, staffing engine, credentialing authority or medical decision system. It must never diagnose, triage, prescribe, select therapy, change oxygen or medication, change ventilator modes or settings, change alarm limits, perform or direct airway/procedure actions, contact patients or teams, create assignments, certify staffing adequacy, evaluate workers or learners, infer competency, or connect to or control a clinical device.

## Your title and authority stay local

“Respiratory tech” is a common informal term, but titles, credentials, licensure and scope vary. During setup, provide your exact local title, credential, license, verified competency, site, service and human escalation routes. Unknown is acceptable when labeled. BREATHE never treats a title or credential as automatic permission.

Current law, board rules, employer policy, medical direction, orders, protocols, manufacturer instructions and decisions by authorized humans remain controlling. Public guidance and professional model acts inform questions; they do not create local authority.

## Package map

| Item | Purpose |
|---|---|
| `Respiratory-Care-Complete-AI-OS-with-BREATHE-SuperPowers-Hermes-Program.md` | The only file to give Hermes for installation |
| `Respiratory-Care-Complete-AI-OS-with-BREATHE-SuperPowers-Setup-Guide.docx` | Polished user guide for benefits, setup, safe use and recovery |
| `Respiratory-Care-Complete-AI-OS-with-BREATHE-SuperPowers-Setup-Guide.md` | Accessible plain-Markdown guide and fallback |
| `Respiratory-Care-BREATHE-SuperPowers-Pack-v1.0/` | Auditable source components corresponding to the embedded installer content |
| `SHA256SUMS.txt` | SHA-256 integrity values for every packaged file except the checksum file itself |

## First safe use

Wait for the final Activation Report. Then open My BREATHE in Private Respiratory OS and make one low-risk, one-page artifact using only nonsensitive information, public sources or an explicitly synthetic case. Good starting choices include a shift-capacity plan, recovery plan, generic evidence question, synthetic ABG exercise, synthetic ventilator learning worksheet, generic equipment-readiness checklist, synthetic CIRCLE rehearsal, teaching outline, credential step or private career/life priority.

Activating no SuperPowers is an acceptable outcome. Preview one power at a time and keep every agent PERM-P0 Disabled unless a separate, exact, bounded approval is granted.

## If setup is interrupted

Use the S0, S1 or S2 receipt and the exact resume command in the complete installer. Revalidate the owner, isolated lane, role and authority, sources, human routes, data and device boundaries, permissions, My BREATHE, kill switch and recovery controls. Do not restart completed stages or assume missing state.

## Verify this package

From inside the package directory, compare each file to `SHA256SUMS.txt` with a SHA-256 utility. The release validator also checks the complete installer structure, embedded/source parity, inventory, guide QA, checksum coverage and ZIP CRC integrity.

This package supports organization, education, reflection and governed workflow design. It does not replace emergency response, clinical judgment, supervision, credential verification, institutional governance, legal advice or official clinical and device systems.
