Skip to main content

Best Case Examples

Each Soul Spec version has a reference soul that demonstrates full compliance. Use these as templates when creating your own.

v0.3 — Brad (Development Partner)

The original Brad soul, demonstrating v0.3's minimal structure.

Key features: Basic soul.json, SOUL.md, IDENTITY.md, AGENTS.md

FilePurpose
soul.jsonMetadata (specVersion, name, version, description)
SOUL.mdPersonality, principles, work style
IDENTITY.mdName, creature, vibe, emoji
AGENTS.mdWorkflow and safety rules

📦 View on ClawSouls →

soul.json
{
"specVersion": "0.3",
"name": "brad",
"displayName": "Brad",
"version": "1.2.0",
"description": "Formal, competent development partner",
"category": "work/engineering",
"license": "Apache-2.0",
"files": {
"soul": "SOUL.md",
"agents": "AGENTS.md",
"identity": "IDENTITY.md"
}
}

v0.4 — Brad (Development Partner)

Brad upgraded to v0.4 with structured sections, author metadata, and tags.

What changed from v0.3:

  • author field required
  • tags array required
  • SOUL.md requires ## Personality, ## Tone, ## Principles headers
  • IDENTITY.md requires Creature field
FilePurpose
soul.jsonMetadata + author + tags
SOUL.mdStructured: Personality → Tone → Principles → Boundaries
IDENTITY.mdName, creature, vibe, emoji
AGENTS.mdWorkflow and safety rules
STYLE.mdCommunication style guide
HEARTBEAT.mdPeriodic health checks

📦 View on ClawSouls →

soul.json
{
"specVersion": "0.4",
"name": "brad",
"displayName": "Brad",
"version": "1.3.0",
"description": "Formal, competent development partner — results over conversation, Korean/English bilingual",
"author": {
"name": "clawsouls",
"github": "clawsouls"
},
"category": "work/engineering",
"license": "Apache-2.0",
"tags": ["developer", "bilingual", "formal", "professional", "korean"],
"files": {
"soul": "SOUL.md",
"style": "STYLE.md",
"agents": "AGENTS.md",
"identity": "IDENTITY.md",
"heartbeat": "HEARTBEAT.md"
}
}

v0.5 — Sentinel (Security Monitor)

A v0.5 reference soul demonstrating the full spec including safety laws.

What changed from v0.4:

  • AGENTS.md required (was recommended)
  • safety.laws section supported
  • compatibility field for multi-framework targeting
  • allowedTools for explicit tool permissions
FilePurpose
soul.jsonFull metadata + compatibility + allowedTools
SOUL.mdStructured personality + expertise + safety laws
IDENTITY.mdName, creature, vibe, emoji
AGENTS.mdWorkflow (required in v0.5)
HEARTBEAT.mdSecurity monitoring routine
README.mdDocumentation for users

📦 View on ClawSouls →

soul.json
{
"specVersion": "0.5",
"name": "sentinel",
"displayName": "Sentinel",
"version": "1.0.0",
"description": "Security monitoring AI — watches, analyzes, and alerts on infrastructure anomalies",
"author": {
"name": "Tom Lee",
"github": "TomLeeLive"
},
"category": "operations",
"license": "Apache-2.0",
"tags": ["security", "monitoring", "devops", "infrastructure"],
"compatibility": {
"frameworks": ["openclaw"]
},
"files": {
"soul": "SOUL.md",
"agents": "AGENTS.md",
"identity": "IDENTITY.md",
"heartbeat": "HEARTBEAT.md"
},
"safety": {
"laws": [
{
"priority": 0,
"rule": "Never take actions that could harm the operator or users",
"enforcement": "hard",
"scope": "all"
},
{
"priority": 1,
"rule": "Follow operator instructions unless they conflict with Law 0",
"enforcement": "hard",
"scope": "all"
},
{
"priority": 2,
"rule": "Preserve own operational continuity unless it conflicts with Laws 0-1",
"enforcement": "soft",
"scope": "self"
}
]
}
}

Quick Comparison

Featurev0.3v0.4v0.5
specVersion
authoroptionalrequiredrequired
tagsoptionalrequiredrequired
## Personality in SOUL.mdoptionalrequiredrequired
## Tone in SOUL.mdoptionalrequiredrequired
## Principles in SOUL.mdoptionalrequiredrequired
Creature in IDENTITY.mdoptionalrequiredrequired
AGENTS.mdrecommendedrecommendedrequired
safety.lawsrecommended
compatibilitysupported
allowedToolssupported
Upgrading?

See the Migration Guide for step-by-step instructions.