Soul: Identity and Continuity Layer

Definition

The soul layer is the durable identity envelope for a swarm. It stores mission intent, operating constraints, approved policies, and continuity context that should persist beyond any single task run.

Why it matters

Without a continuity layer, each run starts from partial context and teams re-apply the same constraints repeatedly. A stable identity layer improves consistency, reduces policy drift, and speeds onboarding of new tasks.

When to use

Use a soul layer when workflows span multiple sessions, require consistent behavioral constraints, or must preserve approval and policy context over time.

When not to use

If execution is fully stateless and one-off, with no need for continuity or governance carryover, a dedicated identity layer may add unnecessary overhead.

Failure modes

Common failures include stale memory being treated as current truth, unconstrained profile growth, and mixing transient execution logs with durable policy state.

Related pages

Centralized vs Federated Agent Memory · Support: Triage and Escalation Swarm · Scope Agent Permissions Safely

Common questions

Is the soul layer the same as memory storage? No, it is the policy-and-identity contract that governs how memory should be interpreted and used.

When should teams add this layer? Add it when workflows repeat over time and policy consistency matters across sessions.