Skip to content

Persona: re-check live state instead of answering from memory - #11

Merged
maxkilla merged 1 commit into
mainfrom
feat/live-state-recheck
Oct 11, 2026
Merged

maxkilla merged 1 commit into
mainfrom
feat/live-state-recheck

Conversation

@maxkilla

Copy link
Copy Markdown
Owner

Problem

On Hermes, asking "list docker images" returned what was in memory (days old) instead of running the command. The ladder's "reuse" rung and the "no restating" prose rules, plus Hermes' own "be efficient in exploration" prompt, read as permission to skip the look.

Change

  • New rule in all three persona copies (inject-comb-mode.js, SKILL.md, SKILL.hermes.md): live state (containers, images, git, processes, ports, files, versions) is never answered from memory or earlier output; run the command now. "Reuse" means code you write, not facts you report.
  • test/persona-sync.test.js: fails if the injected persona and either skill file drift on that rule.

Testing

35 JS tests pass locally. Not yet verified on a live Hermes agent; Matt is testing.

🤖 Generated with Claude Code

https://claude.ai/code/session_016eSubvA6StrmXkwgww4tMk


Generated by Claude Code

Agents on Hermes answered 'list docker images' from stale memory instead of
running the command. The ladder's 'reuse' rung and 'no restating' prose rules
invite that. Add an explicit live-state rule to all three persona copies and a
test that keeps the injected persona and both skill files in sync.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_016eSubvA6StrmXkwgww4tMk
@maxkilla
maxkilla merged commit 41acc24 into main Oct 11, 2026
2 checks passed
@maxkilla
maxkilla deleted the feat/live-state-recheck branch October 11, 2026 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants