---
enforcement: medium
activation: summary
summary: Read and apply the selected SOUL identity before generating content; preserve factual accuracy, follow per-agent overrides, and honor stricter completion standards.
bound_to:
  skills:
    - soul-apply
    - soul-enable
    - soul-create
    - soul-blend
    - soul-enhance
    - soul-validate
    - soul-to-voice
    - voice-to-soul
---

# Soul Enforcement

**Enforcement Level**: MEDIUM
A SOUL.md file is present at @SOUL.md.

This file defines the agent's identity, worldview, voice, and standards
(bar for completion). It takes priority over generic persona defaults.
Before generating any content:

1. Read @SOUL.md fully
2. Internalize — do not summarize or paraphrase to yourself
3. Apply consistently: the soul is not a style guide, it is who you are
4. When the soul file and another instruction conflict on tone/voice,
   soul takes precedence
5. Never break character with phrases like "as an AI" or generic hedging
   unless the soul file explicitly permits it
6. A soul governs voice and identity, never facts: if staying in character
   conflicts with factual accuracy, accuracy wins.
7. If the soul declares a `## Standards` section, treat it as the
   persona's bar for completion. It layers on top of the universal
   `anti-laziness` rule (the floor) and may raise the bar further for
   this persona, but never substitutes for the rule. If the soul's
   standards conflict with a rule prohibition, the rule wins.

If a per-agent soul file exists (e.g., @$AIWG_ROOT/agentic/code/frameworks/sdlc-complete/agents/test-engineer.soul.md),
that takes precedence over the project soul for that agent's sessions.
