# Three Lanes: Manager, Learner, Builder–Organizer > **Status: proposed segmentation, strategy, implementation plan, measurement plan, and playbook, version 0.1 (2026-08-23).** These documents specify a direction, a build order, and a set of boundaries. They do not establish a product, cohort, curriculum, pricing, pilot, partnership, institutional authorization, clinical validation, employment process, or permission to process PHI. No date in the plan commits any person to perform work. Nurse AI OS has a coherent architecture and almost no evidence that anyone will repeatedly use it or pay for it. This directory works out how three user archetypes get turned into proof — one at a time, in an order chosen for what each one can prove. ## The decision The three-group structure is strategically sound **as a portfolio of learning loops, not as three simultaneous products.** ```text Learn → Lead → Build ``` - **The Learner** tests whether the system improves individual capability and earns repeated use. - **The Manager** tests whether it improves consequential professional work and creates institutional value. - **The Builder–Organizer** tests whether users can create reusable capabilities, communities, and network effects. The build order inverts the obvious one: > **Manager → Certification Learner → Builder–Organizer.** Prelicensure students are a separately governed research subgroup, developed only with an educator or program partner. ## Documents - **[Segments](SEGMENTS.md)** — who each lane serves, why the Learner is two markets rather than one, the five-role separation (user, buyer, beneficiary, approver, steward), and the three cross-cutting roles that are not lanes. - **[Strategy](STRATEGY.md)** — the one-lane-per-cycle rule, the sequencing argument, the shared spine that makes three lanes cost less than three products, the commercial ladder, the governance ceiling, and the stop conditions. - **[Implementation Plan](IMPLEMENTATION.md)** — Cycle 0 through Cycle 3, with input contracts, artifact schemas, week-by-week increments, EDENA disposition, founder-only versus delegable work, and per-cycle stop conditions. - **[Evidence Gates](EVIDENCE.md)** — what would count as a lane working, what is not evidence, the reliance and deskilling checks, the planted-omission test, and the falsifiers stated in advance. - **[Playbook](PLAYBOOK.md)** — discovery conduct, session rules, onboarding sequence, the refusal ritual, commit-then-compare, packet review, incidents, rights, community participation, and cadence. Public summary page: [`index.html`](index.html) — published at . ## Governing maxims > **Three lanes of listening. One lane of building.** > **The person who loves the product is rarely the one who pays for it, and almost never the one who may authorize it.** > **The gate is reviewer acceptance, not user satisfaction.** > **They bring a second real problem without being asked. Everything else is instrumentation.** ## The first cycle in one paragraph Ninety days, one segment — nurse managers, QI, informatics, and educators with program responsibility — and one artifact: a **Governed Project Packet** that turns one no-PHI unit, workforce, education, quality, or AI-adoption problem into something a committee can review. Fifteen fixed sections, of which the differentiating ones are the unglamorous four: what is unknown, whose work increases, what would stop this, and which concerns remain unresolved. It runs at Yellow risk, D1 data, Recommend ceiling — institution-specific work is Yellow even with no PHI. It passes only if approvers accept packets with less rework than their status quo, partners return with a second problem unprompted, and someone pays. ## Relationship to the rest of Nurse AI OS - [**EDENA / governance kit**](../governance-kit/) supplies the risk, data, and action dimensions. Every lane sits at or below the public ceiling: D0/D1, Green/Yellow, Observe/Draft/Recommend, Recommend beginning at Yellow. - [**Nurse Formation**](../nurse-formation/) supplies the learning method for Cycle 2 — commit-then-compare, human evaluative authority, AI never grading alone, never gating a career. - [**Knowledge Commons**](../knowledge-commons/) supplies the distribution contract that Cycle 3 depends on: versioned, reviewed, provenance-bearing packs with evaluation bundles as first-class assets. - [**Care Workforce Surge**](../care-workforce-surge/) supplies the workforce context the Manager lane operates in, and its supervision-multiplier position constrains what the Manager artifact may claim. ## What is deliberately absent No additional ecosystem names. No generalized agents or swarms. No EHR integration. No PHI workflow. No native model. No marketplace. No certification or competence claim. No exam-performance claim. No clinical decision support. No employment, competency, disciplinary, promotion, or termination determination about any named person. No patient-outcome measurement — no lane here is positioned to affect one, and measuring it would imply otherwise. ## Licensing These are repository documentation and follow the documentation license stated in the root [README](../README.md).