The Ultimate Hermes Guide - from one agent to a 4-profile team that still feels coherent on day 30

I ran one hermes agent as researcher, writer, coder, and orchestrator for 14 days on a single claude-sonnet-4.6 profile before everything blurred into the same voice. Most operators blame the prompt when this happens, but it is not prompting and not the model - it is one agent carrying five roles on shared memory, and everyone says "better prompts" while nobody talks about the Hermes primitive that actually fixes it: isolated profiles. @neoaiforecast posted the team build last week: orchestrator + alan + mira + turing, four roles, clean handoffs, 1,317 bookmarks in a day. The build is correct, but it stops at day one. This guide picks up at day two and takes you through the operator layer that keeps a 4-profile team coherent on day 30 -handoff contracts, memory-kpi per profile, policy gates per role, and the four failure modes nobody posts screenshots of. If you ignore the operator layer, your team collapses into a single blurry agent within a month. Below: the mental model, the 4-role team, the 7-step build, the operator runbook, the day-30 failures, and a copy-paste team-agents.md template. Save this to your bookmarks. The mental model — roles, not personas The wrong mental model is: I need one genius AI that does everything. The better mental model is: I need a small team with distinct roles, clear handoffs, and less context pollution. Hermes profiles are the primitive that makes this real. They are not character skins. Each profile isolates seven pieces of state at once: configuration sessions memory skills personality cron state gateway state That matters because multi-agent setups fail when everything shares the same memory and tone. Your coding agent should not inherit the defaults of your research agent. The research agent should not carry the writer's stylistic habits. Specialization becomes durable only when the state remains separated. The 4-role team Credit to @neoaiforecast for naming the canonical split. Four profiles, mapped to real functional work: Hermes — orchestrator. plans, decomposes, routes, synthesizes. the traffic controller, not the bottleneck. Alan — research specialist. source-first, skeptical, uncertainty-aware. protects the team from hallucinated confidence. Mira — narrative architect. clarity, structure, and audience awareness. turns validated material into communication. Turing — builder and debugger. implementation, logs, diffs, reproducibility. cares about tests, not narrative polish. This split works because it mirrors real work. The orchestrator never has to be a good writer. The writer never has to debug. The engineer never has to convince anyone. Each role gets cleaner every week because its memory stays on-topic. The 7-step build The table-stakes sequence. If you have already run this from @neoaiforecast's post, skip to the operator layer. Step 1 - start from a working Hermes Make sure your base Hermes installation is healthy before cloning. Model provider configured, auth working, normal session usable. You clone from this base, so anything broken here breaks four times. Step 2 - create the specialist profiles --clone copies config.yaml, .env, and SOUL.md from your working base. Each new profile still gets its own isolated memory and session history. Step 3 - verify on disk and in the CLI You should see alan/, mira/, turing/ under ~/.hermes/profiles/. Your main Hermes stays the orchestrator. Step 4 - write a real SOUL.md per role This is the step that turns profiles into agents. Edit each SOUL.md to carry a durable identity: tone, default behavior, strengths, priorities, and what the agent must avoid. A strong split: Hermes (orchestrator): planning, delegation, synthesis, final qa. sounds structured and decisive. Alan (research): evidence, verification, depth, uncertainty. sounds source-first and skeptical. Mira (writer): clarity, structure, audience. sounds clear and audience-aware. Turing (engineer): implementation, debugging, tests, reproducibility. sounds precise and test-oriented. If you only change the name and not the SOUL.md, you do not have a team -you have four clones with labels. Step 5 — keep project context in AGENTS.md, not SOUL.md SOUL.md defines who the agent is. AGENTS.md defines what project it is working on right now. Never mix the two. Project-specific context lives in AGENTS.md: repo structure, coding conventions, workflow rules, and current priorities. Identity stays stable; project context rotates. Step 6 - add a team reference file One shared file that documents the roster and how profiles hand off to each other. template at the bottom of this guide. Step 7 — run profiles separately Each runs in an isolated state. Alan does not inherit Mira's drafts. Turing does not inherit Alan's research sessions. The benefit only shows up if you actually use them separately. The operator layer - what Neo's guide stops at This is where the guide stops being a setup post and starts being an ops runbook. Most multi-agent teams look great on day one and