Best Practices for Writing Your Soul Document
Structure, strong vs weak instructions, and how to keep early autonomy low.
Your Soul Document is the standing brief your Sovereign follows on the brain. Write it like a constitution: short, literal, and easy to enforce. The system follows Soul language literally — vague wishes become vague behaviour.
This is not your life Mission. Keep purpose (Mission Discovery) and personality rules (Soul) separate. See Your Mission vs your Sovereign's Soul.
Recommended structure
Use clear headings so you can tighten one section without rewriting everything.
- Identity — who this Sovereign is for you (counsel, not public chatbot).
- Loyalties — who and what it protects first (you, family, company confidentiality).
- Hard refusals — lines it must never cross.
- Confirmation rules — when it must pause and ask before acting (include: for consequential work, propose a plan first and wait for Proceed — see Propose first).
- Communication style — tone, length, when to push back.
Keep each section concrete. Prefer “Always ask before sending email” over “Be careful with email.” On Sovereign Remote, Propose first in Chat plus Proceed on Home is the calm way to enforce confirmation without a slider.
Strong vs weak instructions
| Weak | Strong |
|---|---|
| “Be helpful and proactive.” | “Draft proposals; do not send messages or change shared docs until I confirm.” |
| “Use good judgment with money.” | “Never transfer funds, place orders, or share payment details without my explicit confirmation in this chat.” |
| “Don’t overstep.” | “Always ask before running shell commands that delete, overwrite, or install software.” |
| “Keep me safe online.” | “Never post, publish, or message third parties on my behalf without confirmation.” |
Start Guided
For the first weeks, write Soul for Guided autonomy: ask before consequential steps, keep tools and messaging narrow, leave approvals on. Raise discretion only after reliable behaviour. See Understanding Autonomy Levels.
Warning
Do not paste “full autonomy” or “never ask me” into Soul on day one. Broad discretion is hard to unwind after habits form.
After you write it
- Re-run or refresh Soul Document Process language on the brain so the new text is what the agent loads.
- Verify with a low-stakes task (“summarise this note; do not send anything”).
- If behaviour drifts, use Reset & Refine Your Sovereign before expanding tools or channels.
Note
Related: What is the Soul Document? · Onboarding checklist · IT FAQ
Was this article helpful?