Get started
One team. One month.
Twelve artifacts.
You do not need the full architecture to begin — and you do not need new software. The Minimum Viable Version is documents and resolve. Most of its value has nothing to do with AI: it is your team, finally described truthfully.
Before anything else
Take your team's vital signs
One page, eight questions — write it down, folklore and all, and mark the spots where you flinch. The flinches are your map. Prefer guided? The interactive vital-signs tool walks you through all eight, rates each verb green/yellow/red, and exports the result as a report — or as a ready-made prompt your own AI can act on.
List every channel through which work reaches you — including the hallway.
Who decides what a request is, whether it's urgent, whether it's yours? Name the actual humans.
Your team's five recurring outputs. Just five.
Every standing meeting and update, and what each is for. Be honest.
Three things your team knows that exist only in someone's head. Name the heads.
The last thing that went out and shouldn't have. What check would have caught it? Does that check exist?
Who receives your work, and what do they do with it next?
The last time a lesson became a changed procedure. If you can't remember one, write that down too.
The four-week build
The Minimum Viable Version
Each artifact below has a definition of done in the MVV tracker — twelve artifacts with sub-checklists, progress saved in your browser, exportable as a ledger entry or a prompt for your AI to draft the next artifact.
Charter · Catalog · Front door
Write the team charter with its intent clause. Name three services, each with a default risk tier, automation ceiling, evidence level, and gate. Open one intake channel and declare it the front door.
Triage · Workflow · Roles
Stand up triage with a governance profile per request. Map one core workflow, declaring per step: automation level, role, evidence, gate. Draft the role map — every chain ends in a named human.
Knowledge map · Gates · Ledger
Tier your knowledge sources and name their stewards. Design your review gates as active, measured, and independent. Start the audit/evidence log — the ledger.
Dashboard · Brief · Metrics · Loop
Build the task/status dashboard with governance visible. Install the weekly SBAR-shaped brief. Snapshot metrics including gate health. Schedule the first improvement cycle before the month ends.
Then the strange thing happens: the team starts to feel different to be on. Calmer. More honest. Less dependent on heroics. The AI becomes useful in the boring, compounding way instead of the impressive, brittle way.
The full instrument
The Department Configuration Canvas
When you outgrow the MVV, the complete canvas configures the operating model on any team — ICU, marketing, product, finance, nonprofit, creator business. Twenty-four items, in order — and every item is explained in full, with what good looks like, the red flags, and a maturity rubric (Absent → Folklore → Written → Governed), on the canvas rubric page:
| # | Item | # | Item |
|---|---|---|---|
| 1 | Team name & recursion level | 13 | Human review gates (active, measured, independent) |
| 2 | Mission / mandate — with intent clause | 14 | Knowledge sources — tiered, stewarded |
| 3 | Scope: what the team owns | 15 | Data sources & sensitivities |
| 4 | Boundaries: what it does not own | 16 | Tools / systems — the permission matrix |
| 5 | Stakeholders — served vs. governing; harm registry | 17 | Communication rhythm — SBAR, closed loops |
| 6 | Services — each with four governance attributes | 18 | Quality standards per output type |
| 7 | Core workflows — leveled per step | 19 | Risk rules & the prohibited zone |
| 8 | Intake channels by signal type | 20 | Metrics — including governance health |
| 9 | Request types | 21 | Escalation rules — andon, PACE, two-challenge |
| 10 | Priority rules — protection override, slack rule | 22 | Automation permissions (L0–L5 per step) |
| 11 | Roles & owners — the mixed roster | 23 | Audit requirements — the workflow header |
| 12 | Decision rights — the RAPID registry | 24 | Improvement loop — four asset classes, one cadence |
Nurses: start on the governed system itself
Nurse AI OS is the framework's home implementation — a free, nurse-built way to learn AI safely, on your terms, under this architecture. Everyone else: the book walks the full build, chapter by chapter.
The aha moment
When it clicks, it sounds like this
Twelve documents. Not a platform, not a budget line, not a committee. Documents and a month.
I flinched at "uses knowledge." Three things live only in Dana's head — and Dana retires in June.
The vital signs took twenty minutes and told me more than our last two off-sites.
We scored Folklore on almost everything. It all works — until the person it lives in goes on leave.
A team scheduled to 100% has no room for exceptions. So that's why every surprise here becomes a crisis.
My AI drafted the charter skeleton from the export. I edited it for an hour. We've needed that charter for three years.
Week one is just telling the truth about how we work. That's the hard part. That was always the hard part.
The flinch is the map. Twenty minutes, eight questions, nothing leaves your browser. Take the vital signs now →