ELNOR REPO READER TEXT MIRROR
Original path: Memory Rebuild Docs/Flattening/Execution Ledger/Open_Issues_Map.md
Source repo: /Users/OpenClaw1/Elnor/Elnor Specs
Git branch: main
Git commit: dbaa25962edc11ab30e8d4ca1715f9ae5bf77331
Generated: 2026-06-09T01:23:58.539Z

---

# DOC80 Flatten — Open Issues Map

**Purpose:** single page that traces every issue surfaced by the Stage 5 / Stage 5R skeletal-target reviews to where it landed (closed) or where it is scheduled (deferred).

**Use this when:** you ask "did we cover X?" or "where is Y being handled?" or "what is still open before Stage 6?"

**Status at 2026-06-01 (Stage 6 — E0 (DOC80 core) RATIFIED: patch package applied, CODEX fidelity audit passed, design pass (2× `MINOR_FIXES_THEN_RATIFY`) applied + verified, discharge swept):**
- Skeletal review findings: ALL CLOSED
- Stage 5R3 Pass 1: COMPLETE
- Stage 5R3 Pass 2: COMPLETE (ratified 2026-05-28; OPA V4 published)
- Stage 5R3 Pass 2c: COMPLETE (9 documentation-propagation fixes applied after external review by Claude 4.8 + GPT-5.5 Pro)
- Stage 6 charter authoring: OPEN — **E0 (DOC80 core): RATIFIED 2026-06-01.** R2 (~80 edits) + R3 (§22 + non-egress) applied to `DOC80_Core_Charter_Draft.md` (1,869 lines); CODEX application-fidelity audit passed (F1–F4 fixed); design pass (ChatGPT + Claude, both `MINOR_FIXES_THEN_RATIFY`) — 8 fixes applied + verified; `Ratification.md` written; discharge swept (SM-060→17, Owner Map, Import Graph, Retired Names, STAGE_6 index, ADQ + OPA notes). **Next charter: E1/E2** (Scope/Policy lockstep)

**Update history:**
- 2026-05-28 (R1) — initial map: skeletal review closed; Pass 2 not started; Stage 6 blocked.
- 2026-05-29 (R2) — Pass 2 and Pass 2c complete; OPA V4 operative; Stage 6 E0 in red-team review.
- 2026-05-31 (R3) — **E0 adjudication + confirmation complete (NOT applied / NOT ratified).** §22 egress binding (Critical) + non-egress lock patch folded into the R3 *card*; scope-residue sweep; OPA §6.Z3 committed; two R3 confirmation passes + capture audit clean. **Patch package NOT yet applied to `DOC80_Core_Charter_Draft.md`.** Next: apply + §15.5 + `Ratification.md` + discharge, then next charter E1/E2.
- 2026-05-31 (R3) — attachment-as-memory-retrieval-signal scheduled to E7/E8 (DOC84) with architect weighting note; OPA §6.Z4; DOC80 unaffected (capture only, decision B).
- 2026-06-01 — **E0 RATIFIED.** Patch package applied to `DOC80_Core_Charter_Draft.md` (R1 → 1,869 lines); CODEX application-fidelity audit (`FIXES_NEEDED` → F1–F4 fixed + re-verified); design pass (ChatGPT + Claude, both `MINOR_FIXES_THEN_RATIFY`, no family-architecture defect) — 8 consolidated fixes applied + re-verified; `Ratification.md` + `E0_Design_Fix_Record.md` written; discharge sweep applied (baseline + trackers). Next charter: E1/E2.

---

## Section 1 — Closed (already landed)

### 1.A Synthesis §4 — 12 must-fix items

All landed at Stage 5R2 / 5R2b / 5R2c.

| # | item | landing |
|---|---|---|
| 1 | OP-A reconciliation (OPA-001/004/005/011/012) | Stage 5R2 — OP_A Candidate Disposition rows rewritten |
| 2(a) | 6 compound-owner rows split | Stage 5R2 — Owner Map split; one residual at line 88 cleaned at Stage 5R2c |
| 2(b) | Owner Map placeholder strings cleared | Stage 5R2 — VersionedClaim → DOC73; DynamicHeaderLedger → DOC84 (DR-004 closed) |
| 3 | 4-edge-kind import graph | Stage 5R2 — Import Graph §2.1–§2.4; phantom cycle dissolved |
| 4 | TopicIdentityContract stub for DOC83→DOC87 ordering | Stage 5R2 — OPA-032 |
| 5 | Purge DOC8-as-runtime language | Stage 5R2 §10.18 sweep + Stage 5R2c residuals cleanup |
| 6 | DOC82↔DOC83 disposition seam | Stage 5R2 — Skeletal §10.7-ish; anti-overlap rule assigned to DOC82 |
| 7 | SM-202 enum-value correction + DR-006 re-opened | Stage 5R2 (values corrected); Stage 5R2b (rename to AlternativeExtractionRouting); Stage 5R2c (rename propagation in SM-202 prose) |
| 8 | VersionedClaim + WorkSession resolutions | Stage 5R2 — DR-003 closed (VersionedClaim → DOC73 + lineage table); DR-005 disposition recorded (WorkSession → DOC83) |
| 9 | EC partial/moving + ECSeamContract | Stage 5R2 — OPA-031; Skeletal §10.9 |
| 10(a) | Plan file DOC87 amendment | Stage 5R2 — Plan §12.4-bis (E_org slice between E6 and E7) |
| 10(b) | ADQ-221 status drift | Stage 5R2 §10.18 + Stage 5R2c residuals |
| 10(c) | Standing maintenance discipline (cross-artifact sweep) | Stage 5R2 §10.19 |
| 11 | Network/sharing ADQ | Stage 5R2 — ADQ-222 opened; remains the one open `batch_for_architect` row |
| 12 | V5 non-goal + manual deletion statements | Stage 5R2 — Skeletal §10.1 + §10.2 |

### 1.B Synthesis §5 — ~14 fold-ins

All landed at Stage 5R2.

| item | landing |
|---|---|
| Legal-hold flag + invariant + OPA rows for non-memory destructive jobs | Skeletal §10.3 + OPA-033 |
| CascadingSourceInvalidation 5-plane verification | Skeletal §10.11 |
| DOC81/DOC87 non-overlap invariant | Skeletal §10.4 |
| MemoryMutationEnvelope NAMED | Skeletal §10.5 (schema body deferred to Stage 7) |
| MemoryProvenanceGraph NAMED | Skeletal §10.6 (schema body deferred to Stage 7) |
| ABC §21 normalization-object placement check | Skeletal §10.17 (as Stage 6 charter input — `WarrantEvaluationResult`, `WarrantConsequenceRegistry`, `DomainProfileWarrantPolicy`, `IngestionCostBudget`, `PromotionGateRecord`, `ConsideredItemLedger`, `PromptShellExposure`) |
| Memory-object classification table | Skeletal §10.12 (column set fixed; Stage 6 fills body) |
| Embedding-model-migration refs | Skeletal §10.14 |
| Observability / health seam | Skeletal §10.15 |
| Scale / quota / MemoryOperationQuota | Skeletal §10.16 |
| §18 phase-order fix + revocation scenarios | Skeletal §10.11 (revocation) + ECSeamContract OPA-031 (phase order in policy/extraction handoff); full golden scenario is Stage 6 fixture |
| Concurrency revalidation rule | OPA-031 + Skeletal §11.2 |
| CognitiveDiff → ResumeCard rename | Skeletal §10.13 |
| DOC87 charter prereq (ordering/conflict/idempotency) | Skeletal §10.10 |

### 1.C Stage 5R2b additions — 22 items beyond synthesis

All landed at Stage 5R2b 2026-05-27 from an audit of the underlying Claude / ChatGPT / Codex reviews that the synthesis hadn't rolled up. Architect-authorized same day.

| § | item | source review item |
|---|---|---|
| 11.1 | Recovery / replay seam | Claude R2 A-1 GAP |
| 11.2 | Consistency / concurrency / ordering model | Claude R2 A-5 + Codex R2 A-5 |
| 11.3 | Extraction-side policy-generation re-gate | Claude R2 B-2 |
| 11.4 | Invariant enforcement-point naming | Codex R2 B-3 |
| 11.5 | DOC15 import seam check | ChatGPT §3.22 |
| 11.6 | DOC26 citation check | ChatGPT §3.23 |
| 11.7 | SourceBoundSynthesisAdapter convergence obligation (OPA-035) | Claude R1 B2 SUGGESTION |
| 11.8 | Bitemporal axes on Assertion | Claude R2 D-2 BETTER_IDEA |
| 11.9 | Monotonicity / algebraic invariants | Claude R2 D-3 + Codex R2 D-3 |
| 11.10 | (and 13 more — see live Skeletal §11.10–§11.22) | various |

### 1.D Stage 5R2c bookkeeping (this session)

13 line-level prose fixes across 5 files. See `Stage_5R2c_Patch_Summary.md`. No new architecture; all corrections traceable to already-resolved decisions.

---

## Section 2 — Scheduled (intentionally deferred, has a named landing spot)

### 2.A Stage 6 — E-slice charter authoring

Most ADQ `batch_for_architect` rows (~38) are routed to specific Stage 6 charters where slice design happens. Each charter resolves the open design questions for its slice.

| charter | open items deferred here |
|---|---|
| **E1 (Scope/Policy)** | ADQ-315 AssertionRelationEdge scope checks per relation kind; **privilege/private classification taxonomy hardening** (watch-item logged 2026-05-31 from E0 R3 egress work — ties to ADQ-222 + the Phase-2 egress flip; privilege P1 is a bounded legal taxonomy, private/personal P3 is fuzzier/contextual and largely Phase-II) |
| **E3 (Canonical Knowledge / DOC82)** | ADQ-314 (temporal_class, epistemic_kind) validity table; ADQ-219 DOC73 CU reconciliation finalize; VersionedClaim charter requirements (DR-003); DOC82 evidence-edge contract + DOC73 CU consumption; DOC72 amendment for graph storage |
| **E4 (Source / Evidence)** | ADQ-202 Corpus hierarchy; ADQ-303 parse-quality numeric thresholds; SourceParseQualitySidecar fields; AC-001 DOC25 file-materialization + provider profiles |
| **E5 (Extraction Spine / DOC83)** | ADQ-302 FrictionPattern promotion criteria; AssertionCandidateEmission handoff fixture; DOC83 ↔ DOC87 TopicIdentityContract co-drafting (OPA-032) |
| **E6 (Temporal / Episode)** | WorkSession final disposition (DR-005); OPA-024 RecentActivityRollup E6 lint/fixture |
| **E7 (Runtime context products)** | ADQ-301 DAMS attenuator formula finalization (test-vector-gated); ADQ-305 DynamicHeaderLedger manifest finalization; **attachment as a memory-retrieval signal** — current-turn attachment becomes an input to retrieval, seeded from the DOC25 summary (not the raw doc); documents likely warrant different weight/precedence than the typed prompt (architect note 2026-05-31, decide at DOC84 drafting); delivery already works (DOC25 §3/§22) and DOC80 needs nothing; track via OPA §6.Z4 (`OBL-D84-ATTACHMENT-RETRIEVAL-SIGNAL-01` + `OBL-D25-SUMMARY-AS-RETRIEVAL-SEED-01`) |
| **E8 (Render Safety / Final-Prompt Proof)** | RenderSafetyProof execution at KDA/DOC11 |
| **E9 (Learning / DOC85)** | Two-phase per ADQ-221: Phase 1 architecture + write-back + proof-gating now; Phase 2 BDSM-consumption deferred until BDSM v6.5 next revision. Charter explicitly the LAST among slices. |
| **E10 (UI / Inspector / Search)** | ADQ-306 review-queue auto-archive TTL; ADQ-307 Topic future-watch tier/action 4×4 matrix; ADQ-309 ProjectAutoLinkState TTL |
| **DOC87 charter (E_org)** | OPA-025/026/027/028/029 membership-edge seams; OPA-032 Topic identity contract; DOC87 charter prereq (membership transition ordering, conflict resolution, idempotency) per Skeletal §10.10 |

### 2.B Stage 7 — schema-body work

| item | gate |
|---|---|
| `MemoryMutationEnvelope` schema body | NAMED at 5R2 Skeletal §10.5; body at Stage 7 |
| `MemoryProvenanceGraph` schema body | NAMED at 5R2 Skeletal §10.6; body at Stage 7 |
| `PublishedViewEnvelope` / `TaskSharedMemoryExposureContract` / `PublishedLibraryCorpusExposureContract` | OPA-034 placeholder + ADQ-222 open; schema bodies conditional on architect saying "draft Phase-1 schemas now" — otherwise wait to V6+ |

### 2.C Stage 8 — preservation proofs

| item | gate |
|---|---|
| `capability_preservation_proof_ref` on all 49 SM rows | Plan §8.2 placeholder; preservation-proof landing at Stage 8 after slice review |

### 2.D ADQ-401 / AC-001–005 — aspirational completion rows

| item | minimum_completion_for_v5 enum |
|---|---|
| AC-001 DOC25 file-materialization + provider profiles | schema_plus_owner_boundary |
| AC-002 DOC73 corpus-source-bindings | schema_plus_lints_and_fixtures (depends on ADQ-202) |
| AC-003 RecentActivityRollup E6 lint/fixture (= OPA-024) | schema_plus_lints_and_fixtures |
| AC-004 Memory Intake + At-Use Disciplines | schema_plus_lints_and_fixtures (declined per Stage 5R3 Pass 1 architect decisions — see PASS_1_ARCHITECT_DECISIONS_RESOLVED #6) |
| AC-005 EC Core Addendum A intake-routing | schema_plus_owner_boundary (depends on ADQ-202) |

### 2.E V6+ items (NOT in V5 scope by architect decision)

| item | resolution |
|---|---|
| Automated hard-destruction cascade / DOC88 | DECLINED per synthesis §6. Replaced by: DOC80 core sentence (manual EC deletion); DOC81 `LegalHoldState` flag; OPA-033 for non-memory destructive jobs. No `LifecycleRequest` / `LifecycleEffectPlan` / `DataObjectClass` schema set in V5. |
| Phase-2 networking (multi-device sync, mobile sync, shared Projects, cross-user memory, remote write authority) | Out of V5 per Skeletal §10.1. Stable IDs / generation refs already present for future replay/conflict-detection. Re-open at V6+ if approved. |

---

## Section 3 — Stage 5R3 audit work

### 3.A Pass 1 (Codex coverage audit) — COMPLETE 2026-05-28

Deliverables in `Memory Rebuild Docs/Flattening/Execution Ledger/Stage_5R3/`:
- PASS_1_INVENTORY.md
- PASS_1_DISTRIBUTION_PREVIEW.md
- PASS_1_ROW_SOURCE_DRIFT.md
- PASS_1_S9_TRIAGE.md
- PASS_1_MISSING_SOURCES.md
- PASS_1_ARCHITECT_DECISIONS.md (13 decisions surfaced)
- PASS_1_ARCHITECT_DECISIONS_RESOLVED.md (13 decisions resolved by architect)
- PASS_1_WILL_REVIEW_PACKET.md
- PASS_1_SELF_AUDIT.md

Pass 1 found: 38 explicit `OBL-*` IDs in high-obligation current/folded sources that are absent from OP-A V3.18. Architect decision: 6 DOC24 R3.1.1 IDs add now as Bucket A; 33 DOC23 Addenda B IDs defer entirely (out of scope until flatten complete).

### 3.B Pass 2 (Claude Code retargeting) — COMPLETE (2026-05-28)

Produced 8 deliverables in `Stage_5R3/`:
- PASS_2_WILL_REVIEW_PACKET.md
- OPA_V4_CANDIDATE.md (published as live `OP-A and Operations and Trackers/OPA_V4.md`)
- BUCKET_A.md (512 high-confidence retargets)
- BUCKET_B_SPLITS.md (3 splits → 7 owner-clean children)
- BUCKET_C_ARCHITECT_DECISIONS.md (2 architect-judgment items; both resolved at publication: PBE cluster → DOC73 via ADQ-PASS2-01; corpus/library identity → DOC87 via ADQ-PASS2-02)
- STAGE_6_CHARTER_INPUT_INDEX.md (per-charter input deck)
- SECTION_15A_REWRITE_PREVIEW.md
- Stage_5R3_Pass_2_Self_Audit.md (8th deliverable, recommended)

Inputs pinned in `Stage_5R3_Source_Package.md` (hashes refreshed at Stage 5R2c + Pass 2 ratification).

V4 row counts: 521 §6 active + 17 §8 deferred = 538 total OBL rows; 117 rows own a DOC80-family target.

### 3.C Pass 2c (post-publication external-review cleanup) — COMPLETE (2026-05-28)

External red-team review by Claude 4.8 + GPT-5.5 Pro converged on NEEDS_V4_PATCH_ROUND (documentation-propagation only; row data was sound). 9 fixes applied:
- §9 D7 Bucket C resolutions propagated + pair (4) kept-both note
- STAGE_6_CHARTER_INPUT_INDEX ADQ-PASS2-* marked resolved at 5 line positions
- OPA_V4 candidate-era language scrubbed
- OBL-D7-NEW-LIBRARY-NAMING-01 retargeted DOC7 → DOC86
- §6.A appendix with starter bodies for 7 ADD rows
- §9 D14 (SOURCEARTIFACT charter-deferral marker), D15 (113→117 reconciliation), D11 expansion (D15-RT promotion deferral)

Both reviewers' verdicts moved from NEEDS_V4_PATCH_ROUND to STAGE_6_CAN_OPEN.

### 3.D Stage 6 E0 charter — RATIFIED 2026-06-01 (applied + CODEX-audited + design-passed + discharged) — opened 2026-05-28

First charter: E0 (DOC80 core / Memory Control Plane foundation).

Workflow state:
- Folder + input deck + opening brief: COMPLETE
- Drafting commission (Claude Code) — COMPLETE 2026-05-28 (1083 lines, 17 sections, 15 paste-ready TS schemas, ~15-20 min in fast mode)
- Claude Code self-audit — COMPLETE; minor fixes applied; READY_FOR_RED_TEAM
- Red-team review prompts (single comprehensive prompt; 3-model paste-ready) — COMPLETE
- Gemini upload folder (file copies for Gemini which lacks repo access) — COMPLETE at `ECQ Development/Stage_6_E0_Red_Team_Gemini_Upload/`
- **Red-team reviews IN PROGRESS** (ChatGPT 5 Pro + Claude 4.8 fresh session + Gemini 2.5 Pro)
- Adjudication / synthesis — COMPLETE (Card 1 → R2 → R3 §22 egress-lock fold; multi-LLM red-team + meta-review).
- Apply fixes + ratify — **DONE 2026-06-01.** R2 (~80 edits) + R3 (§22 + non-egress) applied to `DOC80_Core_Charter_Draft.md`; §15.5 regression run (`E0_Application_Report.md`); CODEX application-fidelity audit passed (F1–F4 fixed); design pass (ChatGPT + Claude, both `MINOR_FIXES_THEN_RATIFY`) — 8 fixes applied + verified; `Ratification.md` written. *(SPEC_STATE Core-Specs row deferred to DOC80 graduation / nightly sync — flatten status tracked here + dashboard.)*
- Discharge sweep — **DONE 2026-06-01:** SM-060 14→17, Owner Map (ContextProduct 17 + ResumeProjection/ResumeCard + MFC-variant/MemoryDestructionLedger rows), Import Graph (ECSeamContract pins), Retired Names (17 + invented-names), STAGE_6 index (ADQ-313), ADQ ledger + OPA E0-ratification notes. **Next charter E1/E2** (Scope/Policy seam, lockstep pair).

E0 folder: `Memory Rebuild Docs/Stage_6_Charters/E0_DOC80_Core/`.

---

## Section 4 — Critical path forward (Stage 6 + beyond)

> **UPDATE 2026-06-01 — E0 is RATIFIED.** The patch package (R2 ~80 edits + R3 §22 + non-egress) was applied to `DOC80_Core_Charter_Draft.md`, CODEX application-fidelity-audited (F1–F4 fixed), and design-reviewed (ChatGPT + Claude, both `MINOR_FIXES_THEN_RATIFY` → 8 fixes applied + verified); `Ratification.md` written; discharge swept. Steps 1–3 below are COMPLETE. **Next charter: E1/E2.**

**Both prior blockers cleared.** Stage 5R2c and Stage 5R3 Pass 2 + Pass 2c are all ratified and committed; OPA V4 is operative; Stage 6 charter authoring is open.

**Current immediate path:**

1. **Complete E0 red-team review collection.** Three reviewers in flight (ChatGPT 5 Pro + Claude 4.8 + Gemini 2.5 Pro). All read the same E0_Red_Team_Review_Prompt.md from the repo (Gemini reads from uploaded COPY files).

2. **Adjudicate E0 red-team reviews.** Once all 3 reviews are collected: a fresh chat session synthesizes them into a value-tiered patch list (Critical / Substantive / Minor / Considered-and-declined per Will's standing synthesis discipline — NOT must-fix only).

3. **Apply E0 fixes + ratify.** Cowork or Claude Code applies the patch list; architect reviews + commits. DOC80_Core_Charter_Draft.md becomes the operative DOC80 core spec (Stage 7 schema-body work consumes it).

4. **Discharge sweep.** Mark discharged ADQs/conflicts/OPA rows; update SPEC_STATE for DOC80; refresh dashboard.

5. **Open next charter.** Per the recalibrated 4-week schedule:
   - E1+E2 (DOC81 Scope/Policy lockstep)
   - E_org TopicIdentityContract stub
   - E5+E6 (DOC83 Extraction/Temporal)
   - E3+E4 (DOC82 Knowledge/Source/Evidence)
   - E_org full (DOC87)
   - E7+E8 (DOC84 Delivery/Proof)
   - E10 (DOC86 UI/Inspector/Search)
   - E9 Phase 1 (DOC85 Learning architecture)

After all 8 charters complete: Stage 7 schema bodies + Stage 8 fixtures + Stage 9 lints. Total runway from now per recalibrated estimate: ~4 weeks for Stage 6 charters at Will's normal 2-3 day per-cycle cadence.

---

## Section 5 — How to use this map

- Question: "did we cover X from the skeletal review?"
  - Check §1.A (synthesis must-fixes), §1.B (fold-ins), §1.C (Stage 5R2b additions). If X is named, you have the landing site.
- Question: "where will Y be handled?"
  - Check §2. Find the slice / stage that owns Y.
- Question: "what's blocking Stage 6?"
  - §4. Two items. That's the full list.
- Question: "what's NEVER going to be done in V5?"
  - §2.E. Two items: automated destruction cascade; Phase-2 networking.

This map is a state file — update it as items move from §2 to §1 during Stage 6+ work.