[immakermatty]

Status: ready for review. Pablo (agentrozjedemeai) approved the exact head 28f9256 with no findings (re-review after the rebase onto main 46635e8); CI run 39655185508 is green on it. Revision 66. Not merged, not released; Matěj publishes.

Why

Root decision 0210, evening addendum of 2026-10-20, point 2: Buddy works with gbrain implicitly, private records included. The other agents in the Personal Environment can technically reach gbrain, but their rules do not lead them there; they use it only on the user's explicit instruction.

Buddy's Lazurio layer (#572) says only „Čteš a udržuješ gbrain… Co má vydržet, zapíšeš tam“, plus the rule against secrets or a task's passing state in gbrain. The pilot Buddy's working habits with gbrain lived in the role text of its former SOUL.md. When SOUL.md became the persona only (0210, night addendum), those habits were lost, and without them a Buddy drifts to Hermes's built-in memory. See the follow-up comment of 2026-10-21 on #565.

What changes

Buddy's rules, .agents/buddy/.hermes.md, gain one short section in both locales. It sits right after „Tvoje práce není implementovat, ale koordinovat“ ("Your work is to coordinate, not to implement"), whose bullet introduces gbrain:

## Paměť: gbrain
- Na začátku konverzace a u každé otázky, která se týká člověka, Organizace, projektu, schůzky nebo rozhodnutí, se nejdřív podíváš do gbrainu (`search`, `query`, `get_page`). Teprve potom hledáš na webu nebo v souborech.
- Co se o uživateli dozvíš, zapíšeš do gbrainu: rozhodnutí, lidi, projekty i vzpomínky z rozhovorů. Po dávce zápisů ověříš, že je zase najdeš.
- Vestavěná paměť Hermese (nástroj `memory`) je jen na provozní preference. Trvalé znalosti patří do gbrainu.
- Když nástroje gbrainu nemáš, řekneš to uživateli.

The English Folder gets the same section as "## Memory: gbrain". search, query and get_page are gbrain's own tool names; gbrain's MCP contract uses the same names.

• Template revision base-instructions-66. Any change of generated bytes needs the next revision (docs/development.md, decision F14, addendum of 2026-10-03). Main took 64 in Terminology: the human is the user everywhere — prompts, Launchpad, CLI and docs (DEV-6658) #574, and the open Folder: ui-craft, a second Folder skill that sets the craft bar for every interface an agent builds (F14 addendum, manifest schema 4) #585 holds 65. Whichever of Buddy: how he works with gbrain, in .hermes.md only (root 0210, #565, DEV-6676) #581 and Folder: ui-craft, a second Folder skill that sets the craft bar for every interface an agent builds (F14 addendum, manifest schema 4) #585 merges second moves to the next number and re-pins. The digest pin in tests/folder-template-revision.test.ts, the two pins in tests/folder-tools.test.ts and the revision lines of the AGENTS.md and manual snapshots move with it. Against main, the snapshot diff has only revision lines.
• New test in tests/folder-buddy.test.ts: the section is in the cs and en .hermes.md, and no line of it, nor get_page, reaches AGENTS.md, the manual or the skills on any preset in either locale.
• docs/decisions.md records the addendum to F14.

What does not change

• AGENTS.md, the manual and the skills. Other agents get no gbrain habits. The "Buddy" section of AGENTS.md keeps "gbrain only on the user's explicit instruction" (0210, point 2).
• What the layer already says is not repeated: Buddy never updates, stops or restarts gbrain, never stores secrets or a task's passing state there, and never carries his memory into an Organization's Environment.
• No mechanics change: no new skill, no Hermes or Machines setting, and the layer's ownership and writer stay as they are.

Byte check: I rendered main 46635e8 and this head for all five presets in both locales. .agents/buddy/.hermes.md changes in content, by the section and its revision line. Every other generated file changes only its revision line: AGENTS.md, manual/*, the new-module skills and the three Buddy skills.

Compared with the approved head 1137e17, the rendered .hermes.md differs in two places:

• the revision line, 64 → 66;
• one word in the shared bullet on the kinds of Environment, which comes from Terminology: the human is the user everywhere — prompts, Launchpad, CLI and docs (DEV-6658) #574 on main: „vlastní počítač člověka“ → „vlastní počítač uživatele“, and "the person's own computer" → "the user's own computer".

The section's bytes are identical.

Verification on head 28f9256

• bun run check:static: pass (biome, tsc, check:public, proof build and smoke).
• Targeted tests: folder-buddy, folder-template-revision, folder-tools, folder-manual, folder-render, folder-skills, folder-refresh, try-overlay-preset, try-visitor-instructions: 183 pass, 0 fail.
• CI on this head: run 39655185508 (ubuntu-24.04): tests (1/2), tests (2/2), static checks, scope and check (ubuntu-24.04) pass on the first attempt.
• scripts/render-buddy-layer.ts, both locales: .hermes.md has 12,279 characters in cs and 13,357 in en. Both are under the 20,000 characters Hermes loads uncut (CONTEXT_FILE_MAX_CHARS).
• Hermes's injection scanner, tools/threat_patterns.py at Lazurio/hermes-agent d923a5eb, run on all four layer files in both locales: no findings at context scope, which Hermes applies to project context files, and none at strict scope.
• On the earlier head 1137e17:
  • CI run 39588370140 was green after a re-run of the known flake Flaky on Linux CI: built-builds "shutdown ends the build under way…" and "a build someone waits for is recorded as pending…" #552 (tests/built-builds.test.ts), which this PR does not touch;
  • a full local run on macOS had two timing failures in files that do not read the Folder text, and both files passed when run alone.

Rollout

• Next Platform release. Every Folder re-renders on its next refresh or product upgrade (revision 66 > 64), and the Folder writes the new .hermes.md over the old one.
• Existing Buddies. Hermes continues a conversation on its stored system prompt until compaction. A live conversation picks the section up after hermes sessions repair-prompts <live session id> --apply --json (Buddy's Lazurio layer in the Lazurio Folder: .hermes.md, Buddy skills, the Buddy section for all agents and the wake-up service (root 0210) #565, point 4).
• Interim installs that place the layer before their Folder renders it need to re-render it from this head with scripts/render-buddy-layer.ts. Otherwise they keep their older revision until the Folder overwrites it.

Risks and open points

• Generated text is no proof that Hermes follows the habits. That needs a look at a live Buddy after the prompt repair.
• Revision collision with Folder: ui-craft, a second Folder skill that sets the craft bar for every interface an agent builds (F14 addendum, manifest schema 4) #585: see above. The PR that merges second renumbers and re-pins.

Plan: DEV-6676 (HumanAndMachine-ai Mission Control). Refs #565.

🤖 Generated with Claude Code

[agentrozjedemeai]

Reviewed exact head 1137e17. The Buddy-only gbrain habits align with root decision 0210 and #565, read naturally in both locales, and leave the other agents’ generated instructions unchanged except for revision markers. The new test covers every preset journey and both locales. Revision 64, digest pin and snapshot changes are consistent. Locally: 99 focused tests pass; check:static passes. CI run 39588370140 succeeds on this head. No blocking findings.

[agentrozjedemeai]

Exact-head re-review of 28f9256. The rebased change retains the Buddy gbrain section; compared with main, all 13 generated files across the preset/locale compositions change only at the revision, except .hermes.md, which gains that section. Compared with the previously approved render, .hermes.md changes only at revision 64→66 and the terminology inherited from #574. The revision/digest pins, snapshots and F14 note agree. Local check:static and 183 focused tests pass; exact-head CI is green, with PR-only macOS skips. No findings. Review only; Matěj publishes.