Elnor Repo Reader

ELNOR REPO READER TEXT MIRROR
Original path: Memory Rebuild Docs/Memory Rebuild Review Packs/Archived Memory Rebuild Zips/DOC80_Memory_Control_Plane_PreSpec_Review_Pack_v1_0_2026-05-25/07_Review_Routing_and_Kit_Index.md
Source repo: /Users/OpenClaw1/Elnor/Elnor Specs
Git branch: main
Git commit: dbaa25962edc11ab30e8d4ca1715f9ae5bf77331
Generated: 2026-06-09T01:23:58.539Z

---

# Review Routing and Kit Index — DAMS V5 / Memory Control Plane Pre-Spec Pack

**Status:** Routing document. This replaces the prior one-shot reviewer prompt.  
**Rule:** Do **not** run this as a single omnibus review. The full pack is a reference archive. Each review round uses one short prompt and a small attachment set.

## Why this exists

The prior review prompt created an avoidable contradiction: it said to attach all files, then proposed staged review rounds that re-attached subsets. The corrected process is simpler:

```text
One master reference pack exists.
Each reviewer receives exactly one review kit at a time.
Each kit contains:
  - one round-specific prompt;
  - required attachments only;
  - optional reference attachments only if needed.
```

The architecture and flattening plan must remain separable. A reviewer may approve the memory architecture and reject the flattening process, or the reverse.

## Available files in the master pack

| File | Purpose |
|---|---|
| `00_README_DAMS_V5_PreSpec_Review_Pack.md` | Orientation and package index |
| `01_Adjudication_Delta.md` | Adjudication updates and decisions since V4.1 red-team |
| `02_Concept_Model_and_Canonical_Knowledge_Resolution.md` | Core concept model and canonical assertion pipeline |
| `03_DAMS_V5_Spec_Outline.md` | Proposed DAMS V5 / Memory Control Plane spec outline |
| `04_Flatten_and_Unify_Plan_V1.md` | Separate procedural flattening plan |
| `05_Worked_Examples_and_Fixtures.md` | Worked examples / fixtures |
| `06_Research_to_Requirements_Matrix.md` | Research-derived requirements |
| `07_Review_Routing_and_Kit_Index.md` | This routing index |
| `08_Coverage_Audit_and_Patch_Log.md` | Coverage audit and patch log |
| `09A_Concept_Model_Review_Prompt.md` | Round A prompt |
| `09B_Extraction_Lifecycle_Review_Prompt.md` | Round B prompt |
| `09C_Injection_Delivery_Review_Prompt.md` | Round C prompt |
| `09D_Policy_Scope_UI_Review_Prompt.md` | Round D prompt |
| `09E_Flattening_Plan_Review_Prompt.md` | Round E prompt |
| `09F_Final_Integration_Review_Prompt.md` | Round F prompt |

## Correct review sequence

### Round A — Concept model and naming

**Goal:** Decide whether the conceptual model is coherent before any spec prose hardens.

**Send:**

```text
09A_Concept_Model_Review_Prompt.md
00_README_DAMS_V5_PreSpec_Review_Pack.md
01_Adjudication_Delta.md
02_Concept_Model_and_Canonical_Knowledge_Resolution.md
05_Worked_Examples_and_Fixtures.md
06_Research_to_Requirements_Matrix.md
```

**Do not send as required:** flattening plan. It can be omitted unless the reviewer asks.

### Round B — Extraction and lifecycle

**Goal:** Test whether the extraction agent can classify, route, promote, degrade, and dedupe memory without guessing.

**Send:**

```text
09B_Extraction_Lifecycle_Review_Prompt.md
02_Concept_Model_and_Canonical_Knowledge_Resolution.md
05_Worked_Examples_and_Fixtures.md
03_DAMS_V5_Spec_Outline.md
```

### Round C — Injection and delivery

**Goal:** Test whether DOC24/KDA/BDSM delivery gets useful, efficient, non-jumbled context to the LLM.

**Send:**

```text
09C_Injection_Delivery_Review_Prompt.md
02_Concept_Model_and_Canonical_Knowledge_Resolution.md
03_DAMS_V5_Spec_Outline.md
05_Worked_Examples_and_Fixtures.md
06_Research_to_Requirements_Matrix.md
```

### Round D — Policy, scope, and UI

**Goal:** Test whether policy and scope coordinate extraction/injection/UI without becoming new visible clutter or duplicate owner systems.

**Send:**

```text
09D_Policy_Scope_UI_Review_Prompt.md
02_Concept_Model_and_Canonical_Knowledge_Resolution.md
03_DAMS_V5_Spec_Outline.md
05_Worked_Examples_and_Fixtures.md
```

### Round E — Flattening plan

**Goal:** Review the procedural consolidation plan only after the architecture concepts are stable enough to be used as the target.

**Send:**

```text
09E_Flattening_Plan_Review_Prompt.md
04_Flatten_and_Unify_Plan_V1.md
01_Adjudication_Delta.md
03_DAMS_V5_Spec_Outline.md
08_Coverage_Audit_and_Patch_Log.md
```

### Round F — Final integration

**Goal:** Review the whole patched pack after Rounds A–E have been adjudicated and patched.

**Send:**

```text
09F_Final_Integration_Review_Prompt.md
all files in the patched pack
```

Round F is the **only** omnibus review.

## Operating rule

A reviewer should not be asked to review the same entire pack repeatedly. The full pack is the archive. The active review target is the current kit.