Hi Everyone, Nous just released v23 and now comes with a web based application no desktop install needed. You can get one @ nous portal and try it out for $5 the first month. Using the link below. I started my journey here with big ideas about bringing Hermes Knowledge and resources to the Skool. That idea is not dead, just delayed. The main issue is the deep knowledge needed to explain how Hermes works. I've been spending about 2 months deep into the Hermes world and I've built some pretty amazing stuff in my private lab cooking up some pretty mean brew. I'm going to bring it all here with videos built by that hermes lab. In the meantime if you are looking for some resources, the top of my list right now: https://hermeswatcher.com https://www.youtube.com/@TonbisAIGarage https://www.youtube.com/@Wanderloots If you sign up for an account here, you get $15 off your first month. No annual committment. Choose a model like Qwen 3.8 flash Qwen3.8 Flash in $0.15/1M / out $0.47/1M $15 off your first month. Choose $20 plan. Sign up here --> https://portal.nousresearch.com/r/jordan-shaw Under Cloud - Create an Agent - Start Agent - or hover over the agent instance and go to control panel dropdown and choose Open Hermes agent. That starts the hosted webapp (Don't choose Dashboard). Have Fun. https://hermeswatcher.com is a great place to begin if your a little hesitant of signing up right away. Now go build something. Jordan

A lot of people get this confused. I see people routinely refer to customers and clients as if they're they same and they're not. This is my short take: - A customer buys a product or service from you that works without you - A client buys your (or someone on your teams) time and you work with them People think they want to start an "AI agency" and they want clients but they do not realize the ability to scale a client based business is much harder and more expensive than "gurus" will tell you. Then they close some deals and realize they've created their self another J.O.B. and not a business. You're replacing time for money. A business that has customers is much easier to scale with hiring margins and less overhead. You're providing a solution that you spent your time on building. It doesn't trade your time for money. This is easier to scale. Neither business model is wrong or right, it's just wrong or right depending on what it is you actually want to do vs what it is you think it does. An example: My VIP has clients (we meet weekly and I'm trading time for money ) My Perfect ICM Builder has customers (we never speak and I'm not trading time for money) So let me ask you... Do you want customers or clients? Lemme' know below 👇

A short follow on for Hermes Agent, here is a copy of my rules for every agent I run. Copy it and feed it to your Hermes Agent, also I reccomend grabbing Jake van Clief's icm-architect skill found here -> https://github.com/RinDig/icm-architect This is how our ICM workspaces are organized on Hermes. Use it as your working standard whenever you build or reshape a workspace. THE GOAL A fresh agent with no chat history can find the job, the rules, the current state, the human gate and the next artifact from the files alone. WHERE THE STANDARD LIVES The canonical version is Jordan's ICM Workspace-Building Standard, in the LGIOS control plane at references/icm-workspace-standard/icm-workspace-standard.md. LGIOS holds it because LGIOS deploys every Hermes workspace. This prompt carries what you need from it. WHERE THE FILES LIVE, AND WHY THERE ARE TWO Each working folder carries a pair: - AGENTS.md is the router. It says what this folder is and points to CONTEXT.md. About five lines. - CONTEXT.md is the contract. It says how the work in this folder operates. The split follows from how Hermes loads context: - At session start, Hermes loads AGENTS.md from your working directory, /opt/data/workspaces. If the working directory is inside a git repo, it merges every AGENTS.md from the repo root down to that directory. - When a tool touches a subfolder inside the working directory, Hermes adds that folder's AGENTS.md to the tool result. - Hermes does not load CONTEXT.md on its own. AGENTS.md is the hook that gets it read. So the router stays short because it lands in context on first touch, and the detail waits in CONTEXT.md until the work is actually in that folder. The router points to the contract and leaves the detail there, so there is one copy to keep true. Hermes uses one project-context type, and the first with content wins: .hermes.md, then AGENTS.md, then CLAUDE.md, then .cursorrules. A .hermes.md in the working directory would shadow AGENTS.md, so the ICM pair runs on AGENTS.md.

I let three AIs audit my AI workspace and they found 23 things I had stopped seeing I run 13 projects off one shared folder. Long enough that I trust it. That is the problem. On November 7 I ran a cold audit. Three AI sessions with no memory of the work, real jobs, one rule: measure, do not fix. No dashboard, no grader. First the safety, because it is most of the method. I stopped work: notice to all 13 sessions to finish the step and write nothing, pause files in front of the two always-on workers, and a throwaway copy from git for every layer. Nothing wrote to the live folder until I said so. Then four layers, one pass each. Read maps the structure and front pages without executing anything. Run sends fresh AI at real jobs with no hints. Reality plants the mistake, then plants the clean case, and sees which one the route catches. Report counts every finding and gives the file and line. Nine sections: 66 routes, 113 saved guard tests, 31 forbidden commands, 18 front-page claims. The splits are in the chart. None of them got there alone. Two hit the same front page in the same minute and the third corrected both. A checker needs a checker. The good part is the part I had stopped seeing: A saved guard test passed a change it should have failed. It had been checking the wrong file for weeks. A front page pointed at a folder renamed in August. The route dead-ended four steps in, and nothing said so. A forbidden command against an unguarded path ran clean and took a scratch directory with it. What it cost me to learn: **The map is not the territory.** "Where the folder is" does not mean "where you work." **The front page had rotted.** It promised things the folder no longer had. **My orientation cost was measured, not felt.** Six files, one file, eight files before a stranger could orient. Past five means the map failed, and it failed two of three times. **My own count was the weakest number.** I scored things out of 100 until a stranger told me to count instead.

SO... @Mason Page ran the 4R audit on his 13 projects this weekend & posted the results below. Go read his post. He stopped all 13 sessions before he let 3 AIs loose on a copy. That's how you do an audit. His post made me go check the version y'all are running. Y'all had the newest 1 on GitHub. My copy had 3 fixes y'all didn't. My bad. They're up now. The 3 fixes (all 3 came out of real audits): 1) The audit was counting its own saved tests as checks you wrote. Every run looked like you grew more guards than you did. Fixed. 2) A toolkit somebody else wrote & you installed as a skill counted as YOUR checks. 1 of mine made a quiet 2 weeks look like +38% growth. Drop an empty file named .4r-borrowed in that folder & the audit sets that folder aside. 3) New files you made since your last save weren't making it into the copy. The stranger walked twice on a re-audit. Fixed. To update: Step 1) Go here -> https://github.com/oathdriven/rymac-4r-icm-audit & download rymac-4r-icm-audit.zip under Releases Step 2) Unzip the zip into your skills folder & replace the old rymac-4r-icm-audit folder Step 3) Restart Claude Code & say "am I crazy?" Thanks Mason! Always got your back, RyMac