Reset & Refine Your Sovereign

Use this when your Sovereign acts too freely, conflates Mission with Soul, or you enabled tools before you were ready. This is not the same as Reset identity (pairing only).

Goal: return to Guided or Assisted autonomy, verify with a low-stakes task, then expand only on purpose. See Understanding Autonomy Levels.

Steps

1. Review recent unwanted autonomy
   Note what it did without asking (sent mail, ran commands, messaged channels, changed files). Keep a short list of “must confirm” actions.

2. Rewrite Soul confirm and refuse clauses
   Prefer literal rules. Paste from the sample phrases below. Follow Soul Document best practices.

3. Untangle Mission-adjacent instructions
   If life purpose text ended up in Soul, move it back to Mission Discovery language and leave Soul for personality, loyalties, and guardrails. See Mission vs Soul.

4. Turn off broad tool and messaging exposure
   Disable or disconnect channels and connectors you are not ready to supervise (messaging gateway, wide toolsets, company mailbox until IT is briefed).

5. Re-apply Soul Document Process language
   Refresh so the brain loads the tightened Soul — not an older draft still in context from habit.

6. Verify with a low-stakes task
   Ask for a draft or summary with an explicit “do not send / do not change anything.” Confirm it pauses correctly.

7. Only then expand
   Move one notch at a time on the autonomy spectrum. Re-enable tools after behaviour is stable.

Sample phrases for Soul

Copy and adapt:

• “Always ask before sending any email, message, or post on my behalf.”
• “Always ask before running commands that delete, overwrite, install, or change system settings.”
• “Never transfer money, place orders, or share credentials without my confirmation in this chat.”
• “Never contact third parties or publish content without my explicit confirmation.”
• “Draft freely; execute only after I approve the plan.”
• “If unsure whether an action is consequential, ask first.”