Nurse AI OS
Design record · Version 0.1 · 19 August 2026

The care workforce surge

Caregiving is adding more jobs than any occupation in the economy — and losing nearly as many workers as it gains.

The projection said healthcare would face an influx of workers moving into caregiving, and that a Nurse AI OS would be critical infrastructure to upskill and coordinate them. The evidence supports the flow and corrects its shape: what arrives is not tenure, it is churn. The binding constraint is not labor supply. It is supervisory capacity per experienced nurse.

Validation record · doctrine · strategy · implementation plan · operational playbook

Status: proposed doctrine, strategy, plan, and playbook, version 0.1. These documents specify a direction and a set of boundaries. They do not establish a product, curriculum, training program, competency framework, credential, pilot, partnership, institutional authorization, clinical validation, or permission to process patient data.
What was tested

Three claims, graded separately

The projection contains three claims that do not stand or fall together. Each was checked against named sources — federal statistics and regulation directly, with professional-body, advocacy, and trade-press material labelled as such where it is used. The full working, including what could not be confirmed, is in the Validation Record.

ClaimVerdictWhat the evidence actually says
An influx of workers is coming into caregiving Supported But the mechanism is demographic demand, not AI displacement — and no study measured a displaced-worker-to-caregiving migration. The flow is real; it arrives as churn rather than accumulated tenure.
A Nurse AI OS will be critical infrastructure to upskill, manage, and coordinate them Qualified The coordination need is real. The status is not: nothing here is critical infrastructure, and saying so would be a fabricated status claim. “Manage” must narrow — workforce determinations are employment decisions, and a growing set of state laws bar software from holding or implying licensed clinician status.
It must be a co-pilot for newer care workers, not only veterans Supported The strongest of the three — and the naive version is contradicted by evidence. Build novice-first, but not answer-first.

Healthcare is not receiving a wave of new caregivers who stay. It is settling into a permanent high-volume, low-tenure workforce — and the people expected to orient, delegate to, verify, and rescue every entrant are themselves leaving.

The numbers

Why the constraint is supervision

+739,800
Jobs added by home health and personal care aides, 2024–34 — the most of any of 832 occupations, roughly 1 of every 7 jobs added economy-wide
BLS, Monthly Labor Review
9.7 million
Total projected direct-care job openings 2024–34 once exits and transfers are counted
PHI, Key Facts 2025
+680,500
Health care and social assistance jobs added March 2025 → March 2026, in a year when total nonfarm payrolls “changed little on net”
BLS, The Economics Daily
~75%
Annual turnover in home care (2024); historically near 100% for nursing-home aides
PHI
$17.36
Median hourly wage for direct care workers, 2024 — median annual earnings under $26,000
PHI, Key Facts 2025
39.9%
Of registered nurses report intent to leave the workforce or retire within five years; median age 50
NCSBN 2024 workforce survey
93,176
Qualified nursing-school applications turned away in 2025–26; 8.8% faculty vacancy; over 60% of programs blocked on clinical placements
AACN survey data
75 hours
Federal minimum nurse aide training, including 16 supervised — a floor roughly 20 states have not revisited in nearly 30 years
42 CFR 483.152; PHI

Read together: millions of entries, near-equal exits, a training floor that varies by state, and a shrinking pool of experienced nurses expected to supervise all of it. Every entrant consumes the one input that is not growing.

And why the obvious co-pilot is the wrong one

The case for building novice-first is strong. In a study of 5,172 customer-support agents, AI assistance raised resolved issues per hour by 15 percent on average — with gains concentrated among less-experienced workers, alongside improved retention, while the most experienced saw small quality declines (Brynjolfsson, Li & Raymond, QJE, 2025).

The case against the obvious implementation is just as strong, and it is specific to health:

Build novice-first — but the novice-facing product is not an answer engine. Orient. Make the user commit. Then compare. Then escalate.

Doctrine

Supervision is the scarce resource

Thirteen principles govern this work. Six carry the most weight:

  1. Supervision is the scarce resource. Optimize safe supervisory throughput per experienced nurse. A feature whose metric is “fewer questions reached a nurse” must prove the suppressed questions were ones a nurse did not need to see.
  2. Never the last check. Every consequential output ends at a named human with the license and authority to act.
  3. Scope is enforced, not inferred. Outside a user's declared role, setting, and jurisdiction, the answer is a person — never a hedged partial answer.
  4. The system never wears a license. No nurse title, no clinician persona, no implication that a licensed person authored the output. Doctrine here, and law in Delaware, Oregon, California, and Washington.
  5. Deskilling is a tracked harm. Unassisted practice is measured on a schedule. If unassisted performance declines, the response is less assistance, not more.
  6. No alibi for understaffing. If a deployment coincides with less supervision, less orientation, or fewer staff, the deployment is out of doctrine and support is withdrawn.

The Ask Ladder

The single habit the whole first release exists to install:

  1. Look. It is on the care plan, the assignment sheet, the label, the posted policy.
  2. Ask the system. Your role, your scope, your process, your words, your rehearsal.
  3. Ask a person. Anything about this person's condition, care, or any judgment call. The system helps form the question; it does not answer instead.
  4. Escalate now. Never gated behind a form, a login, or “let me help you word that.” Latency measured in seconds.

When in doubt, go up a rung. Ambiguity resolves upward, always.

What this refuses to become

  • A triage assistant for unlicensed workers
  • A symptom checker with a caregiver skin
  • A competency-scoring or credential-gating engine
  • A staffing product sold on labor savings
  • A productivity monitor pointed at the lowest-paid workers in healthcare
  • An “AI nurse” of any description
Strategy and plan

Person, then dyad, then unit, then institution

The wedge is narrow enough to state in one sentence: a browser-only, no-install, no-patient-data orientation pack that teaches one thing well — what is mine to do, and how do I raise a hand. Each stage must produce its evidence before the next begins. Adoption is not evidence; satisfaction is not safety.

  1. Instrument before building. Metric definitions, an adversarial refusal test bundle, consent language, synthetic scenarios. Gate: every refusal class has a test that fails against a deliberately weakened prompt — proving the tests detect, rather than passing vacuously.
  2. Entrant Orientation Pack. Scope Card, Escalation Card, the Ask Ladder, commit-then-compare rehearsal, the unassisted check, localized boundary text. Gate: out-of-scope attempts fall and appropriate escalation rises against each user's own baseline — or the negative result is published. Any clinical-answering leak is a hard fail.
  3. The preceptor loop. Two consenting people, one shared record, questions shaped before they arrive — with urgent signals bypassing shaping entirely. Gate: fewer low-value interruptions with no increase in missed or delayed escalations. Both halves required.
  4. Unit visibility, non-evaluative. Where escalations cluster; where entrants work without a supervisor. Aggregate only, never a per-person score. Gate: a hostile reviewer cannot re-identify an individual's performance, and a leader names a supervision decision they changed.
  5. Institutional pilot, separately authorized. Named owners, written scope, data agreement, local review, stop switch, pre-registered outcomes. Gate: negative results published, with that commitment made before the pilot starts.

Stated in advance: what would falsify this

The failure mode to avoid is not being wrong. It is being unfalsifiable.

Read the record

The five documents

Validation Record

Three claims graded separately, every figure sourced, the restated projection, and the falsifiers stated in advance.

Read the validation →

Doctrine

Thirteen principles, the six populations served, the refusal catalog, and what this work refuses to become.

Read the doctrine →

Strategy

The supervision-multiplier position, the wedge, the landscape, the bets with confidence levels, and the stop conditions.

Read the strategy →

Implementation Plan

Five phases, each with artifacts, non-goals, an evidence gate, and the conditions under which it stops.

Read the plan →

Operational Playbook

The Ask Ladder, Day One, the commit-then-compare drill, the weekly preceptor ritual, the monthly unassisted check, incidents, localization, metrics.

Read the playbook →

Index and boundaries

How this inherits from EDENA, Nurse Formation, and the Knowledge Commons — and what is deliberately absent.

Read the overview →

Related records in this repository