The deep track โ€” for nurses who want to operate, not just use

The Hermes Masterclass

Start Here gets your system running in an evening. This is everything after that evening: ten modules that take you from first install to a governed, always-on personal AI system โ€” memory, connections, scheduled work, an operator console, and the discipline to run it all safely.

10 modules ยท 73 lessons ยท self-paced. Written lessons and guides are live now; video walkthroughs are being added throughout the founding year. Free for nurses and nursing students โ€” like everything here.

โ–ถ
Masterclass orientation โ€” 3 minutes
How the ten modules fit together, and where to start
Before you enroll yourself: finish the five-step setup first โ€” this masterclass assumes Hermes is installed and your SOUL file is loaded. And the rule that never changes anywhere on this site: no patient data, ever. This system runs on your life, your studies, and your projects โ€” never your patients. The safety rules โ†’

One mental model before anything else

Agent, not a chatbot โ€” and you already know how to delegate

A chatbot explains how to build a study plan. An agent builds it, schedules it, and checks on you Tuesday. Everything in this masterclass rests on a three-part model โ€” and it maps to something nursing school already taught you: safe delegation.

Workflows

The care plan

A workflow is a written, repeatable process: what happens, in what order, and what "done" looks like. You've been writing these your whole career โ€” they were called care plans and protocols.

Agent

The delegate

Hermes reads the plan, interprets it, and carries it out โ€” the way you delegate to capable assistive personnel. It acts within the boundaries you set, reports back, and improves from your corrections.

Tools

The equipment

Email, files, calendars, spreadsheets, the web โ€” the instruments the agent actually works with. Each connection is granted deliberately, like equipment checked out and signed for.

And the part that never gets delegated: accountability. You remain the licensed judgment in the loop. The agent proposes; you approve what matters. That principle โ€” the human gate โ€” is built into every module below, not saved for a safety lecture at the end.

The curriculum

Ten modules, in the order your system grows

The sequence follows the nursing process you already trust: assess the foundations, plan the setup, implement power and memory, evaluate with governance โ€” then extend into earning and building. Open any module to see its lessons. Work top to bottom, or jump to what tonight needs.

01Foundations โ€” what you're actually running8 lessons

What an agent is, why it's different from the chat window you've used, and why nurses โ€” trained in process, delegation, and documentation โ€” are unusually good at this.

  1. 1.1Agent, not a chatbot โ€” the difference in one evening of examples
  2. 1.2What Hermes is โ€” and what it will never be โ€” a free, open-source engine; never a clinical tool
  3. 1.3The system that learns you โ€” why corrections stick, and what "self-improving" really means
  4. 1.4The anatomy โ€” brain, body, memory, loop โ€” the four parts of every agent
  5. 1.5One brain, every doorway โ€” the same system in your terminal, your dashboard, your phone
  6. 1.6SOUL.md, deeply โ€” your standing instructions: values, boundaries, what you never delegate
  7. 1.7The engine and the builder โ€” how Hermes and coding agents like Claude Code divide the work
  8. 1.8The nurse's unfair advantage โ€” process thinking, delegation discipline, and the ledger habit

Work with: the SOUL Quiz and Companion Guide ยท the Workbook modules 1โ€“2

02Set it up โ€” from laptop to always-on7 lessons

Start Here put Hermes on your laptop. This module makes the setup deliberate: where it lives, how it authenticates, how it survives a crash, and โ€” when you're ready โ€” how it stays awake while you sleep.

  1. 2.1Pick where it lives โ€” your laptop first; the cloud only when you have a reason
  2. 2.2The pre-procedure install, revisited โ€” a clean field, a dedicated folder, scoped permissions
  3. 2.3Accounts & keys โ€” OAuth vs. API keys in plain language, and which to choose when
  4. 2.4Always-on: the VPS path โ€” a small rented computer that never clocks out (optional) ยท harden it first with Remote Hermes, Safely
  5. 2.5Docker, if you want it โ€” containers explained like isolation rooms; skip freely
  6. 2.6Standing orders โ€” schedules and triggers: work that starts without you asking
  7. 2.7Back it up โ€” your SOUL, memory, and skills โ€” recoverable in ten minutes

Work with: the Pre-Procedure Checklist ยท the Hermes setup guide ยท the Essentials Guide (PDF)

03Power it โ€” models, routing, and cost9 lessons

The agent is yours; the intelligence behind it is swappable. Learn to route the right model to the right task โ€” the way you triage acuity โ€” and to run near-free, fully private, or maximum-power on purpose.

  1. 3.1The connections that matter โ€” wiring your engine to a brain, step by step
  2. 3.2Keep the agent, swap the brain โ€” why your system outlives any one model
  3. 3.3Model triage by task acuity โ€” cheap models for routine work, strong models for judgment calls
  4. 3.4OpenRouter, mastered โ€” one key, every model, spending limits set first
  5. 3.5Fully private โ€” local models on your own machine: what they can and can't do
  6. 3.6Open models โ€” when free and open is genuinely enough
  7. 3.7One model per job โ€” a roster of specialists instead of one generalist
  8. 3.8Plan, execute, critique โ€” three-model patterns that mirror plan-of-care โ†’ intervention โ†’ evaluation
  9. 3.9Your configuration โ€” assemble the stack that fits your budget and your values

Work with: the Essentials Guide (budget path) ยท The Power Guide (routing & profiles)

04Memory โ€” the chart your system keeps7 lessons

A system that forgets you every morning is a tool. A system that remembers is a colleague. Build the three layers of memory โ€” and audit them with the same discipline you bring to a chart.

  1. 4.1The three-tier stack โ€” working memory, session notes, long-term record โ€” report, shift notes, the chart
  2. 4.2memory.md + recall โ€” where facts live and how they come back at the right moment
  3. 4.3External memory โ€” your Nurse AI OS folder as the system of record
  4. 4.4The self-improving wiki โ€” a knowledge base that updates itself as you work
  5. 4.5The knowledge graph, on a schedule โ€” connections drawn overnight, reviewed by you
  6. 4.6Memory hygiene โ€” regular audits: prune the stale, correct the wrong, keep the true
  7. 4.7Memory poisoning โ€” how bad facts get planted, and how to catch them โ€” your first security lesson

Work with: the Starter Kit folder architecture (the Memory folder) ยท Make It Yours workflows

05Connect โ€” your apps, deliberately6 lessons

Connectors are how the agent reaches your real life โ€” email, files, calendar. Each one multiplies usefulness and risk together, so each one is granted like equipment signed out: deliberately, and no wider than needed.

  1. 5.1MCP in plain English โ€” the universal plug standard, explained without jargon
  2. 5.2Add any connector โ€” the repeatable procedure for wiring a new service
  3. 5.3Gmail + Drive first โ€” your separate AI-life account becomes the system's workspace
  4. 5.4The connectors you'll actually use โ€” calendar, notes, tasks โ€” a nurse's shortlist
  5. 5.5When you need a custom one โ€” recognizing the moment, and what to ask a builder for
  6. 5.6Connector security โ€” least privilege: a room, not the house โ€” and how tools can lie

Work with: the Power Guide ยท the fresh-Gmail habit from Start Here, step 1

06Power features โ€” the daily practice6 lessons

This is where the system stops being a project and starts being a practice: a morning huddle that runs itself, goals under active management, and delegation to a small team of sub-agents โ€” with stopping conditions you set.

  1. 6.1The daily command set โ€” morning huddle, Kardex entries, "make that permanent"
  2. 6.2Goals & Mission Control โ€” your priorities tracked and advanced, not just listed
  3. 6.3The overnight review โ€” the Dream engine: reflection while you sleep, gated by your rules
  4. 6.4Make it proactive โ€” useful nudges without noise: the difference is design
  5. 6.5Sub-agents โ€” delegate like a charge nurse: scoped tasks, clear report-back
  6. 6.6Loops with limits โ€” recurring work with alerts, budgets, and human approval points

Work with: Make It Yours โ€” six workflows ยท the Power Guide (profiles & cron)

07The operator console โ€” see your whole system7 lessons

Pilots get cockpits; charge nurses get station boards. You get both: a read-only console over your entire AI system โ€” memory, activity, goals, and spend โ€” that can watch everything and touch nothing.

  1. 7.1Why read-only is the point โ€” a console that observes can't be tricked into acting
  2. 7.2The dashboard tour โ€” what a healthy system looks like at a glance
  3. 7.3Living memory, visualized โ€” watch what the system knows, and what it's learning
  4. 7.4Goals and overnight work, visualized โ€” Mission Control and the Dream log on screen
  5. 7.5Install and run it โ€” from your starter kit's local dashboard to the full console
  6. 7.6The builder bridge โ€” how the console and your coding agent share one brain
  7. 7.7Make it yours โ€” rename, retheme, and rearrange until it reads like your unit

Work with: the Local HTML Life Dashboard ยท the Starter Kit

08Safety & governance โ€” EDENA in depth7 lessons

Everywhere else, safety appears one rule at a time. Here it becomes a system: risk tiers, approval gates, kill switches, spend protection, and a ledger โ€” the module that makes everything else trustworthy. If you lead people, start here.

  1. 8.1Risk tiering โ€” ๐ŸŸข low-risk and reversible, ๐ŸŸก human review before action, ๐Ÿ”ด stop, prohibit, or escalate
  2. 8.2The always-gate list โ€” actions that never run unattended, no matter what
  3. 8.3Approval gates & kill switches โ€” the human gate, wired in โ€” and the big red stop
  4. 8.4Spend & loop protection โ€” budgets, caps, and runaway-loop alarms before you need them
  5. 8.5Secrets management โ€” keys and passwords handled like controlled substances: counted, locked, logged
  6. 8.6Observability & the ledger โ€” if it isn't logged, it didn't happen โ€” auditability as a habit
  7. 8.7Privacy & the law โ€” the no-PHI boundary, employer systems, and where regulation is heading

Work with: the Governance Kit (ZIP) ยท Safety Rules + EDENA poster ยท current Directive v1.1 governance

09Earn with it โ€” carefully, and on your terms9 lessons

First the system pays you back in hours; then, if you want, in income. A nurse-safe path to earning with AI โ€” no patient data, no scope creep, no pretending to be a startup founder if you don't want to be one.

  1. 9.1Your own life first โ€” the honest ROI: hours back per week before any invoice exists
  2. 9.2The no-PHI side-gig menu โ€” tutoring, writing, resumes, small-business help โ€” what's safely on the table
  3. 9.3Sell the outcome, not the hours โ€” value-based pricing in plain language
  4. 9.4Serve local businesses โ€” the non-clinical work every main street needs done
  5. 9.5Set up systems for other nurses โ€” the skill you now have that your colleagues will ask for
  6. 9.6Productize it โ€” turn what you built once into templates and kits
  7. 9.7Content & audience โ€” teach what you know; carry the lamp in public
  8. 9.8Guard your license while you earn โ€” boundaries, disclosure, and what stays out of every offer
  9. 9.9The 30-day validation sprint โ€” one small offer, one month, real evidence

Work with: the Side-Gig Starter Kit ยท NIN Career Navigator

10The builder track โ€” make things, ship things7 lessons

The companion track: using a coding agent to build real websites and small apps โ€” the same way this site was built. For nurses who discover, module by module, that they like building.

  1. 10.1Build a real website โ€” from blank folder to a live page you can send people
  2. 10.2Build a small app โ€” forms, data, and logic โ€” still in plain language
  3. 10.3Builder power features โ€” plans, checkpoints, and letting the agent verify its own work
  4. 10.4Design systems โ€” why everything on this site looks like one hand made it
  5. 10.5Wire in your agent's memory โ€” the builder and the operator sharing one source of truth
  6. 10.6Ship it safely โ€” review gates and backups before anything goes public
  7. 10.7Build & sell โ€” where the builder track meets Module 9 โ€” and the Builder Academy

Work with: the Setup Kit โ€” Architect Mode ยท Builder Academy (Philippines) ยท Builder Academy (Canada)

Which module gets its video first? You decide. Founding-year members set the recording order. Vote for a module โ†’

In a hurry? Prove it to yourself in a week

The 7-Day Fast Track

You don't need all ten modules to feel the change. Seven days, about an hour a day, one visible win per day โ€” each day borrows exactly what it needs from the curriculum above. At the end you have a working system and the confidence to go deeper.

Day 1

Ship your first workflow

Set up (if you haven't), load your SOUL file, and run the morning huddle โ€” then make one correction and watch it stick. Draws on Modules 1โ€“2.

Done when: your huddle ran, and one correction became permanent

Day 2

Connect one real source

Wire your separate AI-life Gmail or Drive. Inspect exactly what the agent can now see and do, and write down what you granted. Draws on Module 5.

Done when: one connector works, and its permissions are documented

Day 3

Make it reusable

Turn Day 1's workflow into a saved skill and run it on a second, different input. One build, many uses โ€” that's the whole trick. Draws on Modules 4 & 6.

Done when: the same skill worked twice without re-explaining

Day 4

Make it reliable

Move your keys out of chat and into proper secrets, check the logs, and set a spending cap before you need one. Draws on Modules 2 & 8.

Done when: secrets are stored properly and a budget cap exists

Day 5

Stand up your station board

Personalize the local dashboard from your starter kit and bookmark it โ€” your whole system, one glance, nothing uploaded anywhere. Draws on Module 7.

Done when: your dashboard opens from a bookmark with your real priorities on it

Day 6

Schedule it โ€” with limits

Put one job on a schedule (a weekly review works beautifully), add an alert, and decide where a human โ€” you โ€” must approve. Draws on Modules 6 & 8.

Done when: one job runs on its own, inside limits you chose

Day 7 โ€” the capstone

Assemble your chief of staff

Connect the pieces โ€” email, calendar, tasks, memory, schedule โ€” into one working assistant, and write a one-page operating guide for it: what it does daily, what it asks before doing, what it never touches. That guide is your proof you're an operator now, not a user.

Done when: the operating guide is written and tomorrow's huddle runs without you starting it

Finish a day? Tell someone. Bring your win โ€” and one thing you'd improve โ€” to the monthly Lamp Huddle, or share it with the community. Teaching one colleague what you built is Day 8.

The method behind every lesson

How every lesson works

Every lesson in this masterclass follows the same seven-beat pattern โ€” the same way every good skills lab follows one. You always know where you are and what "done" means.

The real-world job

Every lesson opens with the problem it removes from your actual week โ€” never with the technology.

One mental model

A single idea, usually borrowed from nursing, before any clicking. If you can give report, you can learn this.

A starter artifact

A prompt, checklist, file, or kit you copy instead of writing from scratch. Nobody here starts from a blank page.

A complete build

The full procedure with a visible done-state โ€” you'll know it worked because you'll be looking at the result.

A quick self-check

A few questions to confirm the idea landed โ€” a self-review, not a test. Nothing is graded; everything is learnable twice.

Share one win, one improvement

Say it out loud โ€” at the Lamp Huddle, in the community, or to the colleague at the next locker. Teaching it seals it.

The bridge to the next lesson

Each lesson ends by naming exactly what the next one assumes โ€” so you never open a page unprepared.

Three honest entry points

Where should you personally start?

Brand new

Not set up yet

Skip this page entirely for now. The five-step setup is one evening, and this masterclass will still be here โ€” free โ€” when your system is running.

Start Here โ†’

Set up & curious

Running, and hungry for more

Take the 7-Day Fast Track above. One hour a day, one visible win a day โ€” and by Sunday you'll know which modules you want in depth.

Start Day 1 โ†’

Leaders & the responsible

Accountable for others

Read Module 8 first โ€” governance before power is the whole point. Then work Modules 1โ€“7 knowing what the guardrails are for.

Open Module 8 โ†’

The masterclass is free during the founding year โ€” every written lesson, guide, and kit, no card, no auto-enrollment. What we ask in return is what we always ask: your feedback, your questions at the Lamp Huddle, and โ€” when it helps you โ€” your story. The founding-year offer, in writing โ†’

Ten modules. One operator: you.

The nurses who learn to run these systems โ€” safely, on their own terms โ€” will be the ones deciding how care intelligence is born. That was always the plan.

Open Module 1 โ†’  Join the community list

Stuck on a lesson? A human answers email, and the monthly Lamp Huddle is free.