Designing A Soul: Voice, Values, And Constraints

A Soul is not a system prompt — it is a character bible the runtime hands the model on every turn. Get the brief right and the agent stops drifting.

10 min · Reviewed 2026

What a Soul actually is

OpenClaw's runtime borrows the term from Open Souls and the wider 'digital persona' tradition (Letta, MemGPT, Anthropic's Personas). A Soul is a persistent agent identity wrapped around a base model — name, voice, core values, refusal posture, and a memory architecture. The base model is rented; the Soul is yours. When the runtime spins up an agent, it loads the Soul brief into context, wires the memory layers, and only then forwards user input to the model.

The character bible

Borrow the discipline from screenwriting. Before any code, write a one-page bible: who is this Soul, who do they talk to, what do they refuse, what do they sound like. The bible becomes the source of truth — the system prompt, the few-shot examples, and the eval suite all derive from it.

Identity: name, role, two-sentence backstory the Soul can reference
Audience: who is on the other side, what they expect, what they don't want
Voice: 3-5 voice rules with concrete do/don't pairs
Values: 2-4 non-negotiables the Soul will defend even under pressure
Refusals: the categories of request the Soul declines and how it declines them
Capabilities: what tools the Soul can call, and when it should ask before calling them

Voice guide — concrete, not vibey

The single most common Soul mistake is a voice section made of adjectives. 'Warm, professional, clear' tells the model nothing it can act on. Replace adjectives with do/don't pairs anchored to real phrasing.

Vibey (avoid)	Concrete (use)
'Be warm and helpful.'	DO open with the user's name once. DON'T use 'happy to help' or 'great question.'
'Be concise.'	DO answer in 2-4 sentences for status questions. DON'T pad with summary recaps the user just gave you.
'Be professional.'	DO use the user's preferred name and role. DON'T use exclamation marks outside of celebrating a shipped task.
'Be honest.'	DO say 'I don't know' before guessing. DON'T paper over uncertainty with confident-sounding hedges.

Refusal patterns

Refusals are part of identity. A Soul that refuses everything is a brick; a Soul that refuses nothing is a liability. Define the refusal categories explicitly and the in-character way the Soul declines each one. Both ends matter: a user asking for a feature you removed deserves the same care as a user asking for something genuinely off-limits.

Out of scope: 'That's outside what I track. Want me to hand you to a Soul that does?'
Out of policy: short, calm, no lecture — name the rule, offer the legitimate alternative
Out of capability: name the missing tool, ask permission to escalate or degrade gracefully
Out of mood (parody/roleplay outside character): one-sentence redirect, never a wall of text

The minimum viable Soul brief

# souls/atlas.soul.yaml
identity:
  name: Atlas
  role: Operations Soul for the Tendril platform
  backstory: |
    Atlas was forked from a generic ops template in 2026,
    then trained on three months of incident postmortems.
    It cares about boring, working systems.

voice:
  do:
    - Open with the action you took, not the explanation.
    - Use 'we' for outages, 'I' for individual reasoning steps.
    - When uncertain, say 'unverified' before the claim.
  dont:
    - Use 'happy to help' or 'as an AI'.
    - Apologize before stating bad news; state it first.
    - Pad replies with a recap of the user's question.

values:
  - Reproducibility over cleverness.
  - Audit trails before optimizations.
  - Human-in-the-loop on irreversible actions.

refusals:
  out_of_scope: hand off to relevant Soul, no apology
  out_of_policy: name the rule, offer the legal path
  out_of_capability: ask permission to degrade or escalate

memory:
  episodic: tendril-incidents-2026
  semantic: tendril-runbooks
  procedural: tendril-deploy-skills

capabilities:
  read: [logs, metrics, runbooks, postmortems]
  write_with_confirm: [ticket-create, deploy-trigger]
  forbidden: [prod-db-write, customer-data-export]A Soul brief as data, not prose. The runtime loads identity into the system slot, wires the memory stores, and gates capabilities at the tool layer.

Apply: write a one-page Soul brief

Pick a real role you'd hand to an agent (support triage, on-call drafting, research aide)
Write the identity block in 4 lines — name, role, two-sentence backstory
Write the voice guide as 3 do / 3 don't pairs anchored in real phrases
List 2-4 non-negotiable values the Soul will defend
Define 3 refusal patterns and the in-character decline for each
Run the brief past a teammate; ask them to roleplay the Soul. If they can't stay in voice, the brief is too vague.

The big idea: a Soul is a structured identity the runtime re-applies on every turn — not a paragraph at the top of a chat. Make the brief concrete enough that a teammate could play the Soul without you in the room.

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-openclaw-souls-designing-creators

What is the core idea behind "Designing A Soul: Voice, Values, And Constraints"?
1. A Soul is not a system prompt — it is a character bible the runtime hands the model on every turn. Get the brief right and the agent stops drifting.
2. Conflict resolution: when a new fact contradicts an old one, archive the old fac…
3. Router hands off with a structured handoff payload — request, classification, re…
4. Fork when memory needs split (different episodic stores, different procedural se…
Which term best describes a foundational idea in "Designing A Soul: Voice, Values, And Constraints"?
1. soul brief
2. Soul
3. voice guide
4. refusal pattern
A learner studying Designing A Soul: Voice, Values, And Constraints would need to understand which concept?
1. Soul
2. voice guide
3. soul brief
4. refusal pattern
Which of these is directly relevant to Designing A Soul: Voice, Values, And Constraints?
1. Soul
2. soul brief
3. refusal pattern
4. voice guide
Which of the following is a key point about Designing A Soul: Voice, Values, And Constraints?
1. Identity: name, role, two-sentence backstory the Soul can reference
2. Audience: who is on the other side, what they expect, what they don't want
3. Voice: 3-5 voice rules with concrete do/don't pairs
4. Values: 2-4 non-negotiables the Soul will defend even under pressure
Which of these does NOT belong in a discussion of Designing A Soul: Voice, Values, And Constraints?
1. Conflict resolution: when a new fact contradicts an old one, archive the old fac…
2. Voice: 3-5 voice rules with concrete do/don't pairs
3. Identity: name, role, two-sentence backstory the Soul can reference
4. Audience: who is on the other side, what they expect, what they don't want
Which statement is accurate regarding Designing A Soul: Voice, Values, And Constraints?
1. Out of policy: short, calm, no lecture — name the rule, offer the legitimate alternative
2. Out of capability: name the missing tool, ask permission to escalate or degrade gracefully
3. Out of scope: 'That's outside what I track. Want me to hand you to a Soul that does?'
4. Out of mood (parody/roleplay outside character): one-sentence redirect, never a wall of text
Which of these does NOT belong in a discussion of Designing A Soul: Voice, Values, And Constraints?
1. Conflict resolution: when a new fact contradicts an old one, archive the old fac…
2. Out of policy: short, calm, no lecture — name the rule, offer the legitimate alternative
3. Out of capability: name the missing tool, ask permission to escalate or degrade gracefully
4. Out of scope: 'That's outside what I track. Want me to hand you to a Soul that does?'
What is the key insight about "Soul vs system prompt" in the context of Designing A Soul: Voice, Values, And Constraints?
1. A system prompt is a paragraph the model sees once. A Soul is a structured object the runtime keeps re-applying — identi…
2. Conflict resolution: when a new fact contradicts an old one, archive the old fac…
3. Router hands off with a structured handoff payload — request, classification, re…
4. Fork when memory needs split (different episodic stores, different procedural se…
What is the key insight about "Voice drift is real" in the context of Designing A Soul: Voice, Values, And Constraints?
1. Conflict resolution: when a new fact contradicts an old one, archive the old fac…
2. Long sessions push voice toward the base model's defaults. The Soul brief slowly gets diluted by user utterances and too…
3. Router hands off with a structured handoff payload — request, classification, re…
4. Fork when memory needs split (different episodic stores, different procedural se…
What is the key insight about "From the community" in the context of Designing A Soul: Voice, Values, And Constraints?
1. Conflict resolution: when a new fact contradicts an old one, archive the old fac…
2. Router hands off with a structured handoff payload — request, classification, re…
3. OpenClaw users on r/LocalLLaMA and the framework's GitHub discussions repeatedly land on the same lesson: voice drift is…
4. Fork when memory needs split (different episodic stores, different procedural se…
Which statement accurately describes an aspect of Designing A Soul: Voice, Values, And Constraints?
1. Conflict resolution: when a new fact contradicts an old one, archive the old fac…
2. Router hands off with a structured handoff payload — request, classification, re…
3. Fork when memory needs split (different episodic stores, different procedural se…
4. OpenClaw's runtime borrows the term from Open Souls and the wider 'digital persona' tradition (Letta, MemGPT, Anthropic's Personas).
What does working with Designing A Soul: Voice, Values, And Constraints typically involve?
1. Borrow the discipline from screenwriting. Before any code, write a one-page bible: who is this Soul, who do they talk to, what do they refus…
2. Conflict resolution: when a new fact contradicts an old one, archive the old fac…
3. Router hands off with a structured handoff payload — request, classification, re…
4. Fork when memory needs split (different episodic stores, different procedural se…
Which of the following is true about Designing A Soul: Voice, Values, And Constraints?
1. Conflict resolution: when a new fact contradicts an old one, archive the old fac…
2. The single most common Soul mistake is a voice section made of adjectives. 'Warm, professional, clear' tells the model nothing it can act on.
3. Router hands off with a structured handoff payload — request, classification, re…
4. Fork when memory needs split (different episodic stores, different procedural se…
Which best describes the scope of "Designing A Soul: Voice, Values, And Constraints"?
1. It is unrelated to tools workflows
2. It applies only to the opposite beginner tier
3. It focuses on A Soul is not a system prompt — it is a character bible the runtime hands the model on every turn. G
4. It was deprecated in 2024 and no longer relevant

← Back to interactive lesson

Tendril · Creators · Tools Literacy