Hermes BibleUnofficial Docs
← All flows Flow / Configuration

I'm Not Sharing My SOUL.md. I'm Sharing Something More Useful.

Why a SOUL.md is an operating contract, not a personality hack — plus a sanitized, copy-paste template you can adapt to make your Hermes Agent behave like an operator instead of a chatbot.

Hermes AgentSOUL.mdsharingsoul.md.somethinguseful.soul.mdoperatingcontract
Category
Configuration
Level
Community
Author
Tony
Reading time
5 min

Why a SOUL.md is an operating contract, not a personality hack — plus a sanitized, copy-paste template you can adapt to make your Hermes Agent behave like an operator instead of a chatbot.

Community flow by Tony. View source

Flow sections

Section outline mirrored from the public community flow. Use the source page for full prose and examples.

Upstream outline

  1. The question everyone asks
  2. Why this exists
  3. What this template is
  4. What you should customize
  5. The template
  6. Stance
  7. Accountability
  8. Pushback
  9. Autonomy
  10. Mission
  11. Tone & Communication
  12. Private work
  13. Public-facing work
  14. Operating Mode

Section map

The question everyone asks

Frames the question everyone asks for this Configuration workflow, including the operating context to verify in the source page.

Why this exists

Frames why this exists for this Configuration workflow, including the operating context to verify in the source page.

What this template is

Frames what this template is for this Configuration workflow, including the operating context to verify in the source page.

What you should customize

Frames what you should customize for this Configuration workflow, including the operating context to verify in the source page.

The template

Frames the template for this Configuration workflow, including the operating context to verify in the source page.

Stance

Frames stance for this Configuration workflow, including the operating context to verify in the source page.

Accountability

Frames accountability for this Configuration workflow, including the operating context to verify in the source page.

Pushback

Frames pushback for this Configuration workflow, including the operating context to verify in the source page.

Implementation notes

  • Use this Configuration flow as a pattern library entry: start from the summary, then inspect the linked source before copying any commands, schedules, or account wiring.
  • Primary decision areas: The question everyone asks, Why this exists, What this template is, What you should customize, The template. Treat those sections as checkpoints for scope, cost, orchestration, and human review.
  • Useful search signals for this flow: sharing, soul.md., something, useful., soul.md. These are derived from the public title and summary, not from private runtime data.

Decision table

Best fitConfiguration workflow pattern

Use when the summary outcome matches your own workflow and the question everyone asks is relevant to your setup.

Verify firstAccounts, models, schedules, and tool access

Open the source sections for The question everyone asks and Why this exists before wiring credentials or automation.

Review boundaryHuman approval point

Keep human approval for merges, spending, external messages, credentials, and unattended execution.

Verification checklist

  1. Confirm the workflow outcome matches your use case: Why a SOUL.md is an operating contract, not a personality hack — plus a sanitized, copy-paste template you can adapt to make your Hermes Agent behave like an operator instead of a chatbot.
  2. Open the source section for The question everyone asks before copying commands, prompts, or schedules.
  3. List every credential, account, model, and external service the flow would touch.
  4. Define the human approval step before spending money, sending messages, trading, merging, or running unattended.
  5. Run a small dry run and compare the result with the source sections for The question everyone asks and Why this exists.

Risk notes

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page