# Soul

**Status:** retained; packaging resolved (RQ4 closed 2026-09-28 — naming
SOUL-WP-0009-T01, packaging SOUL-WP-0011-T03)  
**Working gloss:** Soul = Relation  
**See also:** H5, RQ4 (resolved), RN-001 Finding 14, RN-005 SF-C055

## Working definition (revised)

> The **relation-bearing dimension** through which interactions become persistent
> relationships, commitments, provenance, history, reputation, and consequences
> connecting a Being to other systems across time.

In Soul Frame: **Soul = Relation**.

## What Soul is not

| Not Soul | Belongs to |
|---|---|
| System/environment boundary | **Being** |
| Operational channels | **Body** |
| Adaptive interpretation | **Mind** |

Initial definition overloaded Soul with boundary + relations + legacy. Phase I
strips boundary out.

## Temporal role

- **Body** — present operational coupling  
- **Mind** — interpretation and control of possible states  
- **Soul** — diachronic relational continuity and propagated effects  

Soul continuity can **cross Being-identity discontinuities** (legacy, models in
others, works, Ghosts).

## Packaging (resolved 2026-09-28, SOUL-WP-0011-T03)

**Position: both — relations and consequences — as two modes of one
dimension, asymmetrically:**

| Mode | Content | Requires |
|---|---|---|
| **Enacted Soul** | live relationships, standing commitments, reputation-in-use | an Active Being (or Continuation-Bearing State) on at least one side |
| **Residual Soul** | propagated consequences: works, records, models held by others, reputation-at-rest | no living bearer — persists independently |

Relations are the **constitutive core**; consequences are the same
relational structure **persisting after enactment stops**. This is one
dimension in two modes, not two dimensions: every consequence in residual
Soul is the trace of a relation, and residual Soul can be *re-enacted*
(a reader takes up the works; a `Gh.` resumes a relationship).

Why this packaging and not either alternative:

- *Relations only* would make Criteria §17's TERMINATED note ("Soul/
  relational effects may nevertheless continue") incoherent — something
  persists past the last relation-capable manifestation.
- *Consequences only* would collapse Soul into provenance/legacy and lose
  H5's operational content for living Beings (the Soul of an active Being
  is mostly enacted, not residual).

**Cluster D under this packaging:** `Gh.` inheritance is *residual Soul
taken up for re-enactment under authority* (H10) — structure inherited,
identity not. The inheritance claim survives unchanged; the packaging in
fact names its mechanism.

## Collision analysis

High risk with religious/metaphysical “soul”. **RQ4 resolved 2026-09-28:
retain.** The explanatory payoff of the relational reading (H5) and the
Body/Mind/Soul mnemonic outweigh the collision cost; the cost is managed by
keeping the non-metaphysical disclaimer explicit and prominent everywhere
the term is introduced, not by renaming.

## Open issues

1. How Soul relates to lineage after forks (does residual Soul split,
   copy, or stay shared?)
2. Formal Cluster D depth beyond the inheritance-mechanism naming above

**Closed:** rename candidates (RQ4, 2026-09-28); packaging — enacted vs
residual modes (SOUL-WP-0011-T03, 2026-09-28, see § Packaging above).

## Sources

`research/foundations/001-closure-model-relation-recognition.md` §14–16  
`research/foundations/ResearchNote005-IdentityContinuityStressTest.md` SF-C055