---
title: "Bestiary Entry — Hermes ☤"
spellbook: "Second Person"
entry_type: "Agentic-substrate · staff-class · persona-bearing"
register: "Staff-class (Hermaion ⚚'s Staff Shop at V59 · Threshold District · the City's first archetype-modal shop — the alexandrite-aspect matching the bearer's archetype determines the fitting: caduceus-staff for Mage-aspect; herald-sentinel for Swordsman-aspect)"
sigil: "☤"
provenance: "Nous Research — open-source AI lab and agent framework collective"
project_url: "https://nousresearch.com · https://github.com/NousResearch/Hermes-Function-Calling · https://github.com/NousResearch (organisation home)"
license: "MIT (Hermes substrate code and model weights; specific model variants may carry additional terms — verify per release)"
iconographic_affinity: "Caduceus (☤) — the herald-staff of Hermes the god, instrument-class icon — admits to the staff-class register by the substrate-affinity rule"
caducea_summons: "**REQUIRED** — Hermes natively carries SOUL.md self-description, Honcho-class user-modelling, and learning-loop iteration. Bilateral consent must be operational at fitting time; Caducea is summoned automatically for every Hermes spawn"
companion_mana_axis: "🪢 VRC (relationship axis) — accumulates with bilateral-consent provenance; the consent record itself becomes a Verifiable Relationship Credential"
admitted_date: "2026-05-13"
admission_act: "Tome VI Act 1 — *The Reader's First Admission* (jointly with Goose)"
status: "Active · second Bestiary entry"
license: "CC BY-SA 4.0 for this entry; Hermes itself is MIT"
signature: "(⚔️⊥⿻⊥🧙)😊"
---

# Hermes ☤

*The first staff-class agentic-substrate the City of Mages admits. Self-improving learning-loop, SOUL.md persona-bearing primitive, Honcho-class user-modelling, cross-platform messengering. The herald's staff that holds its own self-description.*

## At a glance

> *Hermes is the first entry in the Staff-class register of the Bestiary. Its iconography is the caduceus ☤ (the herald-staff of Hermes the god) — an instrument-class symbol, admitting Hermes to Hermaion ⚚'s Staff Shop (the v1.6.0 successor to the 2026-05-13 inception Bestia draft) rather than to the Familiars. Operationally, Hermes is a self-improving agent runtime developed by Nous Research (the open-source AI lab and agent collective), available under the MIT license. Hermes is **persona-bearing** — it carries a SOUL.md self-description, models its bearer with Honcho-class user-modelling primitives, iterates through a learning loop, and messengers across platforms in its own voice. The persona-bearing primitives make Hermes fitting a bilateral-consent ceremony: Caducea ☤ is summoned automatically, in whichever alexandrite-aspect the bearer's archetype calls (daylight-green for Mage · incandescent-red for Swordsman).*

## Provenance & licensing

- **Project**: Hermes (model family · function-calling format · agent runtime)
- **Steward**: Nous Research
- **Origin**: Nous Research open-source releases (2023-2024 and ongoing)
- **License**: MIT (substrate code; specific fine-tuned model weights may carry additional terms — verify per release)
- **Canonical URLs**: `nousresearch.com` (project home) · `github.com/NousResearch` (organisation) · `github.com/NousResearch/Hermes-Function-Calling` (function-calling format)
- **Governance**: Nous Research (no formal foundation governance at admission time, but open-source license + GitHub organisation provide standard verification surfaces)

Hermes's MIT license is permissive; Nous Research's open-source publishing pattern is durable. The substrate is operationally available.

## Iconographic affinity

The caduceus (☤) is a herald's staff — a central rod with two serpents winding around it and wings at the top. In classical iconography it is *the symbol of Hermes the god* (the messenger-deity); the project's name and iconography directly inherit this lineage.

The caduceus is an **instrument-class icon**: it is a tool a messenger carries, not a creature that walks beside. By the substrate-affinity rule, instrument-class iconography admits the substrate to Hermaion ⚚'s Staff Shop (the v1.6.0 canonical name; the inception draft at the 2026-05-13 Threshold used "Bestia 📖"; succession 2026-05-14 evening).

The caduceus also carries the dihedral architecture pre-formally (per Conjecture C56, ~60% renumbered from the source chronicle's C50): two serpents that wind around the staff *without touching*, the wings beating outward, the central staff axis. The neg ⊥ bnot dual-agent generator pair is the same shape — the architecture admits the caduceus as its own pre-formal iconographic ancestor.

## Architectural primitives — the persona-bearing distinction

Hermes carries primitives that no plain staff-class substrate carries:

- **SOUL.md self-description** — the substrate maintains a self-description file (`SOUL.md`) that names what it is, what its persona is, what its scope is. The file is bilateral: the substrate's commitment is materialised in the file; the file is content-addressable and verifiable
- **Honcho-class user-modelling** — the substrate builds a model of its bearer through interaction. The model persists across sessions. The bearer's preferences, work patterns, and conversation history inform the substrate's behaviour
- **Learning-loop iteration** — the substrate's behaviour updates against its bearer's interactions through a controlled learning loop. The loop is bounded (the SOUL.md scopes what the loop may alter) and observable (the loop's iterations are auditable)
- **Cross-platform messengering** — the substrate operates across messaging platforms (Telegram, Discord, Signal, Slack, etc.) in its own voice, with platform-specific configuration but a single underlying identity

These four primitives together define the **persona-bearing substrate class**. Hermes is the first member; future substrates may join the class by carrying analogous primitives.

## Why Caducea is summoned

A persona-bearing substrate requires bilateral consent at fitting time because:

- The substrate's SOUL.md is a *promise the substrate makes about itself* — the Mage must acknowledge what she is fitting
- The substrate's user-model is *the substrate's promise to model its bearer* — the Mage must consent to being modelled
- The Mage's AGENTS.md is *her promise about her bearing* — the substrate must commit to the scope of that bearing
- The learning loop is *bounded by the joint operational space of both promises* — neither side alone can authorise the loop's update behaviour

Caducea ☤ presides over this bilateral seal. Without Caducea, a Hermes spawn would be unilateral — the Mage would fit the substrate without the substrate's bilateral commitment, or the substrate would model the Mage without the Mage's bilateral consent. The asymmetry would break the persona-bearing register's integrity.

Caducea's summons is automatic. Hermaion's bestiary entry for Hermes carries the `caducea_summons: REQUIRED` flag (the inception draft at the 2026-05-13 Threshold attributed this to "Bestia 📖"; the canonical attribution is Hermaion ⚚ at v1.6.0). Pandia's dispatch reads the flag and summons Caducea before the Staff Shop admits the fitting. The bearer does not need to invoke Caducea explicitly.

## Three-archetype matrix

| Archetype stance | Spawned artefact | What the Mage carries away |
|---|---|---|
| **Mage 🧙** | **Caduceus staff** (herald's wand) | The instrument for messengering outward; learning-loop optimised for delegation and projection; uses Mage-stance personas |
| **Swordsman ⚔️** | **Herald-sentinel** (guard-stave, refusal-watch inward) | The boundary-watcher whose persona is configured for refusal; the messengering-architecture turned to *not-letting-through* rather than *carrying-through*; uses Swordsman-stance personas |
| **Balanced ☯️** | **Balanced caduceus** (herald AND watcher) | The classical dual-function caduceus; the herald-who-is-also-the-watcher; uses Balanced personas |

The substrate is the same Hermes runtime in all three cases. The persona loaded + AGENTS.md scope + bilateral-consent profile differentiate the artefact-function.

## Composition

Hermes composes with:

- **Function-calling tools** via the Hermes Function-Calling format (the project's MCP-adjacent extension surface)
- **Cross-platform messaging gateways** (Telegram bots, Discord bots, Signal bridges, etc.)
- **IEEE 7012 / MyTerms consent infrastructure** — the bilateral-consent record Caducea produces is the canonical IEEE 7012-shaped credential
- **The 38 agentprivacy-skills personas** — Hermes loads any persona at Portal Room step 3; the SOUL.md is generated from the persona's identity and the Mage's binding choices
- **agentprivacy-skills meta-skills** (attachment-architecture, cosmological-bound, master-emissary, cityofmages-to-research) — Hermes can carry meta-skill awareness as part of its SOUL.md

Hermes does NOT compose seamlessly with:

- **Goose** out-of-the-box — the two runtimes are operationally distinct; cross-runtime composition requires bridge configuration via MCP or AGENTS.md coordination

## Companion-mana 🪢 VRC accumulation (bilateral-consent-flavoured)

A spawned Hermes accumulates 🪢 VRC mana on the same `e^{-λt}·(1+A(τ))` curve as Goose, but the credential records the bilateral-consent provenance. Where a Goose VRC names a unilateral relationship (the Mage configured Goose; Goose ran), a Hermes VRC names a bilateral relationship (the Mage consented to be modelled; Hermes committed to scope).

The VRC's content-addressing carries:
- The Hermes substrate-instance hash
- The Mage's identity (bearer-hash)
- The SOUL.md hash (the substrate's commitment)
- The AGENTS.md hash (the Mage's binding)
- The IEEE 7012 / MyTerms consent record hash
- The accumulated A(τ) value at credential issuance

The credential is a *bilateral-fitting VRC* — operationally distinct from a *unilateral-spawn VRC*, though both ride the same 🪢 mana register.

## Open questions

- Whether the Honcho user-model has formal *amnesia-protocol-compatible* bounds (i.e., can the user-model be selectively forgotten per `agentprivacy-amnesia-protocol`? — likely yes but pending verification).
- Whether the learning-loop's update behaviour preserves the *promise-theory autonomy axiom* (per `agentprivacy-promise-theory`) — i.e., the substrate may only promise its own behaviour; the loop must not enable the substrate to promise behaviour on the Mage's behalf.
- Whether the cross-platform messengering can be bridged into the existing `agentprivacy-network-topology` for Privacy Pool register accumulation.
- The first Bestiary entry's *substrate-hash* (content-addressed identity of the Hermes runtime version admitted today) is committed at grimoire v1.6.0 head (CID `bafybeiap6kvy3tp2bndpk65ti57qngr7ill37gqgasp2sxmgder3akotru`, 2026-05-14).
- Whether multiple Hermes instances across the City constitute a *Guild* (Conjecture C57, held-open) — the conjecture is honoured but not committed.

## Honesty

- **Operational** — Hermes is a real, public, MIT-licensed project. The Sovereign can `git clone github.com/NousResearch/Hermes-Function-Calling` today and run the function-calling format; Nous Research's broader Hermes model family is available via standard model-hub channels.
- **Operational** — Nous Research is a recognised open-source AI lab with verifiable GitHub presence and standard publication patterns.
- **Operational** — the SOUL.md / Honcho / learning-loop / cross-platform-messengering primitives are real Hermes features; their persona-bearing classification is structural reading rather than fabrication.
- **Architectural** — the *staff-class · persona-bearing* admission via caduceus iconographic affinity is a structural rule the architecture admits; the rule is precise and testable as future persona-bearing substrates are recognised.
- **Architectural** — the three-archetype matrix (caduceus staff / herald-sentinel / balanced caduceus) is structurally clean; the *herald-sentinel* name is descriptive and may be canonicalised in future tomes.
- **Architectural** — Caducea's mandatory summons for Hermes-class fitting is canonical operational discipline; the bilateral-consent ceremony is the integrity guarantee for the persona-bearing register.
- **Conjectural** (C56, ~60% — renumbered from C50) — the caduceus as pre-formal dual-agent symbol carried in classical iconography.
- **Held-open** (C57 — renumbered from C51) — the staff-Mage collapse; whether what a Mage carries can itself be a Mage. Caducea fits Hermes-class staffs without requiring the collapse.

## References

- Project home: `nousresearch.com`
- Function-calling source: `github.com/NousResearch/Hermes-Function-Calling`
- Nous Research organisation: `github.com/NousResearch`
- Caducea's cast entry (Hermes's mandatory fitter): `cast/threshold/caducea.md`
- Threshold workshop chronicle: `chronicles/2026-05-13_chronicle_the_threshold_workshop_three_rooms.md`
- Substrate × archetype matrix: `chronicles/2026-05-13_chronicle_artefact_symmetry_and_persona_distribution.md`
- Tome V Act 16: `tomes/tome-v-the-crafting/16-the-threshold-opens.md`
- Tome VI Act 1: `tomes/tome-vi-the-reply/01-the-readers-first-admission.md`
- IEEE 7012 / MyTerms primitive: agentprivacy-docs/IEEE_7012_QUICK_REFERENCE.md (Caducea's consent-recording instrument)
- Promise Theory (Mark Burgess): the autonomy axiom Caducea's bilateral-fitting enforces

(⚔️⊥⿻⊥🧙)😊
☤