Elnor Repo Reader

ELNOR REPO READER TEXT MIRROR
Original path: Memory Rebuild Docs/DOC80 Target Baseline/Retired Names/DOC80_Retired_Names.md
Source repo: /Users/OpenClaw1/Elnor/Elnor Specs
Git branch: main
Git commit: dbaa25962edc11ab30e8d4ca1715f9ae5bf77331
Generated: 2026-06-09T01:23:58.539Z

---

# DOC80 — Retired Names

**Repository:** github.com/wbrody/Elnor-Specs — branch `main`
**Document status:** `target-baseline` (companion to `DOC80_Skeletal_Target_Baseline.md`).
**Versioning discipline:** git-native — stable filename, no version suffix. Git history is the version record.
**Round:** Stage 5R (patches applied 2026-05-26).

Names retired by the Supersession Matrix. Lint patterns enforce plan §17.2 `supersession.retired_name_used` and `supersession.retired_name_used_outside_allowed_historical_context`.

**Source of truth:** `Memory Rebuild Docs/Flattening/Supersession Matrix/Supersession_Matrix.md`. This file is the navigable retired-name index drawn from that matrix.

---

## 1. Retired names — table

| retired_name | retired_by_row | superseded_by | retired_name_lint pattern | legacy_alias_allowed | allowed_historical_context |
|---|---|---|---|---|---|
| `PremiseFamily` | SM-001 | `Assertion` | `PremiseFamily` | no | lineage / supersession sections only |
| `PremiseVariant` | SM-002 | `AssertionVariant` | `PremiseVariant` | no | lineage / supersession sections only |
| `Premise` (as memory object) | SM-003 | `Premise` (use role) + `Assertion` | (Premise as standalone storage) | yes (until cross-doc rename pass — see §3 alias-expiry table for owner-of-record and expiry condition) | DOC72 / DOC73 legacy citation contexts |
| `Claim` (bare / generic) | SM-004 | `AssertionCandidate` (staging) + namespaced `Claim` (`LegalClaim`, `EvaluationClaim`, `ClaimExtractorOutput`). **Stage 5R clarification (F1):** bare `Claim` is NOT an unqualified alias of `Assertion`; it is *only* a staging-or-namespaced concept depending on context. The pipeline-staged interpretation is `AssertionCandidate`; the legacy / domain interpretation is `<Domain>Claim`. | (bare `Claim` outside namespaced contexts) | yes (namespaced only) | domain namespaces (legal / evaluation / task output) |
| `ConsolidatedUnderstanding` (as reusable truth-store) — **Stage 5R clarification (F1):** what is retired is *CU-as-reusable-truth-store*, not CU as a concept. CU remains a live concept owned by DOC73 (source-bound synthesis); only its use as a reusable-truth carrier is retired. | SM-005 | `ConsolidatedUnderstanding` (source-bound synthesis only, DOC73-owned per ADQ-219); reusable-truth path runs through `Assertion` pipeline | (CU used as reusable-truth carrier) | yes (until DOC73 reconciliation) | DOC73 source-bound contexts (CU as concept is allowed unconditionally; only the *retired use* is restricted) |
| `SourceSetSynthesis` | SM-006 | `ConsolidatedUnderstanding` (source-bound) | (SourceSetSynthesis as standalone name) | yes (until DOC73 rename pass) | DOC73 lineage |
| `ScopeMembrane` (as monolithic policy + boundary) | SM-010 | `ScopeBoundary` (topology) + `PolicyMembraneDecision` (membrane crossing) | (ScopeMembrane as combined policy + boundary) | yes (until rename pass) | Round B/C lineage citations |
| `MemoryPolicyDecision` (scalar) | SM-012 | `MemoryPolicyDecision` (dimensional, 5 axes) + `EffectiveMemoryPolicy` | (scalar MemoryPolicyDecision usage) | no | lineage only |
| `PolicyMembraneDecision` (as allow/block scalar) | SM-014 | `PolicyMembraneDecision` (membrane crossing only) + `MemoryPolicyDecision` (per-dimension) | (scalar allow/block PolicyMembraneDecision) | no | lineage only |
| `DAMS` (as memory truth owner) | SM-020 | `DAMS V5` (attenuator / capacity-prior / salience substrate only) | (DAMS as durable-truth or final-prompt owner) | no | DOC72 / DOC73 lineage in archived material |
| `DAMS standalone ranking` | SM-021 | `DAMS context-product seam` (PolicyCappedDAMSInput → attenuator → ContextProductDecision) | (DAMS as standalone ranker that bypasses policy) | no | lineage only |
| `Library` / `Corpus` / `SourceCollection` / `CorpusIndex` intermixed | **SM-040 (added at Stage 5R per F1)** | Decomposed per ADQ-220 / B2 step 6: `Library-as-organizational-container` → DOC87; `LibrarySourceBinding` / `CorpusIndex` / `SourceCollection` → DOC82 / DOC25; Library UI → DOC86 / DOC20 | (single "Library" or "Corpus" name standing in for the whole intermixed concept) | yes (until owner-doc rename pass) | DOC20 / DOC25 / DOC73 lineage; matrix gap logged at DR-002 |
| `legacy memory card` / `KDA render card` (ad-hoc) | SM-060 | `ContextProduct` (fixed registry of 17 kinds — canonical ABC R0.2 §9.2; B3 split: registry at DOC80 core, assembly contract at DOC84) | (ad-hoc card outside registry) | yes (until DOC24/KDA rename pass) | archived DOC24 / KDA contexts |
| 14 illustrative `ContextProductKind` draft names (the E0 R1 illustrative set — enumerated in `DOC80_Core_Charter_Draft.md` §17.3 / the E0 adjudication cards; e.g. `assertion_pack`, `orientation_rollup`, `resume_card`, `inspector_explanation`, `search_affordance_result`) | SM-060 (E0 discharge 2026-06-01) | canonical 17-kind set per ABC R0.2 §9.2 (E0 §3.1 / §3.1.1) | (any invented kind-name outside the canonical 17) | no | E0 R1 draft + adjudication-card lineage only |
| `Topic facts` / `Library facts` / `Project facts` (parallel truth) | SM-070 | `MemoryMembershipEdge` (now at DOC87 per ADQ-220) + canonical `Assertion` / `CU` / `EvidenceRecord` | `TopicFacts\|LibraryFacts\|ProjectFacts` | no | lineage only |
| `TopicLens` (as passive saved view only) | SM-071 | `TopicLens` (organization semantics, DOC87-owned per ADQ-220) + `TopicCollectionDirective` (governed extraction rule, DOC83) | (TopicLens as the extraction driver) | yes (until DOC20/DOC23 rename pass) | DOC20 lineage |
| `IssueFrameEvent` | SM-080 | `WorkingStateEvent` / `IssueFrameUpdate` | `IssueFrameEvent` | no | lineage only |
| `IssueFrame` (as Assertion / truth store) | SM-081 | `IssueFrame` (workbench) + `AssertionCandidate` (for truth-apt content) | (IssueFrame as Assertion store) | no | (none) |
| `ask_user` (scalar policy result) | SM-102 | `PolicyDisambiguationRequest` (safe question + fallback) | `ask_user` | no | lineage only |
| `AssertionCandidateDisposition` (11-value Concept Model §17.3 enum) | SM-202 | `AssertionCandidateDisposition` (ABC §7.8 7-value enum — VERIFIED 2026-05-27: `durable_eligible` / `durable_eligible_confirmation_required` / `session_scoped` / `ephemeral_reroute` / `candidate_only_pending_issueframe` / `review_queue` / `reject_not_memory`) + separate `AssertionDedupeOutcome` | (any of `retain_as_cu_component`, `create_directive_candidate`, `create_procedure_candidate`, `evaluation_only` — the 4 discontinued Concept Model §17.3 entries; per G-2 guardrail they stay retired; also any of the 11-value names NOT in the ABC §7.8 7-value set) | no | Concept Model §17.3 lineage only. Capabilities behind the 4 removed values are re-homed via `AlternativeExtractionRouting` (DOC83 — renamed from `NonAssertionExtractionOutcome` at Stage 5R2b) per B9 — not by reviving the old enum. Stage 5R2 correction: prior row mis-cited the ABC §7.8 enum values (had been paraphrasing §7.7 decision-tree outcomes); corrected against source. |
| `RecentActivity` (as evidence) | SM-108 | `RecentActivityRollup` (orientation only — can_orient_only invariant; B3 split: generation at DOC73, consumption contract at DOC83) | (RecentActivity used as evidence or warrant) | no | (none) |
| `contamination_risk` (linear penalty) | SM-106 | `contamination_risk` (threshold veto, not penalty; B3 split: threshold rule at DOC81, computation at DAMS V5) | (linear contamination_risk computation) | no | lineage only |
| `safe labels` (ad-hoc, derived from protected content) | SM-105 | `SafeLabelPolicy` (DOC86) + approved vocabulary registry (PropA / EC) | (ad-hoc safe labels outside registry) | no | (none) |
| `NonAssertionExtractionOutcome` (Stage 5R name; renamed at Stage 5R2b — lineage-only entry) | (rename — not a Supersession Matrix row) | `AlternativeExtractionRouting` (DOC83-owned) | `NonAssertionExtractionOutcome` | no | Stage 5R lineage citations only (e.g. earlier ledger entries, Patch Summary B9 / F-3 references, round-1 / round-2 review responses). New code/spec text uses `AlternativeExtractionRouting`. |
| `SourceBoundSynthesisProjection` (Stage 5R name; renamed at Stage 5R2b — lineage-only entry) | (rename — not a Supersession Matrix row) | `SourceBoundSynthesisAdapter` (DOC82 wrapper-only, activates only if DOC73 reconciliation surfaces divergence per ADQ-219) | `SourceBoundSynthesisProjection` | no | Stage 5R lineage citations only (e.g. Owner Map round-1 / round-2 outstanding-items references, ADQ-219 round-1 / round-2 text). New code/spec text uses `SourceBoundSynthesisAdapter`. The adapter is classified under the SemanticProjectionContract as a `KnowledgeProjection` wrapper case. |

**Total retired entries:** **22** SM-backed entries + **2** Stage 5R2b rename-only entries (`NonAssertionExtractionOutcome` → `AlternativeExtractionRouting`; `SourceBoundSynthesisProjection` → `SourceBoundSynthesisAdapter`). The rename-only entries are NOT Supersession Matrix rows (no migration_effect; no capability shift; pure renames for semantic clarity); they exist here so the lint catches stale uses of the old names.

---

## 2. Allowed historical context — quick reference

The `allowed_historical_context` field on each retired name names where the OLD name may still appear. Outside those contexts, the lint `supersession.retired_name_used_outside_allowed_historical_context` (plan §17.2) fires.

| context kind | allowed names | enforcement |
|---|---|---|
| lineage / supersession sections | `PremiseFamily`, `PremiseVariant`, `MemoryPolicyDecision (scalar)`, `PolicyMembraneDecision (scalar)`, `IssueFrameEvent`, `ask_user`, `contamination_risk (linear)`, `DAMS standalone ranking`, etc. | Lints scoped to allow these names ONLY inside Supersession Matrix rows + retired-name table + explicit "Lineage" subsections |
| DOC72 / DOC73 legacy citation | `Premise` (as memory object) | Allowed inside DOC72 / DOC73 owner-doc citations |
| DOC73 source-bound contexts | `ConsolidatedUnderstanding` (in its source-bound semantics, owned by DOC73 — the *retired use* is reusable-truth-store, not the concept itself) | The concept is allowed; the reusable-truth-store use is restricted |
| DOC73 lineage | `SourceSetSynthesis` | Allowed in DOC73 archived/lineage citations |
| Round B/C lineage | `ScopeMembrane` (as combined policy+boundary) | Allowed in Round B/C lineage citations |
| archived DOC24 / KDA contexts | `legacy memory card`, `KDA render card` | Allowed in archived DOC24/KDA contexts; not in active DOC80 family |
| DOC20 lineage | `TopicLens` (as passive saved view only) | Allowed in DOC20 archived references |
| domain namespaces | `Claim` (namespaced as `LegalClaim`, `EvaluationClaim`, `ClaimExtractorOutput`) | Allowed when explicitly namespaced |
| Concept Model §17.3 lineage | superseded `AssertionCandidateDisposition` values (`retain_as_cu_component`, `create_directive_candidate`, `create_procedure_candidate`, `evaluation_only`) | Allowed only in lineage/supersession citations of Concept Model §17.3; capabilities re-homed via `AlternativeExtractionRouting` (DOC83 — renamed from `NonAssertionExtractionOutcome` at Stage 5R2b) |
| DOC20 / DOC25 / DOC73 lineage (SM-040 new at Stage 5R) | intermixed `Library` / `Corpus` / `SourceCollection` / `CorpusIndex` | Allowed in legacy citations; decomposition mandatory in active family |

---

## 3. Aliases with expiry dates

The following aliases are permitted **temporarily** until the named rename pass is complete. After expiry, the old name fires the lint regardless of context:

| retired_name | legacy_alias_allowed_until | rename pass owner |
|---|---|---|
| `Premise` (as memory object) | until cross-doc rename pass complete | DOC80 family + DOC72 + DOC73 |
| `Claim` (bare) | namespaced contexts only — no expiry | (namespacing is the discipline, not a temporary alias) |
| `ConsolidatedUnderstanding` (as reusable truth-store) | until DOC73 reconciliation complete (per ADQ-219) | DOC73 owner |
| `SourceSetSynthesis` | until DOC73 rename pass complete | DOC73 owner |
| `ScopeMembrane` (combined) | until owner-doc rename pass complete | DOC81 + EC + PropA |
| `legacy memory card` / `KDA render card` | until DOC24/KDA rename pass complete | DOC24 + KDA owners |
| `TopicLens` (passive only) | until DOC20 / DOC23 rename pass complete | DOC20 + DOC23 + DOC87 owners |
| intermixed `Library` / `Corpus` (SM-040) | until owner-doc decomposition complete (DOC87 / DOC82 / DOC25 / DOC86) | DOC25 + DOC82 + DOC87 + DOC86 owners |

All other retired names (no `legacy_alias_allowed` flag, or `legacy_alias_allowed: no`) fire the lint immediately if used outside `allowed_historical_context`.

---

## 4. Stage 5R changes (summary)

Per F1 patch:

- **Added SM-040** (Library/Corpus intermixed) — the 22nd entry; matrix-row addition deferred to next matrix update; gap logged at Conflict Register DR-002.
- **Header count corrected to 22** (was incorrectly "22 entries" with 21 rows in the round-1 baseline).
- **`Claim` semantics tightened** — bare `Claim` is NOT an unqualified alias of `Assertion`; it is staged-or-namespaced.
- **`CU` semantics tightened** — what is retired is *CU-as-reusable-truth-store*, not CU as a concept (DOC73 owns the live concept per ADQ-219).

Per F2 patch:

- `VersionedClaim` is pending disposition (DR-003) — not yet a retired-name row; either becomes one or gains a `schema_owner`. Owner Map row for `VersionedClaim` is marked PENDING.
- `WorkSession` is assigned to DOC83 (working-state) at Stage 5R pending DR-005 resolution — not a retired-name row.

---

## 5. Cross-references

For full disposition details, including `migration_effect`, `requires_local_data_migration`, `capability_preservation_proof_ref`, and `architect_decision_ref`, see `Memory Rebuild Docs/Flattening/Supersession Matrix/Supersession_Matrix.md`.

For the per-schema ownership handoff (who used to own each retired name and who now owns it), see `DOC80_Owner_Map.md`.

## 6. Stage 5R2b changes (summary)

- **2 rename-only entries added** at the end of §1 (NonAssertionExtractionOutcome → AlternativeExtractionRouting; SourceBoundSynthesisProjection → SourceBoundSynthesisAdapter). These are NOT Supersession Matrix rows — they exist only so the lint catches stale uses of the old names.
- **Premise `legacy_alias_allowed` row now cross-refs §3** explicitly (rename-pass owner-of-record / expiry condition reference).
- **AssertionCandidateDisposition lineage citation** updated to point to `AlternativeExtractionRouting` (renamed from `NonAssertionExtractionOutcome`).

## 7. Stage 6 E1/E2 (DOC81) changes (2026-06-08, at DOC81 ratification)

- **`PolicyStampScope` / `PolicyStampScopeRef` — RETIRED** (collapsed into `PolicyStamp.scope_items`, Adj V20/B-S6). The standalone wrapper duplicated `PolicyStamp.scope_items` + freshness/expiry post-U4; two must-stay-in-sync carriers invited divergence. `allowed_historical_context = "pre-R3 PolicyStampScope wrapper / lineage only"`. **Lint:** `schema.policy_stamp_scope_ref_used` (a field still typed `PolicyStampScopeRef`). Owner Map line 83 repoints to `PolicyStamp.scope_items`.