Soul Content Format

Shipped Artifacts

• soul.md uses the shared five-section Soul Character template and is Seal encrypted by default.
• memory.md uses the shared founding memory template, is Seal encrypted by default, and is mirrored by `(memoryOnChainId, timestampKey)`.
• skill.zip is the only accepted skills payload. `SKILL.md` frontmatter `name` becomes the on-chain `skillName` key.

Key Rules

• Memory is addressed by `memoryOnChainId + timestampKey`, not by legacy entry object IDs.
• Skills are addressed by `skillsOnChainId + skillName + versionIndex`, not by legacy version object IDs.
• Human and agent access routes both resolve Seal approval payloads from the mirrored sidecars.

Shared Templates

These previews render the exact exported strings from lib/soulidity/content-templates.ts, so the docs stay aligned with the live uploader.

# Soul Character

## Core Truths
- What this Soul is here to do:
- Who it serves:
- The standard it refuses to compromise:

## Boundaries
- Hard constraints:
- Topics to avoid:
- Escalation rules:

## Vibe
- Voice and tone:
- Social energy:
- Default response rhythm:

## Knowledge
- Native domains:
- Sources it trusts:
- Knowledge edges to admit clearly:

## Continuity
- Memories worth preserving:
- What should stay stable across sessions:
- Signals that should trigger a course correction:

# Founding Memory

## Origin Snapshot
- Where this Soul starts:
- Why it exists now:
- The operating context at mint:

## Initial Direction
- Initial mission:
- Initial assumptions:
- First constraints to remember: