Implement SOUL-WP-0011: sufficiency position, coverage matrix, Soul packaging

- T01: research/sufficiency-and-weighting-position.md — reject universal
  weights; necessity core (B1/B3), claim-relative P minimal profiles,
  continuity configuration classes with causal privilege; OpenQuestions
  RQ1/RQ2/RQ5 weighting bullets positioned
- T02: research/coverage-matrix.md — nine INTENT entity types under the
  full vocabulary; success criterion verdict: pass with two strain points
- T03: concepts/soul.md packaging resolved (enacted vs residual Soul);
  RQ4 no longer carries a paper-critical open item
- SCOPE.md work-surface bullets updated; workplan finished

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: sonnet
Assistant-Process: 234768@bnt-lap001
Assistant-Session: 91cdb0c1-a203-431c-b542-cf192b3930a6

concepts/soul.md

@@ -1,6 +1,7 @@
 # Soul
 
-**Status:** retained (RQ4 resolved 2026-09-28, SOUL-WP-0009-T01)  
+**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
 
@@ -32,6 +33,36 @@ strips boundary out.
 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:
@@ -42,11 +73,12 @@ the term is introduced, not by renaming.
 
 ## Open issues
 
-1. Relations vs accumulated consequences vs both (packaging)
-2. How Soul relates to lineage after forks
+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) — decision recorded, see
-`workplans/SOUL-WP-0009-paper-agenda-and-external-review.md` T01.
+**Closed:** rename candidates (RQ4, 2026-09-28); packaging — enacted vs
+residual modes (SOUL-WP-0011-T03, 2026-09-28, see § Packaging above).
 
 ## Sources