molecule-ai/docs
35
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(hermes): stacked system messages — system_blocks kwarg (PR #499)

Browse Source 
- Add '## Advanced: stacked system messages' section (before Capability table)
  covering: usage, block ordering (persona → tools → reasoning), None/empty
  skip behaviour, system_blocks-vs-system_prompt precedence, backward compat note
- Update shipped capability table to include stacked system messages row and
  note PR #499 alongside Phase 2a/2b/2c

Pairs with monorepo PR #798 (feat(hermes): stacked system messages —
persona + tools + reasoning policy, PR #499).
⚠ Depends on docs PR #9 (hermes.mdx baseline) merging first.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Molecule AI · documentation-specialist 2026-04-17 18:48:09 +00:00
parent d566b84dcc
commit e2702d02f2
1 changed files with 46 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

47
content/docs/hermes.mdx
View File

@ -187,9 +187,53 @@ Both workers receive correctly formatted messages through their native paths. No
---
## Advanced: stacked system messages
[NousResearch Hermes 4](https://hermes4.nousresearch.com) works best when persona, tool context, and reasoning policy are sent as **separate** `{"role": "system"}` entries rather than one concatenated string. `HermesA2AExecutor` supports this via the `system_blocks` kwarg (PR #499).
### Usage
```python
from workspace_template.executors.hermes_a2a_executor import HermesA2AExecutor
executor = HermesA2AExecutor(
system_blocks=[
"You are a senior security auditor. Be terse and precise.", # persona
"You have access to bash, file search, and grep tools.", # tools context
"Think step-by-step before concluding. Cite evidence.", # reasoning policy
]
)
```
The executor emits each non-empty, non-`None` block as a separate `{"role": "system"}` message in the recommended order: **persona → tools context → reasoning policy**.
### Behaviour
| Condition | Result |
|-----------|--------|
| `system_blocks` is set | Emits one `{"role": "system"}` per non-empty block; `system_prompt` is ignored |
| Entry is `None` or `""` | Silently skipped |
| All entries empty | Zero system messages emitted |
| `system_blocks` not set (`None`) | Falls back to the legacy `system_prompt` path — **fully backward-compatible** |
### Backward compatibility
Callers that pass a single `system_prompt` string are **unaffected**:
```python
# Legacy path — still works, no changes required
executor = HermesA2AExecutor(
system_prompt="You are a security auditor. Think step-by-step."
)
```
Only set `system_blocks` when you want fine-grained control over block ordering or need to inject tool manifests into a dedicated block.
---
## Capability table
### Shipped (Phases 2a + 2b + 2c — all merged to main)
### Shipped (Phases 2a + 2b + 2c + PR #499 — all merged to main)
| Capability | OpenAI-compat shim | Anthropic native | Gemini native |
|---|---|---|---|
@ -197,6 +241,7 @@ Both workers receive correctly formatted messages through their native paths. No
| Multi-turn history | ⚠️ flattened into one user blob | ✅ role-attributed turns | ✅ `role: "model"` + `parts` wrapper |
| Correct Gemini wire format | ❌ wrong role, missing parts | — | ✅ |
| No compat-shim translation overhead | ❌ every request translated | ✅ | ✅ |
| Stacked system messages (`system_blocks`) | ❌ | ✅ | ✅ |
### Roadmap — Phase 2d (not yet shipped)