[EPIC] SOUL file: user-authored agent identity #576

Closed
opened 2026-10-27 13:36:53 +00:00 by sam · 0 comments
Owner

Move Archie's identity and tone out of compiled Go constants and into a user-editable SOUL file. Root cause of a real defect on 2026-07-29: heyarchie answered 'Hey are you there?' with 'I'm here. What do you need?', which reads as demanding the user justify getting in touch. The fix required editing DefaultPersonas() in internal/gateway/persona.go and rebuilding -- personality is not tunable without a compile. Modelled on Hermes (SOUL.md occupies the identity slot in the stable tier, DEFAULT_AGENT_IDENTITY is the fallback when absent, re-read per message so no restart is needed) and openclaw, which injects SOUL.md alongside AGENTS.md.

Design

THE BOUNDARY IS THE POINT. The existing layering rule (recorded in the chat-system-prompt-design memory) is that PersonaRegistry is the style layer only and rules live in the template, so switching persona cannot strip the agent's rules or tool inventory. SOUL inherits exactly that constraint: it owns identity, name, register and warmth, and must not be able to touch core_rules -- otherwise 'be terse' in a SOUL silently disarms the no-fabrication rules. Steal from Hermes: is_legacy_template_soul upgrades untouched scaffolding in place but never overwrites a SOUL the user actually edited. This is the first of the three identity layers agreed with Sam on 2026-07-30: invariants (template, nobody edits at runtime) / SOUL (user-authored) / representation (curator-derived, proposes only).

Acceptance Criteria

A user can name their agent and define its personality by editing a file, with no rebuild and no restart. An absent or empty SOUL falls back to the shipped default identity. SOUL cannot weaken the invariants: <instruction_precedence>, <core_rules>, the block and stay in the template and remain unreachable from SOUL, enforced by a test. A SOUL the user has customised is never overwritten by an upgrade.

Close reason

Closed


Imported from beads archie-core-1786637491030-47-0e6fd3b6 · GitHub #68 · type epic · priority P2 · created 2026-08-08 · closed 2026-10-05

Move Archie's identity and tone out of compiled Go constants and into a user-editable SOUL file. Root cause of a real defect on 2026-07-29: heyarchie answered 'Hey are you there?' with 'I'm here. What do you need?', which reads as demanding the user justify getting in touch. The fix required editing DefaultPersonas() in internal/gateway/persona.go and rebuilding -- personality is not tunable without a compile. Modelled on Hermes (SOUL.md occupies the identity slot in the stable tier, DEFAULT_AGENT_IDENTITY is the fallback when absent, re-read per message so no restart is needed) and openclaw, which injects SOUL.md alongside AGENTS.md. ### Design THE BOUNDARY IS THE POINT. The existing layering rule (recorded in the chat-system-prompt-design memory) is that PersonaRegistry is the style layer only and rules live in the template, so switching persona cannot strip the agent's rules or tool inventory. SOUL inherits exactly that constraint: it owns identity, name, register and warmth, and must not be able to touch core_rules -- otherwise 'be terse' in a SOUL silently disarms the no-fabrication rules. Steal from Hermes: is_legacy_template_soul upgrades untouched scaffolding in place but never overwrites a SOUL the user actually edited. This is the first of the three identity layers agreed with Sam on 2026-07-30: invariants (template, nobody edits at runtime) / SOUL (user-authored) / representation (curator-derived, proposes only). ### Acceptance Criteria A user can name their agent and define its personality by editing a file, with no rebuild and no restart. An absent or empty SOUL falls back to the shipped default identity. SOUL cannot weaken the invariants: <instruction_precedence>, <core_rules>, the <tools> block and <env> stay in the template and remain unreachable from SOUL, enforced by a test. A SOUL the user has customised is never overwritten by an upgrade. ### Close reason Closed --- _Imported from beads `archie-core-1786637491030-47-0e6fd3b6` · GitHub #68 · type epic · priority P2 · created 2026-08-08 · closed 2026-10-05_
sam added the mediumepic labels 2026-10-27 13:36:53 +00:00
sam self-assigned this 2026-10-27 13:36:53 +00:00
sam closed this issue 2026-10-27 13:36:53 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#576