Elnor Repo Reader

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

---

# Codex Review — Stage 1: Source Registry (inventory only)

## Repository
github.com/wbrody/Elnor-Specs — branch `main`

## Files to review (repo-relative paths)
- `Memory Rebuild Docs/Flattening/Source Registry/Source_Registry.md`
- `Memory Rebuild Docs/Flattening/Source Registry/Excluded_File_Summary.md`

## Context files (read-only, for owner-boundary grounding — do not re-review)
- `Memory Rebuild Docs/Flattening/Current Flattening Plan/Flatten_and_Unify_Plan_V2_1c.md`
- `Memory Rebuild Docs/Flattening/Prompts and Instructions/DOC80_Claude_Code_Master_Execution_Runbook_v1_3.md`
- `REPO_FILE_MANIFEST.md`
- `README.md`

## What this artifact is
Stage 1 is **inventory only**. It records every document-like file currently in the repo, applies include/exclude rules, and flags first-glance relevance. It does **not** assign plan §3 `source_status` or `normative_weight`, and it does **not** decide DOC80 inclusion — those are Stage 2 work under the Source Freeze.

Generated counts:
- Tracked files in `git ls-files`: **746**
- Untracked document-like in `git status --short`: **0** (working tree clean)
- Included in Source Registry: **723**
- Excluded (with reasons): **23** (20 .zip archives, 1 .jsx outside Design Mockups, 2 repo-metadata)
- First-glance relevance counts: direct 127, adjacent 324, capability 0, process 142, low 106, unknown 24

## Review questions

1. **Missing files.** Are there document-like files in `REPO_FILE_MANIFEST.md` or visible in `git ls-files` that should appear in the Source Registry but do not? (Reconciliation count matches at 746 — looking specifically for category errors, not count errors.)
2. **Wrong exclusions.** Of the 23 excluded entries, do any belong in the registry? Specifically:
   - The 20 `.zip` archives are excluded as inventory rows because they are binary bundles, not document-like files. Several contain DOC80-relevant material (e.g., older PreSpec Review Pack v0.8, MEMORY_RESILIENCE build packs, DOC8 self-learning bundles). Should any of these be unzipped and inventoried instead?
   - The one `.jsx` outside Design Mockups (`Archived and Subsumed Specs and Lineage/COPIES OF ORIG DOCS 2/q-mockup-v11.7m.jsx`) is excluded as a code file outside the canonical design folder. Is it actually a canonical UI design artifact that should be included?
3. **Wrong inclusions.** Are any of the 723 included rows actually build artifacts, caches, or non-document material that should have been excluded?
4. **Folder un-crawled.** Are there any folders or paths in the repo not represented at all in the registry rows? (Look for gaps in the by-`folder_category` counts: `current_specs 91`, `memory_rebuild 22`, `active_working 3`, `op_a_operations 32`, `design_mockups 94`, `parked 1`, `archived_lineage 478`, `root 2`.)
5. **High-value source marked low relevance.** Of the 106 files marked `low` (all in `archived_lineage` or `parked`), are any of them load-bearing for DOC80 (e.g., a crown-jewel old draft that should be marked `direct`/`adjacent`)? Examples worth checking: archived DOC72/DOC73/DOC24/DOC25/KDA/BDSM lineage, archived DOC80 pre-spec material.
6. **Old / aspirational files preserved.** Are aspirational-but-valuable files preserved in the inventory rather than silently dropped? Spot-check the `low` and `unknown` rows for anything that should be classified higher.
7. **Wrongly-excluded zips.** For each zip archive, the unzipped/canonical text version (if any) should already exist as inventory rows. Are there any zips whose contents are NOT otherwise represented in the registry — i.e., the zip is the only copy of the material?

## Output format
Return a concise audit:
- Cite specific rows by `repo_path` (the registry's first column) or by `Excluded_File_Summary.md` bullet.
- Type each finding `BUG` / `GAP` / `SUGGESTION` / `CONFIRMED`.
- Give concrete corrections — name the exact file and the action ("include this", "re-classify to adjacent", "unzip and inventory contents").
- This is a Stage 1 **inventory** review. Do not make plan §3 source_status / normative_weight assignments (that is Stage 2).
- Do not make DOC80 final-inclusion decisions (those happen at Stage 4 / Stage 5 / per-slice).